mirror of
https://github.com/open-metadata/OpenMetadata.git
synced 2025-07-23 17:30:35 +00:00
248 lines
11 KiB
Markdown
248 lines
11 KiB
Markdown
![]() |
---
|
|||
|
title: Athena
|
|||
|
slug: /connectors/database/athena
|
|||
|
---
|
|||
|
|
|||
|
# Athena
|
|||
|
|
|||
|
{% multiTablesWrapper %}
|
|||
|
|
|||
|
| Feature | Status |
|
|||
|
| :----------------- | :--------------------------- |
|
|||
|
| Stage | PROD |
|
|||
|
| Metadata | {% icon iconName="check" /%} |
|
|||
|
| Query Usage | {% icon iconName="check" /%} |
|
|||
|
| Data Profiler | {% icon iconName="check" /%} |
|
|||
|
| Data Quality | {% icon iconName="check" /%} |
|
|||
|
| Lineage | {% icon iconName="check" /%} |
|
|||
|
| DBT | {% icon iconName="check" /%} |
|
|||
|
| Supported Versions | -- |
|
|||
|
|
|||
|
| Feature | Status |
|
|||
|
| :----------- | :--------------------------- |
|
|||
|
| Lineage | {% icon iconName="check" /%} |
|
|||
|
| Table-level | {% icon iconName="check" /%} |
|
|||
|
| Column-level | {% icon iconName="check" /%} |
|
|||
|
|
|||
|
{% /multiTablesWrapper %}
|
|||
|
|
|||
|
In this section, we provide guides and references to use the Athena connector.
|
|||
|
|
|||
|
Configure and schedule Athena metadata and profiler workflows from the OpenMetadata UI:
|
|||
|
|
|||
|
- [Requirements](#requirements)
|
|||
|
- [Metadata Ingestion](#metadata-ingestion)
|
|||
|
- [Service Name](#service-name)
|
|||
|
- [Connection Options](#connection-options)
|
|||
|
- [Metadata Ingestion Options](#metadata-ingestion-options)
|
|||
|
- [Troubleshooting](#troubleshooting)
|
|||
|
- [Workflow Deployment Error](#workflow-deployment-error)
|
|||
|
- [Related](#related)
|
|||
|
|
|||
|
{% partial file="/v1.1.1/connectors/ingestion-modes-tiles.md" variables={yamlPath: "/connectors/database/athena/yaml"} /%}
|
|||
|
|
|||
|
## Requirements
|
|||
|
|
|||
|
The Athena connector ingests metadata through JDBC connections.
|
|||
|
|
|||
|
{% note %}
|
|||
|
|
|||
|
According to AWS's official [documentation](https://docs.aws.amazon.com/athena/latest/ug/policy-actions.html):
|
|||
|
|
|||
|
*If you are using the JDBC or ODBC driver, ensure that the IAM
|
|||
|
permissions policy includes all of the actions listed in [AWS managed policy: AWSQuicksightAthenaAccess](https://docs.aws.amazon.com/athena/latest/ug/managed-policies.html#awsquicksightathenaaccess-managed-policy).*
|
|||
|
|
|||
|
{% /note %}
|
|||
|
|
|||
|
This policy groups the following permissions:
|
|||
|
|
|||
|
- `athena` – Allows the principal to run queries on Athena resources.
|
|||
|
- `glue` – Allows principals access to AWS Glue databases, tables, and partitions. This is required so that the principal can use the AWS Glue Data Catalog with Athena.
|
|||
|
- `s3` – Allows the principal to write and read query results from Amazon S3.
|
|||
|
- `lakeformation` – Allows principals to request temporary credentials to access data in a data lake location that is registered with Lake Formation.
|
|||
|
|
|||
|
And is defined as:
|
|||
|
|
|||
|
```json
|
|||
|
{
|
|||
|
"Version": "2012-10-17",
|
|||
|
"Statement": [
|
|||
|
{
|
|||
|
"Effect": "Allow",
|
|||
|
"Action": [
|
|||
|
"athena:BatchGetQueryExecution",
|
|||
|
"athena:GetQueryExecution",
|
|||
|
"athena:GetQueryResults",
|
|||
|
"athena:GetQueryResultsStream",
|
|||
|
"athena:ListQueryExecutions",
|
|||
|
"athena:StartQueryExecution",
|
|||
|
"athena:StopQueryExecution",
|
|||
|
"athena:ListWorkGroups",
|
|||
|
"athena:ListEngineVersions",
|
|||
|
"athena:GetWorkGroup",
|
|||
|
"athena:GetDataCatalog",
|
|||
|
"athena:GetDatabase",
|
|||
|
"athena:GetTableMetadata",
|
|||
|
"athena:ListDataCatalogs",
|
|||
|
"athena:ListDatabases",
|
|||
|
"athena:ListTableMetadata"
|
|||
|
],
|
|||
|
"Resource": [
|
|||
|
"*"
|
|||
|
]
|
|||
|
},
|
|||
|
{
|
|||
|
"Effect": "Allow",
|
|||
|
"Action": [
|
|||
|
"glue:CreateDatabase",
|
|||
|
"glue:DeleteDatabase",
|
|||
|
"glue:GetDatabase",
|
|||
|
"glue:GetDatabases",
|
|||
|
"glue:UpdateDatabase",
|
|||
|
"glue:CreateTable",
|
|||
|
"glue:DeleteTable",
|
|||
|
"glue:BatchDeleteTable",
|
|||
|
"glue:UpdateTable",
|
|||
|
"glue:GetTable",
|
|||
|
"glue:GetTables",
|
|||
|
"glue:BatchCreatePartition",
|
|||
|
"glue:CreatePartition",
|
|||
|
"glue:DeletePartition",
|
|||
|
"glue:BatchDeletePartition",
|
|||
|
"glue:UpdatePartition",
|
|||
|
"glue:GetPartition",
|
|||
|
"glue:GetPartitions",
|
|||
|
"glue:BatchGetPartition"
|
|||
|
],
|
|||
|
"Resource": [
|
|||
|
"*"
|
|||
|
]
|
|||
|
},
|
|||
|
{
|
|||
|
"Effect": "Allow",
|
|||
|
"Action": [
|
|||
|
"s3:GetBucketLocation",
|
|||
|
"s3:GetObject",
|
|||
|
"s3:ListBucket",
|
|||
|
"s3:ListBucketMultipartUploads",
|
|||
|
"s3:ListMultipartUploadParts",
|
|||
|
"s3:AbortMultipartUpload",
|
|||
|
"s3:CreateBucket",
|
|||
|
"s3:PutObject",
|
|||
|
"s3:PutBucketPublicAccessBlock"
|
|||
|
],
|
|||
|
"Resource": [
|
|||
|
"arn:aws:s3:::aws-athena-query-results-*"
|
|||
|
]
|
|||
|
},
|
|||
|
{
|
|||
|
"Effect": "Allow",
|
|||
|
"Action": [
|
|||
|
"lakeformation:GetDataAccess"
|
|||
|
],
|
|||
|
"Resource": [
|
|||
|
"*"
|
|||
|
]
|
|||
|
}
|
|||
|
]
|
|||
|
}
|
|||
|
```
|
|||
|
|
|||
|
You can find further information on the Athena connector in the [docs](https://docs.open-metadata.org/connectors/database/athena).
|
|||
|
|
|||
|
## Metadata Ingestion
|
|||
|
|
|||
|
{% partial
|
|||
|
file="/v1.1.1/connectors/metadata-ingestion-ui.md"
|
|||
|
variables={
|
|||
|
connector: "Athena",
|
|||
|
selectServicePath: "/images/v1.1.1/connectors/athena/select-service.png",
|
|||
|
addNewServicePath: "/images/v1.1.1/connectors/athena/add-new-service.png",
|
|||
|
serviceConnectionPath: "/images/v1.1.1/connectors/athena/service-connection.png",
|
|||
|
}
|
|||
|
/%}
|
|||
|
|
|||
|
{% stepsContainer %}
|
|||
|
{% extraContent parentTagName="stepsContainer" %}
|
|||
|
|
|||
|
#### Connection Details
|
|||
|
|
|||
|
- **AWS Access Key ID** & **AWS Secret Access Key**: When you interact with AWS, you specify your AWS security credentials to verify who you are and whether you have
|
|||
|
permission to access the resources that you are requesting. AWS uses the security credentials to authenticate and
|
|||
|
authorize your requests ([docs](https://docs.aws.amazon.com/IAM/latest/UserGuide/security-creds.html)).
|
|||
|
|
|||
|
Access keys consist of two parts: An **access key ID** (for example, `AKIAIOSFODNN7EXAMPLE`), and a **secret access key** (for example, `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`).
|
|||
|
|
|||
|
You must use both the access key ID and secret access key together to authenticate your requests.
|
|||
|
|
|||
|
You can find further information on how to manage your access keys [here](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html).
|
|||
|
|
|||
|
- **AWS Region**: Each AWS Region is a separate geographic area in which AWS clusters data centers ([docs](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html)).
|
|||
|
|
|||
|
As AWS can have instances in multiple regions, we need to know the region the service you want reach belongs to.
|
|||
|
|
|||
|
Note that the AWS Region is the only required parameter when configuring a connection. When connecting to the
|
|||
|
services programmatically, there are different ways in which we can extract and use the rest of AWS configurations.
|
|||
|
|
|||
|
You can find further information about configuring your credentials [here](https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html#configuring-credentials).
|
|||
|
|
|||
|
- **AWS Session Token (optional)**: If you are using temporary credentials to access your services, you will need to inform the AWS Access Key ID
|
|||
|
and AWS Secrets Access Key. Also, these will include an AWS Session Token.
|
|||
|
|
|||
|
You can find more information on [Using temporary credentials with AWS resources](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_use-resources.html).
|
|||
|
|
|||
|
- **Endpoint URL (optional)**: To connect programmatically to an AWS service, you use an endpoint. An *endpoint* is the URL of the
|
|||
|
entry point for an AWS web service. The AWS SDKs and the AWS Command Line Interface (AWS CLI) automatically use the
|
|||
|
default endpoint for each service in an AWS Region. But you can specify an alternate endpoint for your API requests.
|
|||
|
|
|||
|
Find more information on [AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html).
|
|||
|
|
|||
|
- **Profile Name**: A named profile is a collection of settings and credentials that you can apply to a AWS CLI command.
|
|||
|
When you specify a profile to run a command, the settings and credentials are used to run that command.
|
|||
|
Multiple named profiles can be stored in the config and credentials files.
|
|||
|
|
|||
|
You can inform this field if you'd like to use a profile other than `default`.
|
|||
|
|
|||
|
Find here more information about [Named profiles for the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html).
|
|||
|
|
|||
|
- **Assume Role Arn**: Typically, you use `AssumeRole` within your account or for cross-account access. In this field you'll set the
|
|||
|
`ARN` (Amazon Resource Name) of the policy of the other account.
|
|||
|
|
|||
|
A user who wants to access a role in a different account must also have permissions that are delegated from the account
|
|||
|
administrator. The administrator must attach a policy that allows the user to call `AssumeRole` for the `ARN` of the role in the other account.
|
|||
|
|
|||
|
This is a required field if you'd like to `AssumeRole`.
|
|||
|
|
|||
|
Find more information on [AssumeRole](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html).
|
|||
|
|
|||
|
- **Assume Role Session Name**: An identifier for the assumed role session. Use the role session name to uniquely identify a session when the same role
|
|||
|
is assumed by different principals or for different reasons.
|
|||
|
|
|||
|
By default, we'll use the name `OpenMetadataSession`.
|
|||
|
|
|||
|
Find more information about the [Role Session Name](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html#:~:text=An%20identifier%20for%20the%20assumed%20role%20session.).
|
|||
|
|
|||
|
- **Assume Role Source Identity**: The source identity specified by the principal that is calling the `AssumeRole` operation. You can use source identity
|
|||
|
information in AWS CloudTrail logs to determine who took actions with a role.
|
|||
|
|
|||
|
Find more information about [Source Identity](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html#:~:text=Required%3A%20No-,SourceIdentity,-The%20source%20identity).
|
|||
|
|
|||
|
- **S3 Staging Directory (optional)**: The S3 staging directory is an optional parameter. Enter a staging directory to override the default staging directory for AWS Athena.
|
|||
|
- **Athena Workgroup (optional)**: The Athena workgroup is an optional parameter. If you wish to have your Athena connection related to an existing AWS workgroup add your workgroup name here.
|
|||
|
|
|||
|
{% partial file="/v1.1.1/connectors/database/advanced-configuration.md" /%}
|
|||
|
|
|||
|
{% /extraContent %}
|
|||
|
|
|||
|
{% partial file="/v1.1.1/connectors/test-connection.md" /%}
|
|||
|
|
|||
|
{% partial file="/v1.1.1/connectors/database/configure-ingestion.md" /%}
|
|||
|
|
|||
|
{% partial file="/v1.1.1/connectors/ingestion-schedule-and-deploy.md" /%}
|
|||
|
|
|||
|
{% /stepsContainer %}
|
|||
|
|
|||
|
{% partial file="/v1.1.1/connectors/troubleshooting.md" /%}
|
|||
|
|
|||
|
{% partial file="/v1.1.1/connectors/database/related.md" /%}
|