A database specialist wants to copy an Amazon Redshift cluster from a production AWS account to a non-production AWS account.
What is the optimal solution to meet this requirement?
Click on the arrows to vote for the correct answer
A. B. C. D.Answer: C.
Option A is incorrect because this solution requires significant implementation effort.
AWS Glue is a cloud-based service.
So access to Redshift via VPC would require provisioning of VPC endpoints.
Therefore, enabling Glue integration to two different VPC endpoints in inter-region VPC peering requires non-trivial networking configurations.
Further, this solution requires the development of an AWS Glue job.
Hence, this is not the optimal solution.
Option B is incorrect because there is no simple way to “export” a CloudFormation template.
Further, the use of CloudFormation would not perform any data migration.
Option C is CORRECT because sharing a manually created snapshot between AWS accounts and using that snapshot to restore an Amazon Redshift cluster is the simplest solution for copying a cluster between two AWS accounts.
Option D is incorrect because Amazon Redshift Spectrum can be used to query data from files in Amazon S3 without having to load the data into Amazon Redshift tables.
It cannot be used for data migration.
It is not applicable to the problem in this scenario.
Reference:
https://aws.amazon.com/premiumsupport/knowledge-center/account-transfer-redshift/The optimal solution to copy an Amazon Redshift cluster from a production AWS account to a non-production AWS account depends on various factors such as the data volume, available resources, and the level of automation required.
A. Create a target Amazon Redshift cluster. Enable VPC peering between the two VPCs in the two AWS accounts. Use AWS Glue to perform data copy from the source Amazon Redshift cluster to the target Amazon Redshift cluster.
This solution involves creating a target Amazon Redshift cluster in the non-production AWS account, establishing a VPC peering connection between the two AWS accounts, and using AWS Glue to perform a data copy from the source Amazon Redshift cluster to the target cluster. AWS Glue is a fully managed extract, transform, and load (ETL) service that makes it easy to move data between data stores. The advantage of this solution is that it can automate the data copy process, ensuring that the data is transferred reliably and securely between the two clusters.
B. Export a CloudFormation template of the source Amazon Redshift cluster. Use the CloudFormation template to stand up a new Amazon Redshift cluster in the target AWS account.
This solution involves exporting a CloudFormation template of the source Amazon Redshift cluster and using it to create a new cluster in the non-production AWS account. CloudFormation is a service that enables the automation of infrastructure deployment and management. The advantage of this solution is that it can automate the creation of the new cluster, ensuring that it is configured the same way as the source cluster.
C. Create a manual snapshot of the source Amazon Redshift cluster. Share the snapshot with the target AWS account. In the target AWS account, create a new Amazon Redshift cluster by restoring from the shared snapshot.
This solution involves manually creating a snapshot of the source Amazon Redshift cluster, sharing it with the non-production AWS account, and restoring it to a new cluster in the target AWS account. The advantage of this solution is that it is simple and straightforward, and it enables the copying of a complete snapshot of the source cluster to the target cluster.
D. Use Amazon Redshift Spectrum to copy data from the source Amazon Redshift cluster to the target Amazon Redshift cluster.
This solution involves using Amazon Redshift Spectrum to copy data from the source Amazon Redshift cluster to the target cluster. Amazon Redshift Spectrum is a feature that enables the querying of data stored in Amazon S3 using SQL statements. The advantage of this solution is that it can efficiently copy data from the source cluster to the target cluster while minimizing network bandwidth usage.
In summary, the optimal solution to copy an Amazon Redshift cluster from a production AWS account to a non-production AWS account depends on the specific requirements and constraints of the use case. Option A and B are good choices for automated data copying, while C and D are simpler solutions for smaller data volumes or fewer requirements.