AWS S3
An overview of the AWS S3 integration with Secoda
Getting started with S3
There are two steps to connect AWS S3 with Secoda
Create a new AWS IAM user or AWS Role
Connect S3 to Secoda
Create a new AWS IAM User or AWS Role
Create a Custom Permissions Policy
Navigate to the 'Policies' page in IAM and 'Create Policy'
Create the following custom permissions policy. Make sure to change
<your-bucket-name>
to the appropriate S3 bucket
Option 1: Create a new AWS IAM user
Navigate to the 'Users' page in IAM and 'Create User'
In the Set Permissions tab select 'Attach policies directly'. Attach the custom permissions policy to the user.
Navigate to the newly created user and click 'Create Access Key' to gain Programmatic Access
Option 2: Create a new AWS Role
Navigate to the 'Roles' page in IAM and 'Create Role'
In the 'Select trusted entity' page, click 'AWS account' and add the following account ID: 482836992928
Click on 'Require External ID' and copy the randomly generated value from Secoda in the S3 connection page
In the Add Permissions tab attach your custom permissions policy to the role.
Connect S3 to Secoda
After creating an IAM user, the next step is to connect S3 to Secoda
In the Secoda App, navigate to the 'Integrations' tab
Click on 'Connect Integration'
Search for and select 'S3'
Add the credentials from the newly created user (Access Key ID, Secret Access Key, Bucket Name, Region) or role (ARN Role, Bucket Name, Region)
Test the Connection - if successful, you'll be prompted to run your initial sync
Last updated