- Newest
- Most votes
- Most comments
Hello.
Is it possible for you to share what kind of error occurs when connecting?
Also, when you say you are connecting from the outside, do you mean that you are making public access to RDS?
In that case, please also check whether any settings have been changed on the local network side (for example, the firewall used on the local network).
- RDS Instance Availability: Ensure the RDS instance is running and not in a rebooting or maintenance state.
- Database Logs: Look at the RDS logs (e.g., error logs) to see if there are any relevant messages or errors.
Database Parameters: Verify that no changes were made to the RDS parameter group that could impact network connectivity, such as changes to the tcp_keepalives_* parameters.
Look into Maintenance Events
- AWS Maintenance: Confirm if AWS has performed any maintenance or updates on the RDS instance recently that might have impacted connectivity.
Review AWS IAM and Access Control IAM Roles/Policies: Ensure that any IAM roles or policies associated with your RDS instance haven't been modified in a way that restricts access.
For more follow the links
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithParamGroups.html
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.IAM.html
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ListEvents.html
Thanks for you attention, Sandeep.
The RDS instance is running and been accessed from other clients, out of AWS. I didn't update the RDS instance before the connect connection of this specific remote client started to be refused.
The logs and events are showing only successful backup messages.
I didn't change any parameter in the RDS parameters group and I'm only one with access. Is there a way to know if AWS did change any parameter?
Relevant content
- asked a year ago
AWS OFFICIALUpdated 2 months ago- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago
Thanks for your attention, Riku.
This is the error message: “Cannot create PoolableConnectionFactory (Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.)”.
Yes, I mean out of AWS, accessing the public address of my RDS resource.
As the admin of the RDS resource, I didn't change the inbound rules. The IP address of the application remote server remain configured. From other computers, out of AWS too, I can access that specific RDS resource. The application remote server manager is telling me he didn't change anything too.