AWS Lambda: org.apache.http.conn.ConnectTimeoutException

Question

My Lambda function is unable to download objects from within Lambda, I get the below exception.

My bucket name and key name are both correct. I tested them out by running the Lambda function from my local machine with a dummy main and the bucket/key it's attempting to download and it downloaded the object just fine.

The role the Lambda function is executing with has S3 Read-Only privileges.

I've tried increasing the socket timeout to 25 seconds, increased the max connections to 10 and still no luck.

Below is the top portion of the stacktrace (can't seem to copy/paste in a pretty format from AWS Cloudwatch). The only reference within my code stops at the

s3Client.getObject(bucket, key);

My s3Client object is created as follows:

private final AmazonS3Client s3Client = new AmazonS3Client();

Searches have come up with similar issues from years ago, which seemed to have something to do with a specific issue or incorrect authentication.

Any thoughts?

Below is the stacktrace:

com.amazonaws.http.AmazonHttpClient executeHelper INFO: Unable to execute HTTP request: Connect to <>:443 http://<>/54.231.112.64 failed: connect timed out

org.apache.http.conn.ConnectTimeoutException: Connect to <>:443 http://<>/54.231.112.64 failed: connect timed out at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:150) at

b.b3rn4rd · Accepted Answer · 2016-07-14 05:59:38Z

3

54.231.112.64 is a public ip address, did you create lambda function inside VPC ? if yes - make sure its in subnet with internet access through a NAT. Read more here

Connection to S3 requires a gateway or NAT instances. If you need internal access you could try to setup VPC endpoints.

edited Jul 14, 2016 at 5:59

answered Jul 14, 2016 at 5:47

b.b3rn4rd

8,8602 gold badges50 silver badges59 bronze badges

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

5 Comments

Brooks Over a year ago

Yeah! I put it inside a VPC because I intend on giving it access to an EC2 instance...never thought for a minute that would restrict access to AWS resources though. If you don't mind, I will edit your answer to include the URL I just found on the subject. Also, would you mind taking a stab at my other question? stackoverflow.com/questions/38342418/…

b.b3rn4rd Over a year ago

yep access to s3 requires NAT or IGW, however VPC has 'Endpoint' feature, that would allow internal access to s3

b.b3rn4rd Over a year ago

with seconds questions, I dunno mate, I'm fortunate to use python it's rarely use more than ~25mb per request

Brooks Over a year ago

If my function only needs access to EC2 and S3, does it still need a NAT with internet access? It seems these instructions are for setting it up with external access. I just created a VPC endpoint, per aws.amazon.com/blogs/aws/new-vpc-endpoint-for-amazon-s3 and now my Lambda function does not even get executed...

b.b3rn4rd Over a year ago

if your lambda needs access to EC2 and S3 I would put it in private subnet with internet access though NAT. However, if you don't want to bother with settign up NAT, VPC endpoint allows you to access S3 without going though the internet

Collectives™ on Stack Overflow

AWS Lambda: org.apache.http.conn.ConnectTimeoutException

1 Answer 1

5 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

5 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related