1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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.
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 10 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
Are you using the public RDS endpoint as host name? (....<region>.rds.amazonaws.com)
Yes.. it is <dbname>.<...>.ap-south-1.rds.amazonaws.com