AWS S3 Setup and Configuration

Bucket and Permissions Setup

To sync data from Triple Whale to AWS S3, you must create an S3 bucket, configure an IAM user, and grant the necessary permissions. This guide walks you through the setup process to ensure a seamless connection.

Step 1: Create an S3 Bucket

1. Open the AWS Console and navigate to S3.
2. Click Create bucket.
3. Enter a Bucket Name (e.g., triplewhale-data), and configure additional settings as needed. Learn more about creating S3 buckets.
4. Click Create bucket to finalize.

Step 2: Create an IAM User

1. Open the AWS Console and navigate to IAM.
2. In the left-hand menu, click Users.
3. Click Create user.
4. Enter a User name (e.g., triplewhale-s3-user).
5. Click Next to proceed.

Step 3: Create a Custom IAM Policy

1. On the Permissions page, click Attach policies directly and then Create policy.

2. Select the JSON tab and replace the content with the following, updating <your-bucket-name>:

   JSON

   {
     "Version": "2012-10-17",
     "Statement": [
       {
         "Sid": "VisualEditor0",
         "Effect": "Allow",
         "Action": ["s3:PutObject", "s3:GetObject", "s3:ListBucket"],
         "Resource": [
           "arn:aws:s3:::<your-bucket-name>",
           "arn:aws:s3:::<your-bucket-name>/*"
         ]
       }
     ]
   }

3. Click Next, enter a Policy name (e.g., TripleWhaleS3Policy), and click Create policy.

Step 4: Attach the Policy to the IAM User

1. Return to the IAM User creation page.
2. Click the Refresh button next to the policy list.
3. Search for the newly created policy (e.g., TripleWhaleS3Policy) and select its checkbox.
4. Click Next and then Create user.

Step 5: Generate and Download Access Keys

1. Go to IAM → Users.
2. Click on the newly created user (e.g., triplewhale-s3-user).
3. Navigate to the Security credentials tab.
4. Scroll to the Access keys section and click Create access key.
5. Select Third-party service as the use case.
6. Confirm and click Create.
7. Click Download .csv file to save the credentials securely.

Step 6: Identify the AWS Region

1. Look at the AWS Console URL (e.g., https://<region>.console.aws.amazon.com).
2. The <region> in the URL indicates your AWS region (e.g., us-east-1, eu-west-1).

---

Connecting to Triple Whale

Once you’ve set up your S3 bucket and IAM user, connect it to Triple Whale:

1. Go to your Triple Whale Integration page.

2. Click Connect on the AWS S3 integration.

   

   Connecting AWS S3 to Triple Whale.

   
   

3. Enter the following details:

   • Region: Found in Step 6.
   • Bucket Name: Enter the bucket name created in Step 1 (e.g., triplewhale-data).
   • AWS Access Key ID: Found in the .csv file from Step 5.
   • AWS Secret Access Key: Found in the .csv file from Step 5.

4. Click Save.

---

Creating an Agent to Schedule Your Sync

After connecting your AWS S3 warehouse to Triple Whale, you can automate data exports by creating an Agent.

1. Open Agents
   Go to Moby > Shop’s Agents in your Triple Whale account. Click New Agent or select an existing one to edit.

2. Set AWS S3 Table as Your Destination
   In the Agent builder, add a Send to Destinations step and pick Sync to Warehouse. Click Select Provider to choose your connected AWS S3 warehouse, and enter the Table ID where you wish to send your data (this should be a unique Table ID that doesn't already exist).

3. Define Query
   Check Use dedicated query, and provide your desired SQL query for the data export. (Note: For smaller exports, you may instead write a custom SQL query using a Get Data step in your agent, though we recommend the Use dedicated query for larger exports.)

4. Configure Your Schedule
   Choose how often you want the Agent to run (e.g., hourly). Once saved, Triple Whale will automatically send new rows to your AWS S3 dataset on that schedule.

---

Troubleshooting

📘

Common Errors and Fixes

• "Access Denied": Ensure the IAM user has the correct permissions. Go to IAM > Policies and verify that the TripleWhaleS3Policy is assigned.
• "Bucket Not Found": Confirm that the correct bucket name was entered in the integration settings.
• "Invalid Credentials": Check that you are using the correct AWS Access Key ID and AWS Secret Access Key from the downloaded .csv file.