> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/integrations/datasyncs/connecting-your-warehouse/authenticate-s3/use-an-iam-role.md).

# Use an IAM Role

### Setting up an IAM Role

If using an IAM role to provide access

1\) **Create a policy that allows access to the bucket:** 

* Go to the AWS IAM Console → Policies → Create Policy
* Go to the JSON tab
* Copy the following policy and paste it into the visual editor. Replace `{your-bucket-name}` with the name of your S3 bucket.

#### For Imports:

```json
{
    "Version": "2012-10-17",
    "Statement": [
        {
        "Effect": "Allow",
        "Action": [
                "s3:GetBucketLocation",
                "s3:GetObject",
                "s3:ListBucket"

        ],
        "Resource": [
                "arn:aws:s3:::{your-bucket-name}/*",
                "arn:aws:s3:::{your-bucket-name}"
        ]
        }
    ]
}
```

#### For Exports: 

```json
{
    "Version": "2012-10-17",
    "Statement": [
        {
        "Effect": "Allow",
        "Action": [
                "s3:GetBucketLocation",
                "s3:PutObject",
                "s3:ListBucket"

        ],
        "Resource": [
                "arn:aws:s3:::{your-bucket-name}/*",
                "arn:aws:s3:::{your-bucket-name}"
        ]
        }
    ]
}
```

* You can save the policy as `HockeyStack-DataSyncs-S3Access`  

\
2\) **Create an IAM role for our user that can properly access your bucket:** 

* Go to the AWS IAM Console → Roles → Create Role
* Select "Another AWS Account"
  * Enter **422597910032** (HockeyStack-DataSyncs AWS Account ID).
* Check "Require external ID" (Recommended for security)
  * Set an External ID (a unique string you choose, that will be used to configure the DataSync)
* In the Add permissions step, select the `HockeyStack-DataSyncs-S3Access` policy you created, then finish creating the policy. 
* When naming the role, please use the prefix `HockeyStack-DataSyncs*`, as this is required for HockeyStack’s AssumeRole wildcard policy to match. 

{% hint style="warning" %}
If the role you want HockeyStack to assume does not match the wildcard, the Data Sync will **fail with an error** when attempting to assume the role.
{% endhint %}

3\) (**Optional) Giving access specifically to HockeyStack-DataSyncs user:** 

* Edit the custom trust policy of the role, to further specify that only our HockeyStack-DataSyncs user can assume the role: 

```
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::422597910032:user/HockeyStack-DataSyncs"
            },
            "Action": "sts:AssumeRole",
            "Condition": {
                "StringEquals": {
                    "sts:ExternalId": "YOUR_EXTERNAL_ID"
                }
            }
        }
    ]
}
```


---

# 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://docs.hockeystack.com/integrations/datasyncs/connecting-your-warehouse/authenticate-s3/use-an-iam-role.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.