1 Answer
1
Hello, not sure if you already did this, but just including two instances (in your case lambda and rds) in the same subnet and the same security group doesn't open any communication ports - you need to define the specific security rules to open the DB port for communication.
If you want to keep them in the same security group, you'll have to create a self-referencing rule in this group with the right DB port to open (depending on your database engine) and indicating the source as the same security group.
Regards
answered 6 months ago
Relevant questions
Timeout error accesing MySql RDS from a Lambda function
asked 5 years agoBypass CORS policy on S3-hosted site connected to RDS database
asked 6 months agoPsycopg2 on AWS Lambda not connecting to RDS database
asked 8 months agoAWS Lambda not able to connect to public RDS instance
asked 5 months agoWhy can't I find my RDS database from my lambda function?
asked 6 months agoHandler error when connecting lambda function to RDS database
asked 6 months agoUnable to find database in RDS console
Accepted Answerasked 2 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 agoUnable to connect to RDS database
asked a year ago
Was Database created? What is the exact error message?
@SandeepVudata The database was created. The error message says "ERROR: Unexpected error: Could not connect to MySQL instance. (1049, "Unknown database 'database_name'")" I have my database connection in a try except block, and this is the exact error that is supposed to be thrown when I can't connect to the database. I am trying to connect by using pymysql.connect() with the endpoint, username, password, and db name as parameters, but the code can't find the name of the database even though it is correct.