41

So, I just created the Amazon RDS account. And I started an instance of database.

The "endpoint" is:
abcw3n-prod.cbmbuiv8aakk.us-east-1.rds.amazonaws.com

Great! Now I try to connect to it from one of my other EC2 instances.

mysql -uUSER -pPASS -habcw3n-prod.cbmbuiv8aakk.us-east-1.rds.amazonaws.com

But nothing works and it just hangs.

I tried to ping it, and nothing works either. Nothing happens.

Do I need to change some settings?

42

By default RDS does not allow any connection that is not specified within the Security Group (SG). You can allow based on CIDR addressing or by Amazon account number which would allow any EC2 under that account to access it.

27

It is "just hanging" as you have not configured the firewall to accept mySQL connections from your other instance, as such the packet is being dropped at the firewall level, to resolve this you need to:

  1. head into your AWS console
  2. EC2 tab
  3. Note down the security group of your mySQL server (well call this SG-MYSQL for now)
  4. click security groups on the left of the console
  5. click your group in the center menu SG-MYSQL
  6. click inbound tab
  7. select mySQL from the list, add the details of your client server and save the rule

NOTE the source IP for the server will not be your elastic IP (in most cases anyway) you will have an internal ip on the device (ifconfig on linux will show you this).

  • 1
    I've done that on my EC2 server. I've opened all the standard ports. – Alex Apr 25 '11 at 20:20
  • 1
    I have no EC2 instance and my RDS couldn't connect to outside world until I did this. – Neutralizer Nov 22 '14 at 14:02
  • 1
    excellent point to use elastic IP! – user1641443 Mar 23 '15 at 9:42
  • 1
    Thanks for this. The walkthrough has made all the difference! – Mr T Feb 22 '16 at 22:18
  • 1
    Created an account at server fault just to upvote this. THANK YOU. – CaptainMarvel Aug 5 '17 at 22:25
6

A lot of talk here about security groups, but also check:

  • Do the associated Subnets seem properly configured?
  • Are the Subnets part of a Routing Group that seems properly configured (Internet Gateway specified, etc?)
  • Does the RDS say it's Publicly Accessible?
  • And of course check the RDS Security Group and EC2 Security Group
    • Don't forget your actual source IP may be an internal IP (if accessing internally via a VPC) or an external IP (which may be a router's IP, or an EC2 instance's Instance IP which is distinct from its Load Balancer / Elastic IP) -- to troubleshoot, you may try to allow access to all IPs and ports.

(The routing group was my problem; in creating a new subnet, I neglected to add it to a routing group with a gateway.)

  • To clarify: ALL the subnets you choose in the RDS subnet group should have routing tables that have the internet gateway specified. My issue was that two of the subnets I chose were my "private" subnets, that had a NAT gateway specified for outbound traffic rather than the internet gateway, and RDS happened to choose a server in one of those subnets. Refer to this article if you're not too familiar with routing: medium.com/@mda590/aws-routing-101-67879d23014d – timetofly Dec 29 '17 at 17:42
4

Fixed.

Had to grant access to it in the security groups under the DB...

  • 6
    Can you elaborate on what you did to grant access? – David Csonka Jun 22 '12 at 5:15
  • 1
    My database has a security group with one rule. Allow access from ANYWHERE to port 1433. I can't connect -_- – The Muffin Man May 29 '14 at 16:44
1

I had the same issue ;

  1. Security Groups > rds-launch-wizard (or any name that was choosen for the db SG)
  2. select the Inbound tab > edit
  3. add new role
  4. MySQL
  5. Source -> insert the aws vm ip (for ex: 12.3.14.80/32)

worked for me ...

0

In an attempt to open up security completely for testing before locking down access, both my database instance and my EC2 instance used the same security group, and both inbound and outbound port 3306 were configured to allow connections from Anywhere. The problem -- I was able to connect to Aurora from my notebook but oddly enough not from my EC2 instance, as if the EC2 instance wasn't Anywhere. The solution was to add another inbound mysql/Aurora rule and specify that same security group id as the source for inbound connections. My security group has a rule that refers to itself, and I can connect from either my notebook or my EC2 instance.

-3

mysql inbound rule should be like below

image this is the problem with security group.

  • 3
    Is there a reason you're bumping a five year old question to answer it with the same answer that's been there for years? Giving 0.0.0.0/0 access to 3306 isn't a great idea, either. – ceejayoz Dec 16 '16 at 14:12
  • i tried to show the user what they should change and how they can change, you know there are many users like me can not solve the problem by reading the above ans. it may not help you but there are user looking for this. you gave the down vote as it does not help you. – Nirmal Dhara Dec 16 '16 at 15:06
  • 3
    My downvote comes from saying people should open up MySQL to the entire internet. It's a dangerous approach. – ceejayoz Dec 16 '16 at 15:10
  • i got it. i just show the place where they can edit the security groups, they can choose from dropdown whatever they want. – Nirmal Dhara Dec 16 '16 at 15:13

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.