[Enhancement]: enable restore to point in time on aws_rds_cluster based on cluster_resource_id

[aristosvo]

Description

The resource aws_rds_cluster has multiple backup restore possibilities, restore from snaphot and restore from an existing cluster. The lacking feature is the restore from an automated backup which is retained after cluster deletion.

On a resource level, aws_rds_cluster.restore_to_point_in_time has already a source_cluster_identifier parameter. This parameter has one major drawback, as specified in the AWS SDK:

Must match the identifier of an existing DBCluster.

This is not the case for the source_cluster_resource_id (example value: cluster-FT2Y56NA7X7JDBKX7GNV5WX3FX), which is unique (you can create, delete and recreate a cluster with the same ARN, which will have different resource IDs). Restores based on a retained automated backup of a deleted database cluster is only possible with source_cluster_resource_id.

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

• aws_rds_cluster

Potential Terraform Configuration

resource "aws_rds_cluster" "restore" {
...
  restore_to_point_in_time {
    source_cluster_resource_id = aws_rds_cluster.test.cluster_resource_id
    restore_type               = "full-copy"
    use_latest_restorable_time = true
  }
...
}

References

• RestoreDBClusterToPointInTime Action

Would you like to implement a fix?

Yes

[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.

[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.61.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.