Connecting to Amazon S3 Connection

Using IAM role and External ID (most secure)

For more information on External ID, please read How to use an external ID when granting access to your AWS resources to a third party.

Step 1. Begin S3 bucket configuration.

1. Enter Destination Name.

2. Enter Description (optional).

3. Select S3 Bucket from the Destination Type dropdown.

4. Enter your S3 Bucket Name.

5. Check Require External ID.

Step 2. Create IAM policy.

1. Open your Amazon IAM console.

2. Go to Policies, then click Create Policy.

3. Select JSON tab.

4. Copy the policy from the Policy field.

5. And paste it into the Policy editor.

6. Click Next.

7. Enter Policy Name, for example Sequentum_S3_Access.

8. Finally, click Create policy.

Step 3. Create IAM role.

1. Find External ID and make a note of it. You will need it to create an IAM role in AWS. Please note that External ID is auto generated and you will not be able to change it.

2. Open your Amazon IAM console.

3. Go to Roles, then click Create role.

4. On the Select truted entity page, select Custom trust policy.

5. Copy the provided Custom trust policy from the Role Custom Trust Policy field.

6. Paste the copied text into the Custom Trust Policy editor.

7. Click Next.

8. Find and select Sequentum_S3_Access policy you created earlier in Step 2.

9. Click Next.

10. Enter Role Name, for example Sequentum_S3_Access_Role.

11. Finally, click Create role.

12. Click the Sequentum_S3_Access_Role role you created.

13. On the Summary page for the role, find the ARN value and copy it.

14. Paste it into the Role ARN field.

Step 4. Finish S3 bucket configuration.

1. Enter Folder (optional).

2. Click Test Connection.

3. Click Save.

Using Bucket Policy (less secure)

Simple Setup:

Copy and paste the generated policy into the “Bucket Policy” section of your S3 Bucket.

Advanced Setup:

If you have an existing Policy in your bucket you need to add a new Statement to the policy:

{
			"Sid": "AllowSequentumGetObjects",
			"Effect": "Allow",
			"Principal": {
				"AWS": "arn:aws:iam::280772890673:user/sequentum"
			},
			"Action": [
				"s3:PutObjectAcl",
				"s3:PutObject"
			],
			"Resource": "YOUR BUCKET ARN"
}

Specifically, make sure the policy grants the Sequentum ARN permission to run s3:PutObject and s3:PutObjectAcl actions.