Choose how Atlan connects to Amazon Athena
Pick the right AWS identity type and network path for Atlan to connect to Amazon Athena - IAM access keys, IAM role delegation, or either with AWS PrivateLink.
Pick the right AWS identity type and network path for Atlan to connect to Amazon Athena - IAM access keys, IAM role delegation, or either with AWS PrivateLink.
Connect Amazon Athena to Atlan's Lakehouse using AWS Glue Catalog Federation. Setup registers Atlan's Iceberg REST Catalog as a federated data source in Lake Formation, making Lakehouse tables available to Athena and other AWS query engines.
The fastest path to connect Atlan to Amazon Athena - create a dedicated IAM user, attach the Atlan policy, and paste its access keys into Atlan.
Set up cross-account IAM role delegation so Atlan connects to Amazon Athena with temporary credentials and no stored secret.
Learn how Atlan borrows an identity in your AWS account for Amazon Athena, why there are two halves to set up, and the four traffic paths a healthy connection uses.
The complete permission surface an Amazon Athena connection needs - including Lake Formation, KMS, and the S3 results bucket that cause most "test passed, crawl failed" issues.
Amazon Athena special cases - PrivateLink, cross-account Glue catalogs, cross-region sources, very large catalogs, and multiple Atlan tenants.
Symptom-first troubleshooting for Amazon Athena connectivity - role authentication failures, JDBC timeouts, permission gaps, platform-side signatures, and sudden breakage.
Resolve common issues when querying Lakehouse Iceberg tables from Amazon Athena via the AWS Glue Data Catalog.