A producer account owns a Lake Formation-governed dataset. A consumer account needs authorized analytical access without maintaining a separate full data copy. Which approach should the engineers implement?

Published
  1. Create only a local table with the same name and assume it inherits all producer permissions.
  2. Grant only the consumer a local catalog table name while omitting the producer data share and key permissions.
  3. Publish the raw S3 bucket publicly and rely on the consumer account knowing the correct prefix.
  4. Use the supported Lake Formation cross-account sharing workflow, including required AWS RAM acceptance or organization integration, consumer references where needed, and IAM and encryption permissions.

Comments — 0