Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Lambda RDS connection timed out – How to Troubleshoot

by | Jun 14, 2021

Wondering how to troubleshoot Lambda RDS connection timed out in AWS? We can help you.

Often our customers using AWS report to us that their AWS Lambda function receives connection timeout errors when it tries to access an Amazon Relational Database Service (Amazon RDS) DB instance.

Here at Bobcares, we handle requests from our customers to fix similar errors as a part of our Server Management Services. Today we will see how our Support Engineers do this for our customers.

How to troubleshoot Lambda RDS connection timed out

We will see the methods that our Support Techs follow to check both intermittent and consistent connection timeouts.

Troubleshoot intermittent and transient connection timeout errors

We must do the following as a basic thing when we receive intermittent and transient connection timeout errors.

1. Check for DNS errors

We must check and confirm whether there is any Domain Name System (DNS)-related errors.

If there are DNS errors, we must retry the DNS request using exponential backoff.

Before retrying the DNS request we must ensure that we are able to resolve the inbound and outbound endpoints.

Troubleshoot consistent connection timeout errors

We must do the following as a basic thing when we receive consistent connection timeout errors.

1. Check the Lambda function’s Amazon CloudWatch Logs

We must enable CloudWatch logging permissions to our Lambda function is not given already.

Then, review the function’s logs to identify specific connection timeout errors.

2. Check the VPC configuration

Private Databases:

We can do either of the following:

  • Keep the Lambda function in the same Amazon Virtual Private Cloud (Amazon VPC) as the database.
  • Create a VPC peering connection between the Amazon VPC that includes the function and the Amazon VPC that includes the database.

Public Databases:

  •  Route public traffic through a network address translation (NAT) gateway or NAT instance for functions in an Amazon VPC.
3. Check the security group rules

Private Databases:

We can add an inbound rule to the DB security group that allows traffic from the CIDR range of the VPC’s subnets or security group.

Public Databases:

We can add an inbound rule to the DB security group that allows traffic from the NAT gateway or NAT instance of the VPC.

4. Update the Lambda function handler

We can try Updating the Lambda function code so that the function opens the database connection outside of the function handler and doesn’t close the connection.

5. Connect using an EC2 instance

First, try connecting to Amazon Elastic Compute Cloud (Amazon EC2) instance with the same Amazon VPC configuration as the lambda function. Then, try connecting to the Amazon RDS DB instance from the EC2 instance.

6. Use Amazon RDS Proxy

We can create an Amazon Relational Database Service (Amazon RDS) Proxy endpoint for the RDS database to handle the database traffic from the Lambda function.

[Need assistance? We can help you]

 Conclusion

In short, we saw how our Support Techs troubleshoot Lambda RDS connection timed out issues for our customers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF