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.

AWS Lambda to Turn off EC2

by | Sep 30, 2021

Wondering how to use AWS Lambda to Turn off EC2? We can help you.

Recently, one of our customers approached us to reduce his Amazon EC2 usage by stopping and starting the EC2 instances automatically.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see how our techs perform the same.

 

AWS Lambda to Turn off EC2

First and foremost, we need to get the IDs of the EC2 instances that we want to stop and start.

Then, to perform the task at regular intervals using Lambda, we do the following:

  • Create an IAM policy and execution role for the Lambda function

1. We create an IAM policy using the JSON policy editor.

Then we copy and paste the following JSON policy document into the policy editor:

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"logs:CreateLogGroup",
"logs:CreateLogStream",
"logs:PutLogEvents"
],
"Resource": "arn:aws:logs:*:*:*"
},
{
"Effect": "Allow",
"Action": [
"ec2:Start*",
"ec2:Stop*"
],
"Resource": "*"
}
]
}

2. After that, we create an IAM role for Lambda.

In addition, while we attach a permissions policy to Lambda, we make sure to choose the IAM policy we just created.

  • Create Lambda functions that stop and start the EC2 instances

1. Here, we select the Create function from the AWS Lambda console.

2. Then we select the Author from scratch.

3. Under Basic information, we add the following:

a) For Function name, we enter a name that identifies it as the function used to stop the EC2 instances. For example, “StopEC2Instances”.
b) Then for Runtime, we select Python 3.8.
c) Under Permissions, we expand Choose or create an execution role.
d) Then for the Execution role, we select Use an existing role.
e) Under the Existing role, we select the IAM role we created.

4. After that, we select the Create function.

5. Under Function code, we add the following code into the editor pane in the code editor (lambda_function).

This will stop the EC2 instances that we identify.

Example function code to stop EC2 instances:

import boto3
region = 'us-west-1'
instances = ['i-12345cb6de4f78g9h', 'i-08ce9b2d7eccf6d26']
ec2 = boto3.client('ec2', region_name=region)

def lambda_handler(event, context):
ec2.stop_instances(InstanceIds=instances)
print('stopped your instances: ' + str(instances))

Here, we need to change the region and instance, to our preference.

6. Under Basic settings, we set Timeout to 10 seconds.

7. Then we select, Deploy.

8. In order to create another function, we repeat steps 1-7.

However, we need to perform the following differently:

In step 3, we enter a different Function name. For example, “StartEC2Instances”.
In step 5, we copy and paste the following code into the editor pane in the code editor:

Example function code – starting EC2 instances

import boto3
region = 'us-west-1'
instances = ['i-12345cb6de4f78g9h', 'i-08ce9b2d7eccf6d26']
ec2 = boto3.client('ec2', region_name=region)

def lambda_handler(event, context):
ec2.start_instances(InstanceIds=instances)
print('started your instances: ' + str(instances))
  • Test the Lambda functions

1. To do so, on the AWS Lambda console, we select Functions.

2. Here, we can select one of the functions that we created.

3. Then we select, Test.

4. In the Configure test event dialog box, we select, Create new test event.

5. We can enter an Event name. Then, select Create.

6. Later, we select Test to run the function.

7. After that, we repeat steps 1-6 for the other function.

  • Create CloudWatch Events rules that trigger the Lambda functions

1. First, we open the Amazon CloudWatch console.

2. Then, under Events, we select Rules.

3. In here, we need to select, Create rule.

4. Similarly, under Event Source, we select Schedule.

5. Later we perform either of the following:

For Fixed rate of, we enter an interval of time in minutes, hours, or days.
For Cron expression, we enter an expression that tells Lambda when to stop the instances.

6. Under Targets, we select Add target.

7. Then we go to the Lambda function.

8. For Function, we select the function that stops the EC2 instances.

9. After that, we select, Configure details.

10. Under Rule definition, we do the following:

For Name, we enter a name to identify the rule.
For State, we select the Enabled check box.

11. Eventually, we select the Create rule option.

12. Finally, we need to repeat steps 1-11 to create a rule to start the EC2 instances.

However, in step 5, for Cron expression, we enter an expression that tells Lambda when to start the instances.

Then in step 8, for Function, we select the function that starts the EC2 instances.
And in step 10, under Rule definition, we enter a Name, such as “StartEC2Instances”.

[Stuck in between? We’d be glad to walk you out]

 

Conclusion

In short, we saw how our Support Techs use AWS Lambda to Turn off EC2.

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

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