cphill
cphill

Reputation: 5924

Unable to Add Security Group to RDS Instance

I am running into an issue trying to connect to my RDS database with Sequel Pro anywhere outside of the IP Address where the instance was created. I came to this conclusion after trying to connect to my db form two computers with the correct information and good Wi-fi, but I would get a time out error. As a result I followed the AWS instructions to setup a VPC security group with the following setup, MYSQL/Aurora - TCP - 3306 - *my IP address*. I thought this was all that needed to be done, but I'm still getting the error and I'm unsure how to connect the security group to my RDS instance despite reading the documentation. Can anyone help?

Upvotes: 3

Views: 3967

Answers (1)

comjf
comjf

Reputation: 414

The first step to identify the problem is to figure out where your RDS instance lies. Is it inside the VPC or is it in the classic network. This part is very important. Additionally, if it's inside the VPC, when creating it there should have been an option to enable public access or not.

After creating a new security group (I'd look at your current one and copy all the settings to your new one + the mysql access change like you have above). Simply go to the RDS console, click on the instance you want to modify, select actions, modify and adjust your security group.

If you don't have the public access enabled and you are in the VPC then you're options are more limited. You'd probably have to bridge your connection over an existing ec2 instance that can both reach the outside and the VPC. Or like I do, have a VPN into your VPC directly.

Sadly all of this is very dependent on your VPC design, and where things lie on your network diagram. If my answer isn't helpful enough, try and provide more information and I can revise.

Upvotes: 4

Related Questions