Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Move Amazon Redshift Cluster from one VPC to another VPC

by | Aug 11, 2021

Wondering how to move Amazon Redshift Cluster from one VPC to another VPC? We can help you.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see how to move the cluster from one Amazon VPC to another VPC.


Move Amazon Redshift Cluster from one VPC to another VPC

To do so, our Support Techs recommend the steps below:

  • Confirm the AWS IAM roles and configuration details of the source cluster

  1. We open the Amazon Redshift console, and from the navigation pane, we select CLUSTERS.
  2. Then we select the Amazon Redshift cluster to move.
  3. At the top of the page, from the Actions drop-down list, we select Manage IAM roles.
  4. We need to associate the IAM roles of the cluster with the new cluster later. So we make note of them.
  • Create a cluster subnet group

Our next step is to create a cluster subnet group. For VPC, we select the ID of the VPC where we want to migrate to.

After that, we add associated subnets if any.

  • Take a snapshot of the source cluster

Then we take a manual snapshot. For the Cluster identifier, we select the cluster that we want to migrate.

  • Restore the cluster to the new cluster subnet group

  1. We select the snapshot and then select Restore from the snapshot.
  2. Then we configure the properties of the new cluster. By default, it automatically selects the same properties as the source cluster.
    However, these properties are different from the source cluster:
    a) Cluster identifier
    b) Virtual private cloud (VPC): the VPC that we want to migrate the cluster to
  3. Finally, we select Restore.
  • Associate the IAM roles

  1. From the navigation pane, we select Clusters > New cluster.
  2. Then from the Actions drop-down list, we select Manage IAM roles.
  3. From Available IAM roles, we select the roles that associate with the source cluster.
  4. After that we Add IAM role > Done.

Once we restore the snapshot and the new cluster status changes to Available, we follow these steps:

  1. Initially, we rename the old cluster.
  2. Then we rename the new cluster to the original cluster name.
  3. We resume the write operations to the cluster from client applications.
  4. Eventually, we delete the old cluster.

[Need help to move your cluster? We’d be happy to help]



In short, we saw how our Support Techs move the Amazon Redshift Cluster from one VPC to another VPC.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.