What does this AWS Solutions Implementation do?

This Solutions Implementation helps you control your AWS resource cost by configuring start and stop schedules for their Amazon Elastic Compute Cloud (Amazon EC2) and Amazon Relational Database Service (Amazon RDS) instances.

It also helps reduce operational costs by stopping resources that are not in use and starting resources when capacity is needed. For example, a company can use AWS Instance Scheduler in a production environment to automatically stop instances outside of business hours every day. If you leave all of your instances running at full utilization, this solution can result in reducing the instance utilization, which will reduce overall cost based on the schedules configured.

Click here for related content 

Benefits

Cross-account instance scheduling

This solution includes a template that creates the AWS Identity and Access Management (IAM) roles necessary to start and stop instances in secondary accounts.

Automated tagging

blank
AWS Instance Scheduler can automatically add tags to all instances it starts or stops. The solution also includes macros that allow you to add variable information to the tags.

Configure schedules or periods using Scheduler CLI

This solution includes a command line interface (CLI) that provides commands for configuring schedules and periods. The CLI allows customers to estimate cost savings for a given schedule.

Configure schedules or periods using SSM maintenance window

For EC2 instances, AWS Instance Scheduler can use SSM maintenance windows defined in the same Region as the instances, and start and stop the instances for the maintenance window.

AWS Solution Implementation overview

The diagram below presents the architecture you can automatically deploy using the solution's implementation guide and accompanying AWS CloudFormation template.

AWS Instance Scheduler | Architecture Diagram
 Click to enlarge

AWS Instance Scheduler architecture

1. The AWS CloudFormation template sets up an Amazon CloudWatch event at a customer-defined interval. This event invokes the AWS Instance Scheduler AWS Lambda function. During configuration, the user defines the AWS Regions and accounts, as well as a custom tag that AWS Instance Scheduler will use to associate schedules with applicable Amazon EC2 and Amazon RDS instances.

2. These values are stored in Amazon DynamoDB, and the Lambda function retrieves them each time it runs. You can then apply the custom tag to applicable instances.

3. During initial configuration of the Instance Scheduler, you define a tag key you will use to identify applicable Amazon EC2 and Amazon RDS instances. When you create a schedule, the name you specify is used as the tag value that identifies the schedule you want to apply to the tagged resource. For example, a user might use the solution’s default tag name (tag key) Schedule and create a schedule called uk-office-hours. To identify an instance that will use the uk-office-hours schedule, the user adds the Schedule tag key with a value of uk-office-hours.

AWS Instance Scheduler

Version 1.4.0
Release date: 04/2021
Author: AWS

Estimated deployment time: 5 min

Use the button below to subscribe to solution updates.

Note: To subscribe to RSS updates, you must have an RSS plug-in enabled for the browser you are using. 

Did this Solutions Implementation help you?
Provide feedback 
Video
Solving with AWS Solutions: AWS Instance Scheduler
Back to top 
Build icon
Deploy a Solution yourself

Browse our library of AWS Solutions Implementations to get answers to common architectural problems.

Learn more 
Find an APN Partner icon
Find an APN Partner

Find AWS certified consulting and technology partners to help you get started.

Learn more 
Explore icon
Explore Solutions Consulting Offers

Browse our portfolio of Consulting Offers to get AWS-vetted help with solution deployment.

Learn more