Mysql – How to move RDS database to different VPC

amazon ec2amazon-rdsMySQLrds

I didn't select a VPC when creating a MySQL RDS database, so it created it inside an auto-generated "default" VPC. I'm now unable to add it to any of my pre-defined security groups, or access it from instances in my existing VPC. The obvious solution would be to relocate it to the proper VPC, but there doesn't seem to be any option to edit the VPC on the "Modify db instance" screen. Is there any way to select a different VPC, or is my only option to delete the db and re-create it inside the correct VPC?

Best Answer

Amazon has recently issued a press release announcing that you can now change the VPC for existing RDS instances:

You can now easily change the Amazon Virtual Private Cloud (Amazon VPC) used by your Amazon RDS DB instance. You can specify a new VPC for an existing DB instance deployed in Single-AZ configuration by using the Amazon RDS Management Console, the Amazon RDS API, or the AWS Command Line Tools. In addition, if you are running your DB instance on the EC2-Classic environment, you can switch to the EC2-VPC environment by modifying your existing DB instance. If your AWS account was created before 2013-12-04, you are potentially running RDS on the EC2-Classic environment.

This feature is available for all regions supported by Amazon RDS, and is available for all supported versions of MySQL, MariaDB, Microsoft SQL Server, Oracle, and PostgreSQL.

Note that this feature is only supported for DB instances running in Single-AZ deployment. If you would like to change the VPC environment of a DB instance in a Multi-AZ deployment, you can temporarily modify your instance to a Single-AZ deployment and then re-enable Multi-AZ once you have changed to the EC2-VPC environment.

Related Solutions

Can Amazon Elastic Beanstalk auto-scale Amazon RDS

Today we faced that problem.

We launched a mobile app that report continuously data to be saved in RDS MySQL, this resulted in a high performance impact, we were using db.t2.micro to take advantage the free tier.

I can confirm, Elastic Beanstalk does not autoscale RDS. However, the environment were re-configured and set other server for RDS, db.m3.medium, the process was smooth from the users, the database was able to continue serving read/write queries and the server was upgraded without downtime.

So, There is a way to perform a manual, but fast and easy scale, but there is not auto-scale.

Programatically, I think you can make some script to monitor your databases and do:

aws elasticbeanstalk --update-environment --environment-name <your-env-name> --option-settings Namespace=aws:rds:dbinstance,OptionName=DBInstanceClass,Value=db.m1.small

Mysql – Connect to MySQL EC2 Instance outside of VPC

You need to set the Security Group to allow inbound connections over port 3306 (or whatever port you configured) to your destination.

If it's from your workstation, then you would need to get your public IP (ie go to whatismyip.com) and allow that.

Example:
INBOUND:
3306 TCP from Destination 10.10.10.10/32

I would recommend NOT using 0.0.0.0/0 as that will allow ANYONE to access your MYSQL database.

If you're feeling adventurous, you can configure a site to site VPN from your office to the VPC and communicate over private IP's. This is the more secure and preferred method.

Best Answer

Related Solutions

Can Amazon Elastic Beanstalk auto-scale Amazon RDS

Mysql – Connect to MySQL EC2 Instance outside of VPC

Related Topic