An analytics account must query S3 tables owned by a producer account.
Share catalog resources and permissions without copying all data.
Which configuration is most appropriate?
Use Lake Formation cross-account sharing and Glue Catalog resource links to govern access without duplicating data.
Detailed explanation
Replication adds delay, cost, duplication, and consistency management.
Replication adds delay, cost, duplication, and consistency management.
Public access exposes data and removes controlled, least-privilege sharing.
Public access exposes data and removes controlled, least-privilege sharing.
Controlled catalog and data-lake permissions let the analytics account query approved tables.
Controlled catalog and data-lake permissions let the analytics account query approved tables.
Broad permission is excessive and does not implement table-level sharing.
Broad permission is excessive and does not implement table-level sharing.
Check official documentation
Compare the following points with the official documentation.
Lake Formation cross-account sharing、Glue Catalog resource link、IAM・S3権限の公式説明を確認する。
What to confirm
公開・全量コピー・過剰権限と、制御されたCatalog共有を区別できる。
Key points
- Cross-account sharing
- Lake Formation
- Resource link
- Catalog permission
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Share versus replicate
Cross-account catalog sharing avoids the delay and cost of copying every object.
Permission layers
Catalog grants, IAM, S3 policies, and encryption keys must all permit the access.