1 Answer
0
I had a similar problem, which I solved with the following steps.
I created a new RDS instance in the management console. At this time, I specified that a new VPC, subnet group, and security group be created as well.
In this case, a rule was created with the source IP "90.149.145.179/32" as an inbound rule for the security group. In this state, I could still connect from the local PC, but not from Lambda. When I changed the source IP to 0.0.0.0.0/0, I was able to connect from Lambda.
answered 5 months ago
Relevant questions
Issues connecting to Postgres RDS instance from within a VPC
asked 3 years agoFrom docker container need to connect RDS - Using Session Manager
asked a month agoHow can I connect Google Data Studio to an Private AWS RDS Postgres instance?
asked 3 months agoWhy can't I find my RDS database from my lambda function?
asked 6 months agoAWS Lambda not able to connect to public RDS instance
asked 5 months agoHow to access a public RDS instance from lambda without compromising on the security of RDS by putting an inbound rule for RDS Sg with source as 0.0.0.0/0 ?
Accepted Answerasked 4 months agoHandler error when connecting lambda function to RDS database
asked 6 months agoHow do I link my Amazon Connect instance to a Lambda function outside the contact flow with automation
asked 3 months agoCan't connect to an RDS Instance from Lambda (different account tough)
asked 2 years agoConnect to MemoryDB from Lambda
Accepted Answerasked 3 months ago
Are you using the public RDS endpoint as host name? (....<region>.rds.amazonaws.com)
Yes.. it is <dbname>.<...>.ap-south-1.rds.amazonaws.com