To protect data from unauthorized access, Athena requires all connections to be authenticated using an access key and a secret key, and uses the SSL protocol that is implemented in Amazon Web Services. The Simba Amazon Athena JDBC Connector protects your data by providing support for these authentication protocols and further obscuring data from unwanted access by providing encryption options for your query results. The connector provides mechanisms that enable you to authenticate your connection using either an AWS access key and secret key, or a class that implements the AWSCredentialsProvider interface. For detailed configuration instructions, see Configuring Authentication. Additionally, the connector automatically applies SSL encryption to all connections. SSL encryption protects data and credentials when they are transferred over the network, and provides stronger security than authentication alone.
Note: In this documentation, “SSL” indicates both TLS (Transport Layer Security) and SSL (Secure Sockets Layer). The connector supports industry-standard versions of TLS/SSL.
The SSL version that the connector supports depends on the JVM version that you are using. For information about the SSL versions that are supported by each version of Java, see “Diagnosing TLS, SSL, and HTTPS” on the Java Platform Group Product Management Blog: https://blogs.oracle.com/java-platform-group/entry/diagnosing_tls_ssl_and_https.
Note: The SSL version used for the connection is the highest version that is supported by both the connector and the server, which is determined at connection time.
For query results, the Simba Amazon Athena JDBC Connector supports all the encryption options that Athena supports. For detailed information about the supported encryption options, see “Configuring Encryption Options” in the Amazon Athena User Guide : http://docs.aws.amazon.com/athena/latest/ug/encryption.html. For information about configuring encryption in the connector, see Configuring Query Result Encryption.