> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/latest/configuration/integrations/registering-metadata/data-sources/register-data-sources/s3-tutorial.md).

# Amazon S3 Data Source

## Requirement

`CREATE_S3_DATA_SOURCE` Immuta permission

## Prerequisite

[Configure the Amazon S3 integration](/latest/configuration/integrations/amazon-s3.md)

{% hint style="info" %}
**Private preview**: The Amazon S3 integration is available to select accounts. Contact your Immuta representative for details.
{% endhint %}

## Register S3 data

1. Navigate to the **My Data Sources** page in Immuta.
2. Click **New Data Source**.
3. Select the **S3** tile in the data platform section.
4. Select your AWS **Account/Region** from the dropdown menu.
5. Opt to select a [default domain](/latest/configuration/domains/domains.md) to which data sources will be assigned.
6. Opt to add default tags to the data sources.
7. Click **Next**.
8. The prefix field is populated with the base path. Add to this prefix to create a data source for a prefix, bucket, or object.
   * If the data source prefix ends in a wildcard (`*`), it protects all items starting with that prefix. For example, a base location of `s3://` and a data source prefix `surveys/2024*` would protect paths like `s3://surveys/2024-internal/research-dept.txt` or `s3://surveys/2024-customer/april/us.csv`.
   * If the data source prefix ends without a wildcard (`*`), it protects a single object. For example, a base location path of `s3://` and a data source prefix of `research-data/demographics` would only protect the object that exactly matches `s3://research-data/demographics`.
9. Click **Add Prefix**, and then click **Next**.
10. Verify that your prefixes are correct and click **Complete Setup**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.immuta.com/latest/configuration/integrations/registering-metadata/data-sources/register-data-sources/s3-tutorial.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.