Need help?

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

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

How to change the VPC for an Amazon RDS DB instance

by | Aug 11, 2021

Wondering how to change the VPC for an Amazon RDS DB instance? We can help you!

As a part of our AWS Support Services, we often receive similar queries from our AWS customers.

Today, let’s see the steps followed by our Support Engineers to move the Amazon RDS DB instance from an Amazon VPC to a new VPC.
 

Change the VPC for an Amazon RDS DB instance

 
Moving the Amazon RDS DB instance to a new VPC requires a reboot of the instance because the DB instance moves from one network to another. So the proper network configurations such as subnet group, security group inbound rules, and Route tables should be done on the new VPC before moving the DB instance to the new VPC. Also, note that we must change the RDS DB instance’s subnet group to move it to the new VPC.

 

Steps to move Amazon RDS DB instance to a new VPC

 
Now, let’s see the steps followed by our Support Techs to change the VPC for an RDS DB instance.

  1. At first, log into the AWS Management Console and open the Amazon RDS console.

2. Select Subnet Groups and then select Create DB Subnet Group.

3. Then enter the details such as subnet name, description, and VPC ID.

4. Also, select the subnets required for the RDS DB instance and then click Create.

5. Select Databases and choose the DB instance and then click Modify.

6. Select the Subnet Group related to the new VPC under the section Network Security and then select the appropriate Subnet Group.

7. Click Continue and then select Apply Immediately.

8. Finally, review the details on the Modify DB Instance page, and then click Modify DB Instance.

This task may take some minutes to complete. To confirm that the task moved the DB instance to the new VPC by selecting the Events section in the Amazon RDS console.

Make sure to change the VPC during a planned change window outside the RDS weekly maintenance window as the DB instance is not accessible while moving to the new VPC.

Now, let’s discuss the cases for which we can’t change the VPC for an RDS DB instance:

  • We are unable to change the VPC for an RDS DB instance if it is in multiple Availability Zones. So we need to convert the RDS DB instance to a single Availability Zone. And move the instance to the new VPC and, then we can convert it back to a Multiple Availablity zone.

 

  • If the RDS DB instance is a read replica or it has read replicas then we can’t change the VPC. So we need to remove the read replicas and we can add back read replicas after moving the DB instance.

 

  • If the Availability Zones for existing and new VPCare different, the operation fails. The subnet group created in the new VPC must have subnets from the Availability Zone where the source database is running.

 

[Need help with more AWS queries? We’d be happy to assist]
 

Conclusion

 
To conclude, today we saw the steps followed by our Support Engineers to change the VPC for an Amazon RDS DB instance.

PREVENT YOUR SERVER FROM CRASHING!

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.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

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

Privacy Preference Center

Necessary

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]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

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
smartlookCookie

Marketing

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
1P_JAR, NID, DV
NID
hblid

Security

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.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF