Property | Description |
|---|---|
Connection Name | Name of the connection. Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -, Maximum length is 255 characters. |
Description | Description of the connection. Maximum length is 4000 characters. |
Use Secret Vault | Stores sensitive credentials for this connection in the secrets manager that is configured for your organization. This property appears only if secrets manager is set up for your organization. When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured. Note: If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option. For information about how to configure and use a secrets manager, see Secrets manager configuration. |
Runtime Environment | The name of the runtime environment where you want to run tasks. |
Authentication type | Authentication mechanism to connect to Amazon Athena . Select Permanent IAM Credentials, EC2 Instance Profile, or EC2 role to assume role. Permanent IAM Credentials is the default authentication mechanism. It requires an access key and secret key to connect to Amazon Athena . Use EC2 Instance Profile when you installed the Secure Agent on an Amazon Elastic Compute Cloud (EC2) system. You can configure AWS Identity and Access Management (IAM) authentication to connect to Amazon Athena . Note: If Amazon Athena and the Amazon EC2 system are set up using different accounts in the same region, you need to configure cross-account access. For more information, see the Amazon Athena user guide in the AWS documentation. You can also configure an EC2 role to assume an IAM role and generate temporary security credentials to connect to Amazon Athena from the same or different AWS accounts. The EC2 role can assume an IAM role without a permanent access key and secret key. |
JDBC URL | The JDBC URL to connect to Amazon Athena . Enter the JDBC URL in the following format: jdbc:awsathena://AwsRegion=<region_name>; S3OutputLocation=<S3_Output_Location>; Workgroup=<Workgroup_Name>; Note: If you use a workgroup with customer managed query results, specify at least one of the two parameters in the JDBC URL, either the S3 output location or the workgroup name. For a workgroup with Athena managed query results, specify only the workgroup name and do not include the S3 output location in the JDBC URL. |
IAM Role ARN | Required if you configure the EC2 Role to Assume Role authentication to connect to Amazon Athena . The Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role assumed by the EC2 role. The EC2 role uses dynamically generated temporary security credentials. |
External ID (Advanced Setting) | The external ID associated with the IAM role. External ID is a unique, user-defined string value that the IAM role requires the EC2 role to provide when calling the sts:AssumeRole API. |