aws-samples / aws-samples/aws-data-mesh-utils

DataMeshConsumer role has no access to shared data product

Open
#26 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
89
Forks
23
PR merge metrics
No merged PRs in 30d

Description

We experimented with the aws-data-mesh-utils to create a simple setup similar to the one outlined in the documentation here.

However, we noticed that the DataMeshConsumer role does not seem to have access to the shared data product (it can see the Glue database, but not the shared Glue table due to insufficient Lake Formation permissions). The reason for this seems to be that the `approve-subscription` step grants Lake Formation permissions to the consumer _account_ as principal, and not to the DataMeshConsumer _IAM role_ as principal.

Is this the intended setup? From what I can see in the code, the `request-access` step uses the requesting account ID as the subscriber principal in the DynamoDB table entry and in the subsequent `approve-subscription` step, this account is used as the principal the Lake Formation permissions are granted to.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.