Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We had a odd issue today related to the security groups in our RDS.

All the sudden, without any changes from our end, our RDS instance's security group stopped working. No server was able to connect to the RDS for 30min.

To workaround the issue, I had to enter the server's specific IP as an IP range in the security group. Once the IP was authorized, the server could connect again.

After awhile, I tried to remove the IP range from the RDS's security group and the sever could still connect. We haven't changed anything in the EC2 groups, so the old security group are set correctly.

Anyone noticed a similar issue?

share|improve this question

migrated from stackoverflow.com Jun 23 '11 at 3:45

This question came from our site for professional and enthusiast programmers.

    
How exactly are you setting the source on the existing security group? –  opsguy Aug 3 '11 at 1:18
    
Did the IP addresses that were connecting to RDS change? –  Drew Khoury Feb 9 at 0:23
add comment

1 Answer

Does DB Events show any issues with the RDS instance (such as a compute unit failure)? (http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ListEvents.html)

Perhaps the rules failed to propagate a needed to be forced via a rule modification. If an RDS instance an EC2 instance are in the same availability zone, the RDS endpoint will resolve to a Private IP address, and a CIDR authorization for an Elastic IP won't be valid for the network traffic. Instead, and EC2 authorization is best, unless you're crossing an account or region boundary, in which case CIDR is the only option and should use the EIP of the EC2 instance.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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