Integrating your Amazon S3 storage with our platform is simple and straightforward. Follow the steps below to securely add your Access Key and Secret Key to your account and begin using your S3 storage seamlessly.
Prerequisites:
- An active Amazon Web Services (AWS) account.
- The Access Key and Secret Key for your S3 bucket.
- Access to your SaaS platform account with relevant permissions to configure storage settings.
Step-by-Step Guide:
Step 1: Retrieve Your Amazon S3 Access Key and Secret Key
To get your S3 credentials, follow these steps:
- Sign in to the AWS Management Console.
- Navigate to IAM (Identity and Access Management) from the AWS dashboard.
- Click on Users from the left-hand menu and select the user you want to grant S3 access.
- Under the Security credentials tab, scroll to the Access Keys section.
- Click Create Access Key and use the "Other" use case. AWS will generate the Access Key and Secret Key. Make sure to copy both keys as the Secret Key will only be shown once.
Step 2: Log in to the ThinkData Works Platform
We will need to add our S3 credentials to the platform. You will only need to do this step once as long as you continue to use the same user account these credentials are associated with.
- Open the platform and navigate to the Credentials page: Data > Credentials > Create Credential
- Enter the user name these credentials belong to (or any other identifying name).
- In the type dropdown, select "Amazon S3"
- Enter the Region, Access Key, and Secret Access Key.
- Save
Minimum Policy
Below is a sample minimum access policy to retrieve objects from S3:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:GetObject"
],
"Resource": [
"arn:aws:s3:::bucket-name/*"
]
},
{
"Effect": "Allow",
"Action": [
"s3:GetBucketLocation",
"s3:ListBucket"
],
"Resource": [
"arn:aws:s3:::bucket-name"
]
}
]
}
Important Security Note:
- Never share these credentials with any support staff of ThinkData Works. You should always be entering them in to the console.
- Regularly rotate your keys to maintain security.
Troubleshooting:
- If you encounter errors during the connection, verify that the Access Key and Secret Key are correct.
- Ensure that the IAM user has sufficient permissions to access S3.
- Check that the S3 bucket’s region matches the one specified in the SaaS platform configuration.