An analytics account needs a local namespace for a table owned by a producer account.
Do not copy the metadata or data, but give analysts a clear local reference.
Which configuration is most appropriate?
Create a Lake Formation Resource Link to the shared database or table.
Detailed explanation
A resource link gives the consumer account a local reference to a shared catalog resource.
A resource link gives the consumer account a local reference to a shared catalog resource.
Audit-event search does not provide a Glue Catalog reference.
Audit-event search does not provide a Glue Catalog reference.
Public access removes fine-grained governance and does not create a catalog namespace.
Public access removes fine-grained governance and does not create a catalog namespace.
Physical replication adds delay, cost, and consistency work.
Physical replication adds delay, cost, and consistency work.
Check official documentation
Compare the following points with the official documentation.
Lake Formation Resource Link、cross-account share、Glue Catalogの公式説明を確認する。
What to confirm
メタデータリンクと物理データコピー・公開設定を区別できる。
Key points
- Resource Link
- Lake Formation
- Cross-account
- Local namespace
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Reference versus copy
A resource link preserves one source of truth while giving consumers a usable local name.
Permission chain
The link still requires catalog, IAM, S3, and encryption permissions to align.