How do I move my Amazon Redshift provisioned cluster from one VPC to another VPC?
Last updated: 2022-08-29
How can I move an Amazon Redshift cluster from one Amazon Virtual Private Cloud (Amazon VPC) to another VPC?
To move an Amazon Redshift provisioned cluster from one VPC to another:
- Confirm the AWS Identity and Access Management (IAM) roles and configuration details of the source cluster.
- Create a cluster subnet group.
- Take a snapshot of the source cluster.
- Restore the cluster to the new cluster subnet group.
- Associate the IAM roles.
Note: Be sure to stop writes to the original cluster during the migration. Otherwise, some data might not be backed up to the new cluster.
Confirm the IAM roles
- Open the Amazon Redshift console, and then choose CLUSTERS on the navigation pane.
- Select the Amazon Redshift cluster that you want to move.
- At the top of the page, choose the Actions dropdown list, and then choose Manage IAM roles.
- Note the IAM roles that are associated with your cluster. You'll associate these roles with the new cluster later.
Create a cluster subnet group
Create a cluster subnet group. For VPC, choose the ID of the VPC that you want to migrate the cluster to, and then add any associated subnets.
Take a manual snapshot of the source cluster
Create a manual snapshot. For Cluster identifier, choose the cluster that you want to migrate.
Restore the cluster to the new cluster subnet group
- Choose the snapshot that you created, choose Restore from snapshot, and then choose Restore to provisioned cluster.
- Configure the properties of the new cluster. By default, Amazon Redshift automatically selects the same properties as the source cluster. Be sure that these properties are different from the source cluster:
Virtual private cloud (VPC): the VPC that you want to migrate the cluster to
- Choose Restore.
Associate the IAM roles
- On the navigation pane, choose CLUSTERS, and then choose the new cluster.
- Choose the Actions drop-down list, and then choose Manage IAM roles.
- From Available IAM roles, choose the roles that are associated with the source cluster.
- Choose Add IAM role, and then choose Done.
After the snapshot is restored and the new cluster status changes to Available, follow these steps:
- Rename the old cluster (for example, "oldcluster-1").
- Rename the new cluster to the original cluster name (for example, "cluster-1").
- Resume write operations to the cluster from client applications.
- Delete the old cluster.