Is your request related to a problem? Please describe.
Right now it is not possible to restore a database using continuous AWS Backup plan (PITR) to restore a deleted database. Currently, no argument is able to provide the support for pointing to continuous recovery point with arn such as arn:aws:backup:eu-west-1:***********:recovery-point:continuous:db-**************-**********
Describe the solution you'd like.
I would like to be able to perform PITR for a deleted database pointing to continuous recovery point in such a way:
The only alternative so far is building additional tools that would base on AWS CLI aws backup start-restore-job or AWS SDKs which introduces other issues when it comes to tracking the correct Terraform state which would have to be handled separately.
Additional context
I can imagine that most of things in here are based off restore-db-instance-to-point-in-time which allow working with continuous backups while the feature I am describing is basing off start-restore-job which might at this point make things undoable at this point already.
Is your request related to a new offering from AWS?
Is this functionality available in the AWS provider for Terraform? Yes
Is your request related to a problem? Please describe.
Right now it is not possible to restore a database using continuous AWS Backup plan (PITR) to restore a deleted database. Currently, no argument is able to provide the support for pointing to continuous recovery point with arn such as
arn:aws:backup:eu-west-1:***********:recovery-point:continuous:db-**************-**********
Describe the solution you'd like.
I would like to be able to perform PITR for a deleted database pointing to continuous recovery point in such a way:
Describe alternatives you've considered.
The only alternative so far is building additional tools that would base on AWS CLI
aws backup start-restore-job
or AWS SDKs which introduces other issues when it comes to tracking the correct Terraform state which would have to be handled separately.Additional context
I can imagine that most of things in here are based off restore-db-instance-to-point-in-time which allow working with continuous backups while the feature I am describing is basing off start-restore-job which might at this point make things undoable at this point already.