Error: KMS Key Access Denied Error DynamoDB
What's Causing This Error
As the error itself represents, this error occurs when you do not own permission to perform the attempted task. For instance, when using an AWS KMS key, several policies determine the security of the database table. So, this kind of error can occur if the necessary permission is not granted to the IAM user trying to access the table.
Solution: Here's How To Resolve It
In such instances, ensure that the IAM user attempting to access the table has the necessary permission to complete the task. For example, a minimum of the following permissions should be there.
- Having kms:GenerateDataKey permission for generating and encrypting table key.
- kms:ReEncrypt permission for re-encrypt data encryption keys from a newly generated table key if the customer-managed key is modified.
- kms:CreateGrant permission and kms:DescribeKey permission.
Other Common DynamoDB Errors (with Solutions)
- dynamodb list_append returns true but does not work
- lambda function not triggering from dynamodb
- AWS DynamoDB CredentialsError: Missing credentials in config
- CORS Error DynamoDB
- failed to begin subsegment named 'amazondynamodbv2': segment cannot be found.
- dynamodb put item not working
- dynamodb ttl not deleting / erasing items
- DynamoDB Key element does not match the schema
- AWS CLI DynamoDB Error Parsing Parameter
- DynamoDB error cannot find module build/Release/DTraceProviderBindings
- dynamodb: one or more parameter values were invalid: type mismatch for index key
- aws lambda dynamodb nodejs not working after few puts
- DynamoDB Code Working In Node But Not SAM
- ValidationException: Invalid KeyConditionExpression: Attribute name is a reserved keyword;
- dynamodb put function not working
© 2022 Dynobase