> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.umnai.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.umnai.com/_mcp/server.

# Storage connectors

A storage connector points to the Amazon S3 bucket that contains your source data. Create the connector before retrieving a schema or running an ingestion job.

## Before you begin

* Know the name of the S3 bucket containing your data.

* Have access to update that bucket's permissions, or arrange for its AWS administrator to complete the permission steps.

## Create an S3 storage connector

1. Select **Data Lab > Storage Connectors** in the left navigation.

2. Select **Create connector** to open the **Create storage connector** form.

3. Complete the two required fields.

| **Field**      | **What to enter**                                    |
| -------------- | ---------------------------------------------------- |
| Connector name | A descriptive name for the connector in the platform |
| Bucket name    | The name of the S3 bucket to connect                 |

![Storage Connectors list and Create connector control](/_fern-files/_img/85c7e316db1adb05b1051161fe39e86dc30c72f88a0e456f7cd38fb19820918d.webp)

![Connector name and Bucket name are required](/_fern-files/_img/560b83e5c947fae34f54f678485794edc8e383cf2d2d40428e3c2242715e60ba.webp)

## Grant access and submit

4. Expand **Grant read-only access to your Amazon S3 bucket** and follow the setup instructions for your environment. The policy grants access to list and retrieve objects. Check the required AWS region before continuing; the example below uses **eu-west-1 (Ireland)**.

5. In the AWS Console, open **S3**, select the bucket, and open **Permissions**. Under **Bucket policy**, select **Edit**.

6. Copy the policy supplied by the platform. Replace each **\<YOUR_BUCKET_NAME>** placeholder with your bucket's name and apply the policy. Keep the AWS principal supplied for your environment.

7. Select **Save changes** in AWS and check the confirmation that the policy was updated.

8. Return to the platform and select the checkbox confirming that you have granted read-only access by applying the bucket policy.

9. Select **Create connector** to submit the form.

![AWS setup instructions supplied by this environment](/_fern-files/_img/9a2fb6d0f0bd4cfa0286a543efdaea4765d8666c46102a6b16d1f00257a0dd3a.webp)

![Permission confirmation checkbox and submission controls](/_fern-files/_img/3d37d271be68279fdba13dfd7106dd80263ba3ea7839a0dbd83e0517ca912338.webp)

## Review a connector

Open **Storage Connectors**, locate the connector, and select its name. You can use **Search connectors...** to locate an entry. The list displays **Connector name**, **Path**, **Created at**, and **Updated at**.

On the connector page, use **Overview** to check the connector name, connector ID, and bucket name. The **Audit trail** section shows creation and update information. Copy icons are available beside the connector name, connector ID, and bucket name.

![Overview of an existing connector and its audit information](/_fern-files/_img/c654a4f4217965c85a8e0089b04d762dd20eb2ae7e24d891815f07b8db38e5d8.webp)

Select **Details** to view the raw connector record, including its identifiers, bucket name, account information, and timestamps. Use the back arrow to return to the list.

![Details displays the raw connector record](/_fern-files/_img/55bb2321ec11caca11172f2dcb62ad5d383ab9784d0f04fc16b17a66600905c1.webp)

## Rename a connector

Open the connector, select **Edit**, update **Connector name** and save. The bucket is read-only on the edit form. Create a separate connector when you need to use another bucket, then select that connector for subsequent schema retrieval or ingestion.

## Next steps

Create a [processing compute configuration](/ui-guides/setup/compute-configurations) for data jobs, then continue to [Data schemas](/ui-guides/data/schemas).