Athena JDBC 2.x driver

Open port 444 – Keep port 444, which Athena uses to stream query results, open to outbound traffic. When you use a PrivateLink endpoint to connect to Athena, ensure that the security group attached to the PrivateLink endpoint is open to inbound traffic on port 444. If port 444 is blocked, you may receive the error message [Simba][AthenaJDBC](100123) An error has occurred. Exception during column initialization.

athena:GetQueryResultsStream policy – Add the athena:GetQueryResultsStream policy action to the IAM principals that use the JDBC driver. This policy action is not exposed directly with the API. It is used only with the ODBC and JDBC drivers as part of streaming results support. For an example policy, see Amazon managed policy: AWSQuicksightAthenaAccess.

Using the JDBC driver for multiple data catalogs – To use the JDBC driver for multiple data catalogs with Athena (for example, when using an external Hive metastore or federated queries), include MetadataRetrievalMethod=ProxyAPI in your JDBC connection string.

Specifying Endpoints in the China Regions – When you use Athena with JDBC in the China Regions, use EndpointOverride= and the endpoint format athena.aws-region.amazonaws.com.cn to specify your Region endpoint in the JDBC URL.

The following example specifies the endpoint for the China (Beijing) Region.

jdbc:awsathena://EndpointOverride=athena.cn-north-1.amazonaws.com.cn:443;AwsRegion=cn-north-1;

4.1 drivers – Starting in 2023, driver support for JDBC version 4.1 is discontinued. No further updates will be released. If you are using a JDBC 4.1 driver, migration to the 4.2 driver is highly recommended.