-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Support customer-managed keys for server_side_encryption in DynamoDB #8137
Comments
@sworisbreathing Thanks for this; We saw this change in the DynamoDB API about 8 months ago in the release notes for AWS SDK v1.15.16:
and I did some work in #5666 that I ultimately ended up closing as at the time the DynamoDB service didn't support the additions. |
Support for this functionality has been merged and will release with version 2.47.0 of the Terraform AWS Provider, tomorrow. Thanks to @ewbankkit for the implementation. 👍 |
This has been released in version 2.47.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Description
As of November, 2018, CreateTable in DynamoDB now supports Server-Side Encryption with the use of a specific customer-managed key (as opposed to the default DynamoDB KMS master key). However, at the moment, the
aws_dynamodb_table
resource only supports turning SSE on/off but does not support specifying the KMS master key ID used for SSE.Ideally, we should be able to pick which KMS key is used for encrypting data in a DDB table through the
aws_dynamodb_table
resource.In my example below, I've also included
sse_algorithm
as I've copied it from howaws_s3_bucket
works. It should be noted that per the documentation forSSESpecification
, only KMS is applicable. So it's debatable whether or not terraform should exposesse_algorithm
as a config option, given that only kms appears to be supported.New or Affected Resource(s)
Potential Terraform Configuration
References
CreateTable API Documentation
SSESpecification for CreateTable API
How Amazon DynamoDB Uses AWS KMS
The text was updated successfully, but these errors were encountered: