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.

Sign up for GitHub

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

Jump to bottom

bug(dynamodb-seeder): CustomResource cannot access KMS key #102

Open
liveFreeOrCode opened this issue May 10, 2021 · 0 comments
Open

bug(dynamodb-seeder): CustomResource cannot access KMS key #102

liveFreeOrCode opened this issue May 10, 2021 · 0 comments

Comments

@liveFreeOrCode
Copy link
Contributor

liveFreeOrCode commented May 10, 2021 •
edited

When a DynamoDB table has a customer-managed CMK, the following error occurs:

Received response status [FAILED] from custom resource. Message returned: KMS key access denied error: com.amazonaws.services.kms.model.AWSKMSException: The ciphertext refers to a customer master key that does
not exist, does not exist in this region, or you are not allowed to access. (Service: AWSKMS; Status Code: 400; Error Code: AccessDeniedException; Request ID: d7d7828b-5a92-40d3-b306-e3cfae47f761; Proxy: null)
(RequestId: fb5a9bb1-a81c-4504-a541-b172aa2797a9)

#99 gives the appropriate actions to the IAM role policy for the lambda, but it seems that the CustomResource does not have access to the KMS key...

@hupe1980 🙃
@liveFreeOrCode liveFreeOrCode changed the title fix(dynamodb-seeder): KMS needs actions as well bug(dynamodb-seeder): CustomResource cannot access KMS key May 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@liveFreeOrCode