# AWS S3 Bucket access share

Assetario requires access to data to tune the predictions for your product and have the best performance. One method of sharing your data is to create and share an AWS S3 Bucket with us. The process includes the following steps:

1. Create bucket
2. Create a user
3. Grant the user access to the bucket by creating an inline policy

### Create the Bucket <a href="#bkmrk-create-bucket" id="bkmrk-create-bucket"></a>

Make sure you have an AWS account and are able to log in to it. Log into **AWS Management Console** using your high level account, and use the S3 service to create a new bucket. The bucket name has to be unique across all AWS S3 instances:

![Choose S3 service in your AWS Console to create a new bucket.](/files/8H9K1h2MJ2AFmzBpUjaB)

Pick a **Region** for the bucket. Leave **Block all public access** on:

![](/files/NXZbfzUZH3Yq277vQ0Yb)

Select the bucket and click **Copy ARN** then paste to Notepad (The ARN is the **Amazon Resource Name**. It’s the full formal name for the bucket):

![](/files/27tE234yBq5buW6q4qqq)

In this example, the ARN for **assetario.unique.bucket.name** is `arn:aws:s3:::assetario.unique.bucket.name`*.*

### Create User <a href="#bkmrk-create-iam-objects" id="bkmrk-create-iam-objects"></a>

Go back to the top-level, and select the **IAM** service (Identity and Access Management) to configure policies, groups, and users:

![](/files/MaGSwsmVvRbwXdHzMqDG)

Navigate to **Users** in the left-hand menu, and click **Add users** in the top right corner.

Name the user, and grant **Programmatic access**.

A user can be added with or without **AWS console access**. Enabling console access will allow the third-party user to log into the console and see some limited information about the account, and explore the bucket. Console access should be enabled unless there is a clear reason not to:

<figure><img src="/files/6kaFckInVNBPTjgNs17s" alt=""><figcaption></figcaption></figure>

Then click next until you create the user. Once the user is created, you get a confirmation screen:

<figure><img src="/files/tfDRNRWdtTEnI4mB9Ldt" alt=""><figcaption></figcaption></figure>

At this point, you can download the .csv file, which contains the user credentials.

### Granting user permissions

Click the newly created user in the **Users** section of **IAM**. Click **Add inline policy** on the right in the permissions section.

<figure><img src="/files/bjN5Jeu44n97j2WjHVJJ" alt=""><figcaption></figcaption></figure>

Select the S3 service. Check the **List** and **Read** checkboxes to add all List and Read permissions to the policy:

<figure><img src="/files/k5YAm9JXQRQ25Psc2IE3" alt=""><figcaption></figcaption></figure>

In the **Resources** section, click **Add ARN** in the **bucket** section. Add the bucket's ARN that you previously noted:

<figure><img src="/files/X3M5NLWRPgFx3rVtp97F" alt=""><figcaption></figcaption></figure>

Click **Add ARN** in the **object** section to apply the permissions to all objects in the bucket. Paste the same bucket ARN as before, and add `/*` at the end, so that the permissions apply to **Any** object in that bucket:

<figure><img src="/files/myR4y4zEQzYnxOlqGmig" alt=""><figcaption></figcaption></figure>

Then click **Review policy**. Name the policy appropriately, and create it.

<figure><img src="/files/gtbLbLzXlY6hYHQZGJqj" alt=""><figcaption></figcaption></figure>

You should see the policy attached as *Inline policy* to the user.

### Sharing credentials

Share the `.csv` file with credentials that you downloaded previously with *Assetario*. Please also mention the ARN of the bucket, as it is not written in the credentials file.

The process is complete!


---

# Agent Instructions: 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:

```
GET https://docs.assetario.com/docs/integration/data-input-integration-guides/aws-s3-bucket-access-share.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
