Amazon Athena

Create a destination bucket, service policy, and role

Create Athena target bucket

Follow these steps to create a bucket to be used for staging data before transferring to a destination.

1. Navigate to the S3 service page.
2. Click Create bucket.
3. Enter a Bucket name, select an AWS Region, and modify any of the default settings as desired. Note: Object Ownership can be set to “ACLs disabled” and Block Public Access settings for this bucket can be set to “Block all public access” as recommended by AWS. Make note of the Bucket name and AWS Region.
4. Click Create bucket.

Create Athena access policy

1. Navigate to the IAM service page, click on the Policies navigation tab, and click Create policy.

2. Click the JSON tab, and paste the following policy, being sure to replace ACCOUNT_ID, WORKGROUP, BUCKET_NAME and SCHEMA with the your account information.

   • WORKGROUP should be primary unless otherwise specified during connection configuration.
   • BUCKET should refer to the bucket created in the previous step.
   • SCHEMA used below does not need to be created ahead of time. If it does not exist, it will be created automatically before transferring data.

   1
   {
   2
       "Version": "2012-10-17",
   3
       "Statement": [
   4
           {
   5
               "Sid": "AllowAthenaAccess",
   6
               "Effect": "Allow",
   7
               "Action": [
   8
                   "athena:GetQueryResults",
   9
                   "athena:StartQueryExecution",
   10
                   "athena:StopQueryExecution",
   11
                   "athena:StartSession",
   12
                   "athena:GetDatabase",
   13
                   "athena:GetDataCatalog",
   14
                   "athena:GetWorkGroup",
   15
                   "athena:GetTableMetadata",
   16
                   "athena:GetQueryExecution"
   17
               ],
   18
               "Resource": [
   19
                   "arn:aws:athena:*:ACCOUNT_ID:workgroup/WORKGROUP"
   20
               ]
   21
           },
   22
           {
   23
               "Sid": "AllowGlueAccessToDestinationDatabaseAndTables",
   24
               "Effect": "Allow",
   25
               "Action": [
   26
                   "glue:GetDatabases",
   27
                   "glue:GetDatabase",
   28
                   "glue:GetTables",
   29
                   "glue:GetTable",
   30
                   "glue:GetPartitions",
   31
                   "glue:CreateTable",
   32
                   "glue:CreateDatabase",
   33
                   "glue:UpdateTable",
   34
                   "glue:DeleteTable"
   35
               ],
   36
               "Resource": [
   37
                   "arn:aws:glue:*:ACCOUNT_ID:catalog",
   38
                   "arn:aws:glue:*:ACCOUNT_ID:database/SCHEMA",
   39
                   "arn:aws:glue:*:ACCOUNT_ID:database/default",
   40
                   "arn:aws:glue:*:ACCOUNT_ID:table/SCHEMA/*"
   41
               ]
   42
           },
   43
           {
   44
               "Sid": "AllowS3AccessToBucket",
   45
               "Effect": "Allow",
   46
               "Action": [
   47
                   "s3:PutObject",
   48
                   "s3:ListBucket",
   49
                   "s3:GetBucketLocation",
   50
                   "s3:GetObject",
   51
                   "s3:DeleteObject"
   52
               ],
   53
               "Resource": [
   54
                   "arn:aws:s3:::BUCKET_NAME",
   55
                   "arn:aws:s3:::BUCKET_NAME/*"
   56
               ]
   57
           }
   58
       ]
   59
   }
   Athena vs. S3 permissions

   Because Athena uses S3 as the underlying storage layer, the Resource access requested in the policy is scoped down via resource-specific permissions in the S3 actions.

3. Click through to the Review step, choose a name for the policy, for example, transfer-service-policy (this will be referenced in the next step), add a description, and click Create policy.

Create role

1. Navigate to the IAM service page.

2. Navigate to the Roles navigation tab, and click Create role.

3. Select Custom trust policy and paste the provided trust policy (from the prerequisite) to allow AssumeRole access to this role. Click Next.

4. Add the permissions policy created above, and click Next.

5. Enter a Role name, for example, transfer-role, and click Create role.

6. Once successfully created, search for the created role in the Roles list, click the role name, and make a note of the ARN value.

   Alternative authentication method: AWS User with HMAC Access Key ID & Secret Access Key

   Role-based authentication is the preferred authentication mode for Athena based on AWS recommendations. However, HMAC Access Key ID & Secret Access Key is an alternative authentication method that can be used if preferred.

   1. Navigate to the IAM service page.
   2. Navigate to the Users navigation tab, and click Add users.
   3. Enter a User name for the service, for example, transfer-service, click Next. Under Select AWS access type, select the Access key - Programmatic access option. Click Next: Permissions.
   4. Click the Attach existing policies directly option, and search for the name of the policy created in the previous step. Select the policy, and click Next: Tags.
   5. Click Next: Review and click Create user.
   6. In the Success screen, record the Access key ID and the Secret access key.

Add your destination

Use the following details to complete the connection setup: database, schema, workgroup, bucket name, bucket region, and IAM Role ARN.

• Instructions for Analyze / Optimize for Webflow sites
• Instructions for Optimize for non-Webflow sites

Data management

Follow these guidelines to manage your new Athena tables effectively:

Optimize Iceberg queries

To optimize the performance of your Iceberg tables, use the OPTIMIZE command. This command reorganizes the data in a way that improves query efficiency. Execute the following query periodically:

1
OPTIMIZE iceberg_table REWRITE DATA;

Set vacuum properties

Iceberg tables can accumulate snapshots over time, which can affect performance. To manage this, set the maximum age for snapshots that the vacuum process should retain:

1
ALTER TABLE iceberg_table SET TBLPROPERTIES (
2
  'vacuum_max_snapshot_age_seconds'='259200');

The default setting is 432000 seconds, we recommend only updating this if you notice degrading performance.

Perform time travel queries

Iceberg supports accessing historical data snapshots using time travel queries. This feature allows you to query the table as it appeared at a previous point in time, which is useful for audits and rollbacks:

1
SELECT * FROM iceberg_table FOR TIMESTAMP AS OF timestamp;

Replace timestamp with the specific UNIX timestamp of the snapshot you wish to query.