(rds): Support Point-in-Time Database Cluster Recovery via L2 DatabaseCluster construct #25998
Open
1 of 2 tasks
Labels
@aws-cdk/aws-rds
Related to Amazon Relational Database
effort/large
Large work item – several weeks of effort
feature/new-construct
A request for a new L2 construct
feature-request
A feature should be added or improved.
p2
Describe the feature
As of March 2023, the
AWS::RDS::DBCluster
CloudFormation resource supports theRestoreToTime
property.It would be great if there were an L2-construct (ala
DatabaseClusterFromSnapshot
) that made restoring a database to a point-in-time simpler.Use Case
The
DatabaseClusterFromSnapshot
construct is great if you have a snapshot you want to restore from. However, a Point-In-Time Recovery (PITR) might be preferable in disaster recovery scenarios.Proposed Solution
Two ideas:
DatabaseClusterFromPointInTime
constructRestoredDatabaseCluster
construct that encapsulates restoring from a point in time or a snapshot.Creating a new construct feels more in line with what we have today for snapshots.
However, the second option feels "cleaner" because the same principals of restoring from a snapshot apply to the PITR option (a new database is created, etc.)
RestoredDatabaseCluster
might take something like this:Other Information
Alternatively, you can reach into the L1 construct to set the
RestoreToTime
property.In the past, to keep my database managed by CloudFormation/CDK, I've created a temporary new Database cluster via PITR (via the console), taken a snapshot, then used
DatabaseClusterFromSnapshot
.Acknowledgements
CDK version used
2.84.0
Environment details (OS name and version, etc.)
MacOS
The text was updated successfully, but these errors were encountered: