[Enhancement]: Support for cross-region restores in aws_dynamodb_table

[breathingdust]

Description

DynamoDB restores allow restoring a table to a different region. Per AWS documentation:

• The sse-specification-override parameter is mandatory for cross-Region restores but optional for restores to the same Region as the source table.

• The source-table-arn parameter must be provided for cross-Region restores.

• When performing a cross-Region restore from the command line, you must set the default AWS Region to the desired destination Region. To learn more, see Command line options in the AWS Command Line Interface User Guide.

Currently neither source_table_arn or sse_specification_override are supported by the aws_dynamodb_resource

Affected Resource(s) and/or Data Source(s)

• aws_dynamodb_table

Potential Terraform Configuration

resource "aws_dynamodb_table" "basic-dynamodb-table" {
  restore_source_name                = ""
  restore_date_time                  = ""
  restore_source_table_arn           = "table_arn"
  restore_sse_specification_override = "Enabled=true,SSEType=KMS,KMSMasterKeyId=abcd1234-abcd-1234-a123-ab1234a1b234"
}

References

• https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery.Tutorial.html

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[johnsonaj]

sse_specification_override is already available via the server_side_encryption attribute

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

This functionality has been released in v5.64.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. Thank you!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.