Python request in AWS Lambda timing out

Question

I'm trying to make a http request from my AWS Lambda but it times out.

My code looks similiar to this:

import requests

def lambda_handler(event, context):
    print('Im making the request')
    request.get('http://www.google.com')
    print('I recieved the response')

But when I test this, I get a timeout.

The output is

Im making the request
END RequestId: id
REPORT RequestId: id    Duration: 15003.25 ms   Billed Duration: 15000 ms   Memory Size: 128 MB Max Memory Used: 18 MB  
2016-04-08T20:33:49.951Z id Task timed out after 15.00 seconds

So I know the issue isn't it not finding the request package, and it's running my python code. I just figure out why it times out on that request.

Did you enable VPC access for your Lambda function?

Mark B
– Mark B

2016-04-08 20:48:55 +00:00
Commented Apr 8, 2016 at 20:48 — Mark B
– Mark B, Commented Apr 8, 2016 at 20:48
Yep, VPC access enabled.

user133688
– user133688

2016-04-08 20:50:50 +00:00
Commented Apr 8, 2016 at 20:50 — user133688
– user133688, Commented Apr 8, 2016 at 20:50

Community · Accepted Answer · 2017-05-23 10:31:14Z

27

I encounter same timeout problem, the reason is below.

AWS document:

When you add VPC configuration to a Lambda function, it can only access resources in that VPC. If a Lambda function needs to access both VPC resources and the public Internet, the VPC needs to have a Network Address Translation (NAT) instance inside the VPC.

Maybe there are some error when you setting your VPC. I advice you can follow this blog to build NAT.

edited May 23, 2017 at 10:31

CommunityBot

11 silver badge

answered Feb 19, 2017 at 16:41

Jim

1,6083 gold badges23 silver badges34 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Nick Strupat · Accepted Answer · 2023-03-07 15:21:31Z

21

The default value for timeout in Lambda is 3 seconds = 3,000 milliseconds. Go to Advanced settings and add 5 min. This could be the only issue, if the timeout happens exactly at 3 seconds. All other errors would take something more or less than that.

edited Mar 7, 2023 at 15:21

Nick Strupat

5,0925 gold badges47 silver badges58 bronze badges

answered Sep 13, 2017 at 16:42

pyBomb

5094 silver badges7 bronze badges

2 Comments

Kenzo_Gilead Over a year ago

Welcome to StackOverflow and thanks for your help. You might want to make your answer even better by adding some explanation.

elshev Over a year ago

The steps are: In AWS Console go inside the Lambda function -> Click 'Configuration' tab -> click 'Edit' -> Set 'Timeout' to the necessary value.

Mark B · Accepted Answer · 2016-04-08 20:54:54Z

9

A Lambda function with VPC access will not have internet access unless you add a NAT gateway to your VPC. You should read the "Things to Know" section of the Lambda VPC support announcement.

If you've enabled VPC support for your Lambda function, but don't have a NAT gateway in your VPC, then your request is timing out trying to access the internet.

answered Apr 8, 2016 at 20:54

Mark B

203k27 gold badges339 silver badges332 bronze badges

3 Comments

user133688 Over a year ago

Added a NAT Gateway to the VPC and a route for 0.0.0.0 through that NAT but still missing something. Timeouts still occur.

John Rotenstein Over a year ago

I wonder if the NAT is still required if a Public Subnet is specified?

Mark B Over a year ago

Yes it is still required because the Lambda function doesn't get a public IP address.

apoclyps · Accepted Answer · 2016-09-23 13:17:37Z

5

You can increase the timeout period for the request by doing the following:

response = requests.get(url, timeout=60)

Also, you will need to increase the timeout period for your lambda function. To do this:

Open your lambda function in AWS
Select 'Configuration', then 'Advanced Settings'
Increase your time out period (up to 5 minutes)
Select 'Save'

Also, I believe 'request.get' should be 'requests.get'.

answered Sep 23, 2016 at 13:17

apoclyps

5315 silver badges9 bronze badges

Comments

Abhineetraj · Accepted Answer · 2017-12-12 19:06:49Z

1

By default, AWS Lambda has 3 seconds of timeout so if your code is running for more than 3 seconds, it will automatically timeout giving you this error.

You can increase the timeout for your lambda function to up to 5 mins (300 seconds - AWS may increase this limit in the future) and that should take care of the problem.

Plus your code should reflect requests.get instead of request.get

answered Dec 12, 2017 at 19:06

Abhineetraj

8591 gold badge7 silver badges9 bronze badges

2 Comments

Julio Marins Over a year ago

where can you do this? couldn't find the place

Chai Ang Over a year ago

The timeout is set in the lambda page for that function. If you scroll down, under Basic Settings.

Zebula · Accepted Answer · 2020-01-08 14:39:23Z

0

I had this issue as well. If you are running lambda outside of a VPC, make sure you are in a Region that supports SES. If the region doesn't support it the lambda functions are always going to fail.

answered Jan 8, 2020 at 14:39

Zebula

1

Comments

Ali · Accepted Answer · 2018-12-31 07:34:47Z

-1

I have configured VPC configuration in Lambda function and also added the NAT gateway, set the function time to 5 minutes.

Still the problem timed out after XX-- seconds existed. By setting context.callbackWaitsForEmptyEventLoop to false solved the problem for me.

edited Dec 31, 2018 at 7:34

Ali

2,7643 gold badges37 silver badges61 bronze badges

answered Dec 31, 2018 at 5:42

Brotherhood

72 bronze badges

1 Comment

Rene B. Over a year ago

does this also exist for Python as the question is about Python

Collectives™ on Stack Overflow

Python request in AWS Lambda timing out

7 Answers 7

Comments

2 Comments

3 Comments

Comments

2 Comments

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

Comments

2 Comments

3 Comments

Comments

2 Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related