Wondering how to move the Amazon Redshift cluster into a different subnet? We can help you!
We often receive similar requests from our AWS customers as a part of our AWS Support Services.
Today, let’s see how our Support Engineers help our customers with moving the Redshift cluster into a different subnet.
Amazon Redshift cluster
An Amazon Redshift data warehouse is a set of computing resources called nodes, which together are called a cluster. When launching an Amazon redshift cluster, we will be provided with Amazon VPC, cluster subnet group, and Security group. Also, Amazon Redshift picks up random subnets from the associated cluster subnet group at the time of launching.
For moving an Amazon Redshift cluster into a different subnet, we should take a snapshot of the existing Redshift cluster and then restore the cluster from the snapshot. Also, make sure that there is only one subnet in the subnet group. If there is more than one subnet in the subnet group, then Amazon Redshift might not launch the cluster in the specified subnet.
Move Amazon Redshift cluster into a different subnet
Now, let’s see the steps followed by our Support Techs to move the Redshift cluster to another subnet.
- Firstly, log into the AWS Management Console and then open the Amazon Redshift console.
- Select CLUSTERS, Snapshots, then select Create snapshot.
- Then enter the properties of the snapshot definition, then click Create snapshot.
- After that, restore the cluster using the created snapshot.
- Disable the Use defaults settings under the Additional configurations option.
- Select the Properties tab and then select Network and security.
- Then select the subnet group that we want to use.
- Select Restore cluster from snapshot.
After that, our support Engineers follow the below steps to confirm which subnet and subnet groups are used by the Amazon Redshift cluster.
- Firstly, open the Amazon Redshift console.
- Then select the Clusters tab.
- Select the Amazon Redshift Cluster.
- Select the Properties tab and then select Network and security.
- The Network and security information shows which subnet group is used.
- From Connection details, we can see the node IP addresses and ranges of the subnet groups which helps us to verify the subnet.
Always consider the following points when moving the Amazon Redshift cluster into a different subnet:
- Set up the cluster group as a homogenous network. In a homogenous network setup, the subnets that reside in the group have the same networking rules. it also reduces the connectivity problems at the time of moving the Amazon Redshift cluster into a different subnet.
- Always make sure that there are sufficient IP addresses present in each subnet in a subnet group. If not the cluster may fail to launch. To solve this launch failure, we can delete any unused elastic network interfaces or, we can move the AWS resources into a different subnet.
[Need help with more AWS queries? We’d be happy to assist]
Conclusion
In short, today we saw how our Support Engineers help our customers to move the Amazon Redshift cluster into a different subnet.
