Using Athena data source connectors

This section lists prebuilt Athena data source connectors that you can use to query a variety of data sources external to Amazon S3. To use a connector in your Athena queries, configure it and deploy it to your account.

Considerations and limitations

• Some prebuilt connectors require that you create a VPC and a security group before you can use the connector. For information about creating VPCs, see Creating a VPC for a data source connector.

• To use the Athena Federated Query feature with AWS Secrets Manager, you must configure an Amazon VPC private endpoint for Secrets Manager. For more information, see Create a Secrets Manager VPC private endpoint in the AWS Secrets Manager User Guide.

• Queries that include a predicate take significantly longer to execute. For small datasets, very little data is scanned, and queries take an average of about 2 minutes. However, for large datasets, many queries can time out.

Additional information

• For information about deploying an Athena data source connector, see Deploying a connector and connecting to a data source.

• For information about writing queries that use Athena data source connectors, see Writing federated queries.

• For in-depth information about the Athena data source connectors, see Available connectors on GitHub.

Athena data source connectors

• Azure Data Lake Storage
• Azure Synapse
• Cloudera Hive
• Cloudera Impala
• CloudWatch
• CloudWatch metrics
• CMDB
• Db2
• DocumentDB
• DynamoDB
• Google BigQuery
• Google Cloud Storage
• HBase
• Hortonworks
• Kafka
• MSK
• MySQL
• Neptune
• OpenSearch
• Oracle
• PostgreSQL
• Redis
• Redshift
• SAP HANA
• Snowflake
• SQL Server
• Teradata
• Timestream
• TPC-DS
• Vertica

Note

The AthenaJdbcConnector (latest version 2022.4.1) has been deprecated. Instead, use a database-specific connector like those for MySQL, Redshift, or PostgreSQL.