By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

AWS Lambda not able to connect to public RDS instance

0

I have a public RDS instance running postgres. I can connect to it from my local host. The same function fails when I try to run it on lambda. The error I get is

***could not translate host name <RDS_HOST_NAME> to address: Name or service not known\n"

There is no VPC associated with the lambda function. I can connect using psq -h <RDS_HOST_NAME> from my machine. Could you please suggest on how to resolve this?

  • AWS-ADolganov
    3 years ago

    Are you using the public RDS endpoint as host name? (....<region>.rds.amazonaws.com)

  • taskmonk
    3 years ago

    Yes.. it is <dbname>.<...>.ap-south-1.rds.amazonaws.com

Topics
ServerlessComputeMigration & ModernizationAnalyticsDatabase
Tags
AWS LambdaAmazon Relational Database Service
Language
English
taskmonk
asked 3 years ago1.7K views
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.

profile picture
moritalous
answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content