Timeout while starting an EC2 instance from AWS Lambda using boto3

Question

I want to allow users to start an EC2 instance only when it is needed.

So I created a Lambda function to do just that:

import boto3

def lambda_handler(event, context):
    ec2 = boto3.resource('ec2', region_name='eu-central-1')
    return ec2.instances.filter(InstanceIds=['i-abc123']).start()

I've also added the following IAM permissions:

    {
        "Effect": "Allow",
        "Action": [
            "ec2:StartInstances"
        ],
        "Resource": "arn:aws:ec2:*"
    },
    {
        "Effect": "Allow",
        "Action": [
            "ec2:DescribeInstances"
        ],
        "Resource": "*"
    }

Problem is that when I execute the Lambda I get timed out.

BTW running the exact same code from an EC2 within the same VPC and same permissions, returns immediately.

Any idea?

Did you setup a proper IAM roles + user in Lambda docs.aws.amazon.com/lambda/latest/dg/setting-up.html You may need to do chnage your resource arn to " "arn:aws:ec2:accoun-id:user-name" The lamdba script also need specific user credential to determine the resources. — mootmoot
I configured the VPC of the lambda to be the same as the EC2 instance. — Michael
I setup the proper IAM role. Not sure how to set the user of the Lambda? — Michael

Jeff Learman Jeff Learman · Accepted Answer · 2016-04-27T18:14:58

If credentials were the problem, you would not get timeouts. More likely, you're using a small memory model, and boto takes lots of memory, even to do simple things. Try running with a larger memory model or longer timeout.

If this does turn out to be the issue, consider creating the ec2 resource in class initialization code or using a singleton pattern, so that subsequent invocations can use the same resource. However, be sure to set the function timeout so that it has enough time to do initialization as well as its normal duties, even if that doesn't seem to be necessary. If your function gets an error, the next run may include class init time.

Timeout while starting an EC2 instance from AWS Lambda using boto3

1 Answers