9 docs tagged with "aws-glue"

What identity Atlan presents to your AWS account for AWS Glue, which values are tenant-specific, and exactly what to request from support in a single ticket.

The exact IAM permissions Atlan needs for AWS Glue, plus the Lake Formation grants whose absence silently empties crawls instead of raising errors.

Pick how Atlan proves its identity to AWS Glue - IAM access keys, a cross-account IAM role, or the self-deployed agent.

The recommended way to connect Atlan to AWS Glue - Atlan assumes a role you create, so no long-lived secret ever leaves your account.

The fastest path to connect Atlan to AWS Glue - create a read-only IAM user in your AWS account and give Atlan its key pair.

Understand how Atlan securely connects to your AWS Glue Data Catalog to extract metadata.

Learn how Atlan reads your AWS Glue Data Catalog - the traffic path, the two ways of proving identity, and the two-key door that makes role-based access safe.

AWS Glue special cases - multiple AWS accounts, multiple regions, cross-account resource links, S3 Table Bucket federated catalogs, and the circuit breaker.

Symptom-first troubleshooting for AWS Glue connectivity - role assumption failures, invalid credentials, access denied, circuit breaker, and missing columns.