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)
- Unable to start DynamoDB Local process
- DynamoDB Network Error: self signed certificate in chain
- dynamodb local shell not working
- dynamodb connection timeout
- AWS Lambda DynamoDB Stream Error
- ImportError: No module named boto3 (DynamoDB)
- dynamodb map template foreach not working
- could not connect to the endpoint URL dynamodb
- DynamoDB error cannot find module build/Release/DTraceProviderBindings
- could not unmarshal the value dynamodb
- dynamodb put function not working
- DynamoDB Error Message KeyError item is not JSON serializable
- dynamodb list_append returns true but does not work
- could not load profile default dynamodb
- CORS Error DynamoDB
Spend less time in the AWS console, use Dynobase.
Start your 7-day free trial today
Product Features
DynamoDB Tools
DynamoDB Info
© 2023 Dynobase