Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DataMeshConsumer role has no access to shared data product #26

Open
SamuelBucheliZ opened this issue Nov 9, 2023 · 0 comments
Open

Comments

@SamuelBucheliZ
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant