Available data source connectors - Amazon Athena
Considerations and limitationsCase resolver modes in Federation SDKConnector support for case resolver modesCase resolver limitationsAdditional information
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Available 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 Create a VPC for a data source connector or Amazon Glue connection.

  • To use the Athena Federated Query feature with Amazon 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 Amazon Secrets Manager User Guide.

  • For connectors that do not support predicate pushdown, queries that include a predicate take 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.

  • Some federated data sources use terminology to refer data objects that is different from Athena. For more information, see Understand federated table name qualifiers.

  • We update our connectors periodically based on upgrades from the database or data source provider. We do not support data sources that are at end-of-life for support.

  • For connectors that do not support pagination when you list tables, the web service can time out if your database has many tables and metadata. The following connectors provide pagination support for listing tables:

    • DocumentDB

    • DynamoDB

    • MySQL

    • OpenSearch

    • Oracle

    • PostgreSQL

    • Redshift

    • SQL Server

Case resolver modes in Federation SDK

The Federation SDK supports the following standardized case resolver modes for schema and table names:

  • NONE – Does not change case of the given schema and table names.

  • LOWER – Lower case all given schema and table names.

  • UPPER – Upper case all given schema and table names.

  • ANNOTATION – This mode is maintained for backward compatibility only and is supported exclusively by existing Snowflake and SAP HANA connectors.

  • CASE_INSENSITIVE_SEARCH – Perform case insensitive searches against schema and tables names.

Connector support for case resolver modes

Basic mode support

All JDBC connectors support the following basic modes:

  • NONE

  • LOWER

  • UPPER

Annotation mode support

Only the following connectors support the ANNOTATION mode:

  • Snowflake

  • SAP HANA

Note

It is recommended to use CASE_INSENSITIVE_SEARCH instead of ANNOTATION.

Case-insensitive search support

The following connectors support CASE_INSENSITIVE_SEARCH:

  • DataLake Gen2

  • Snowflake

  • Oracle

  • Synapse

  • MySQL

  • PostgreSQL

  • Redshift

  • ClickHouse

  • SQL Server

  • DB2

Case resolver limitations

Be aware of the following limitations when using case resolver modes:

  • When using LOWER mode, your schema name and all tables within the schema must be in lowercase.

  • When using UPPER mode, your schema name and all tables within the schema must be in uppercase.

  • When using CASE_INSENSITIVE_SEARCH:

    • Schema names must be unique

    • Table names within a schema must be unique (for example, you cannot have both "Apple" and "APPLE")

  • Glue integration limitations:

    • Glue only supports lowercase names

    • Only NONE or LOWER modes will work when registering your Lambda function with GlueDataCatalog/LakeFormation

Additional information

Athena data source connectors
Note

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