Feature request: AWS RDS Clone

[hashibot]

This issue was originally opened by @gotoadmin as hashicorp/terraform#16671. It was migrated here as a result of the provider split. The original body of the issue is below.

---

The RDS instance clone functionality has been introduced by AWS. When could we expect such possibility in Terraform?

[stumyp]

I also vote for this feature, we have a case, when we need to copy production database to staging on regular basis and snapshot/restore process takes about 2 hours, while cloning is much faster.

[stumyp]

Here is more information on this:
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Aurora.Managing.Clone.html

[dan-petty]

Above URL didn't work for me. Here's the one I found:
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Managing.Clone.html

[dbsaysitall]

Has this issue been addressed? It would be very useful to clone the database as part of the infrastructure set up.

[anGie44]

Hi @bro98025 et al. 👋 I believe this duplicates #5286 and is currently being addressed . The naming differs but I believe the expected behavior is identical as the underlying API method (restore to point in time for both rds clusters and db instances) is used in both situations (clone vs. restore) per AWS RDS docs.

[anGie44]

Hi all, one last follow-up here: support for cloning an Aurora RDS cluster has been merged with #7031 and will release with v3.15.0 of the Terraform AWS Provider, likely out later today.

To use this feature, the argument restore_to_point_in_time restore_type in the rds_cluster resource must be specified with copy-on-write.

Reference: https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBClusterToPointInTime.html (see RestoreType specs)

RestoreType
The type of restore to be performed. You can specify one of the following values:
full-copy - The new DB cluster is restored as a full copy of the source DB cluster.
copy-on-write - The new DB cluster is restored as a clone of the source DB cluster.

Constraints: You can't specify copy-on-write if the engine version of the source DB cluster is earlier than 1.11.
If you don't specify a RestoreType value, then the new DB cluster is restored as a full copy of the source DB cluster.

[dbsaysitall]

Thank you for the update. Will this release support cross AWS account cloning as well? Reference below. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Managing.Clone.html#Aurora.Managing.Clone.CrossAccount.yours

…

On Thu, Nov 12, 2020 at 10:37 AM angie pinilla ***@***.***> wrote: Hi all, one last follow-up here: support for cloning an Aurora RDS cluster has been merged with #7031 <#7031> and will release with v3.15.0 of the Terraform AWS Provider, likely out later today. To use this feature, the argument restore_to_point_in_time restore_type in the rds_cluster resource must be specified with copy_on_write. Reference: https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBClusterToPointInTime.html — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2321 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBBYY6LGJVCUFPK2XCLDCTSPQTNVANCNFSM4EECHU2A> .

[Gufran]

Cross account cloning should work with properly shared clusters and permissions in place. The API and options are same as same account cloning.

[ghost]

This has been released in version 3.15.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!

[ghost]

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!