1 個回答
- 最新
- 最多得票
- 最多評論
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.
已回答 2 年前
相關內容
- 已提問 6 個月前
- 已提問 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
Are you using the public RDS endpoint as host name? (....<region>.rds.amazonaws.com)
Yes.. it is <dbname>.<...>.ap-south-1.rds.amazonaws.com