Ready to get started?

Learn more about the CData JDBC Driver for Amazon Athena or download a free trial:

Download Now

Connect to Amazon Athena Data from a Connection Pool in Jetty

The Amazon Athena JDBC Driver supports connection pooling: This article shows how to connect faster to Amazon Athena data from Web apps in Jetty.

The CData JDBC driver for Amazon Athena is easy to integrate with Java Web applications. This article shows how to efficiently connect to Amazon Athena data in Jetty by configuring the driver for connection pooling. You will configure a JNDI resource for Amazon Athena in Jetty.

Configure the JDBC Driver for Salesforce as a JNDI Data Source

Follow the steps below to connect to Salesforce from Jetty.

  1. Enable the JNDI module for your Jetty base. The following command enables JNDI from the command-line:

    java -jar ../start.jar --add-to-startd=jndi
  2. Add the CData and license file, located in the lib subfolder of the installation directory, into the lib subfolder of the context path.
  3. Declare the resource and its scope. Enter the required connection properties in the resource declaration. This example declares the Amazon Athena data source at the level of the Web app, in WEB-INF\jetty-env.xml.

    <Configure id='athenademo' class="org.eclipse.jetty.webapp.WebAppContext"> <New id="athenademo" class="org.eclipse.jetty.plus.jndi.Resource"> <Arg><Ref refid="athenademo"/></Arg> <Arg>jdbc/athenadb</Arg> <Arg> <New class="cdata.jdbc.amazonathena.AmazonAthenaDriver"> <Set name="url">jdbc:amazonathena:</Set> <Set name="AccessKey">'a123'</Set> <Set name="SecretKey">'s123'</Set> <Set name="Region">'IRELAND'</Set> <Set name="Database">'sampledb'</Set> <Set name="S3StagingDirectory">'s3://bucket/staging/'</Set> </New> </Arg> </New> </Configure>

    Authenticating to Amazon Athena

    To authorize Amazon Athena requests, provide the credentials for an administrator account or for an IAM user with custom permissions: Set AccessKey to the access key Id. Set SecretKey to the secret access key.

    Note: Though you can connect as the AWS account administrator, it is recommended to use IAM user credentials to access AWS services.

    Obtaining the Access Key

    To obtain the credentials for an IAM user, follow the steps below:

    1. Sign into the IAM console.
    2. In the navigation pane, select Users.
    3. To create or manage the access keys for a user, select the user and then select the Security Credentials tab.

    To obtain the credentials for your AWS root account, follow the steps below:

    1. Sign into the AWS Management console with the credentials for your root account.
    2. Select your account name or number and select My Security Credentials in the menu that is displayed.
    3. Click Continue to Security Credentials and expand the Access Keys section to manage or create root account access keys.

    Authenticating from an EC2 Instance

    If you are using the CData Data Provider for Amazon Athena 2018 from an EC2 Instance and have an IAM Role assigned to the instance, you can use the IAM Role to authenticate. To do so, set UseEC2Roles to true and leave AccessKey and SecretKey empty. The CData Data Provider for Amazon Athena 2018 will automatically obtain your IAM Role credentials and authenticate with them.

    Authenticating as an AWS Role

    In many situations it may be preferable to use an IAM role for authentication instead of the direct security credentials of an AWS root user. An AWS role may be used instead by specifying the RoleARN. This will cause the CData Data Provider for Amazon Athena 2018 to attempt to retrieve credentials for the specified role. If you are connecting to AWS (instead of already being connected such as on an EC2 instance), you must additionally specify the AccessKey and SecretKey of an IAM user to assume the role for. Roles may not be used when specifying the AccessKey and SecretKey of an AWS root user.

    Authenticating with MFA

    For users and roles that require Multi-factor Authentication, specify the MFASerialNumber and MFAToken connection properties. This will cause the CData Data Provider for Amazon Athena 2018 to submit the MFA credentials in a request to retrieve temporary authentication credentials. Note that the duration of the temporary credentials may be controlled via the TemporaryTokenDuration (default 3600 seconds).

    Connecting to Amazon Athena

    In addition to the AccessKey and SecretKey properties, specify Database, S3StagingDirectory and Region. Set Region to the region where your Amazon Athena data is hosted. Set S3StagingDirectory to a folder in S3 where you would like to store the results of queries.

    If Database is not set in the connection, the data provider connects to the default database set in Amazon Athena.

  4. Configure the resource in the Web.xml:

    jdbc/athenadb javax.sql.DataSource Container
  5. You can then access Amazon Athena with a lookup to java:comp/env/jdbc/athenadb: InitialContext ctx = new InitialContext(); DataSource myathena = (DataSource)ctx.lookup("java:comp/env/jdbc/athenadb");

More Jetty Integration

The steps above show how to configure the driver in a simple connection pooling scenario. For more use cases and information, see the Working with Jetty JNDI chapter in the Jetty documentation.