Amazon Athena

Amazon Athena is a serverless query service that makes it easy to analyze data stored in Amazon S3. As a scheduler environment in Paradime, Athena enables deploying dbt™ in production with Bolt.

IP RESTRICTIONS

Make sure to allow traffic from one of the Paradime IPs in your firewall depending on the data location selected.

👉 See also: Paradime IP addresses.

Setup Instructions

  1. Click the gear Icon (⚙️) on the top right of the Paradime interface to access Account Settings

  2. In the left sidebar, click "Connections"

  3. Click "Add New" next to the Scheduler section

  4. Select "Amazon Athena"

  5. In the Profile Configuration field, add at least these required parameters. For additional configuration options, see the Profile Fields Reference section.

s3_staging_dir: s3://analytics-staging/athena/query-results/   # Store query results
s3_data_dir: s3://analytics-data/raw/                          # Raw data location
s3_data_naming: table_unique                                   # Unique table naming
region_name: us-west-2                                         # AWS region
database: analytics_prod                                       # Production database
num_retries: 3                                                 # Query retry attempts

After adding the configuration, ensure it's properly formatted using a YAML formatter like YAML Formatter.

  1. Provide a dbt™ Profile Name (This should match with the profile name set in your dbt_project.yml).

  2. In the Target field, enter "prod". This is the default target your dbt™ project will use for your Bolt Schedules.

  3. The "Schema" field is pre-configured, but you can change it to specify the schema where dbt will build objects.

  4. The "Threads" value is pre-configured to 1, but you can adjust this number to specify how many parallel operations your dbt project can run.


Example Profile Configuration


Profile Fields Reference


Important Notes

  • All S3 paths should end with a forward slash (/)

  • The AWS credentials can be configured through environment variables, AWS credentials file, or IAM roles

Last updated