Amazon Web Services – Copy an Amazon Redshift Cluster to Different AWS Account
In this article, we will look into how to copy an Amazon Redshift cluster from one account to a different account. Usually, users perform this operation from a production account to a quality account but you can use the steps to move a cluster from one account to another account in the same region.
To do so follow the below steps:
Step 1: In the account that is the owner of the Amazon Redshift cluster after logging in to the AWS Management console navigate to the Amazon Redshift console.
Step 2: Select the Cluster to move and then go to the properties tab.
Here you can see more details about the cluster regarding the parts that it is using encryption and if the cluster is publicly accessible. Note all those settings.
Step 3: After that go to Maintenance and monitoring. Note the maintenance window details under the section Audit logging. Check if this cluster is generating audit logs.
Step 4: Now let’s create a snapshot of this cluster. Choose Actions-> Create a snapshot and then fill in the snapshot name and the retention period. This value is the number of days that you want to retain the snapshot. In our case, we are setting it to 60 days.
Step 5: On the left pane choose Clusters snapshots to see all the snapshots available. Wait a few minutes and make sure that the status of the snapshot is available.
Step 6: After that, select the snapshot, choose Actions -> Manage access, add the number of the account and choose to save.
Step 7: After that under the section Snapshot access, you can see the accounts that can restore this snapshot.
Step 8: In the account that is receiving the access to restore the snapshot, go to the Amazon Redshift console and then select snapshots. Check the box regarding the snapshot that you received and select restore a snapshot. In this case, because the snapshot is encrypted we are going to need to use an AWS key management service key from this account.
Step 9: Select the Node type and Number of nodes. One point that is important to mention is that the cluster endpoint is going to change even if we use the same cluster name. So it’s important to communicate to the users that the endpoint is going to change so they can update the cluster URL.
Now that we have restored the snapshot we can also set up audit logs for the new cluster.