Tamr supports authenticating to S3 connections using either access keys or AWS IAM role assumption.

Before creating an S3 connection in Tamr:

1. Configure S3 IAM policies for uploading and publishing data. If enabled on your tenant, you can restrict S3 bucket access to Tamr VPC endpoints.
2. Configure either:
   • S3 access key authentication
   • S3 assume role authentication

Once you have completed these steps, gather the required information for the connection, below, and follow the steps in the Managing Connections topic to add the connection.

Required Information for S3 Connection

When adding a connection, you are prompted for specific information for the connection type. Gather the following information before adding the connection.

Required information

• Name
• Description (Optional)
• Bucket name
• Region
• If authenticating via access key:
  • Access Key ID
  • Secret Access Key
• If authenticating via assumed role:
  • Role ARN
• Prefix (Optional)
  Configures a sub-path in the container for this connection. If you specify the prefix, your directories in the path must be created. Do not include a leading "/" in the prefix.

See AWS Documentation for more information.