5 thoughts on “Cross-account AWS Glue Data Catalog access with Glue ETL

  1. Very nice details steps – made it super easy to understand. Thank you for the nice documentation.

  2. In both policies, you are granting “Action”: “s3:*”.

    Why do we need all Write permissions on the source catalog, DBs and S3? The Glue jobs in account A only needs to read the data from the relevant S3 buckets of account B. So granting all Write permissions might lead to accidentally modifying the data in account B which is undesirable if the job is reading from prod accounts/buckets. Just reflecting based on a real scenario I’m facing!

    I guess only List and Read permissions would be enough.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s