Troubleshooting
Resolve common IAM, cross-account, and catalog connection errors in a Serverless e6data deployment on AWS.
Permission denied
Verify the IAM role has s3:GetObject and s3:ListBucket on the correct bucket ARNs.
Glue access denied
Ensure the role has Glue permissions (glue:GetTable, glue:GetPartitions, and so on) on the correct resources.
Role cannot be assumed
Check the trust policy includes the correct e6data account ID and role name.
Cross-account access fails
Verify that both the trust policy and the S3 bucket policies allow cross-account access.
Catalog test connection fails
Ensure the IAM role can access both the Glue catalog and the underlying S3 data.
Federated credential issues
Make sure the trust policy Action includes both sts:AssumeRole and sts:TagSession.
Still blocked
Contact e6data support with the IAM role ARN, error logs, and bucket information.
See also
Configure AWS access - the IAM role and policies these errors refer to.
FAQs - access and revocation questions.
Last updated
Was this helpful?