- Newest
- Most votes
- Most comments
Take a look at the subnet group into which the RDS instance has been provisioned. All of the subnets that comprise the subnet group must be public subnets - that is to say each of them needs to have an entry in its route table which whose destination is an Intenet Gateway.
If the subnet group has a mix of pubilc and non-public subnets then this could be where your problem is. Amazon Reachability Analyser may be able to help you here https://aws.amazon.com/blogs/database/troubleshoot-network-connectivity-to-amazon-rds-databases-using-vpc-reachability-analyzer/
if you're still having trouble after all this, further things to try are listed in these docs https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Troubleshooting.html https://repost.aws/knowledge-center/rds-cannot-connect
Relevant content
- asked 6 months ago
- asked 9 months ago
- asked 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 9 months ago