- #Aws auto shutdown ec2 instance how to#
- #Aws auto shutdown ec2 instance full#
- #Aws auto shutdown ec2 instance free#
Whatever role you run this script as the same role and inline permissions are created within IAM. In retrospect this is obvious, but it wasn't obvious to me when I started. It specifies only the role used to run the CloudFormation script, it makes no difference to the resources created or the role used when the lambda function runs. The Permissions / IAM role section of the CloudFormation template is a red herring - ie it's largely irrelevant.
#Aws auto shutdown ec2 instance how to#
I haven't spent the time to work out how to disable them, I just deleted it re-ran the Cloudformation template to reinstall.
Notification options: I found it useful to set up SNS notifications so I could validate it was working. Leave it as default, and be running as an administrator when you try to set up EC2 Scheduler. (second screen) Permissions - this is a red herring, see the section below. #Aws auto shutdown ec2 instance free#
Because the DynamoDB free tier doesn't expire most people are unlikely to be charged.
DynamoDB: settings are stored in DynamoDB. Default start/stop time: Default UTC time to start and stop the instances. Leave it at the default value unless you have a good reason, or need multiple installations. Custom Tag Name: this is the "key" of the tag you put against EC2 instance. It's just what it's called in CloudFormation. Stack Name: call it anything you like. Here's some of the most important parameters When you run the CloudFormation template you have to enter a lot of parameters. I doubt you'd use this on production though. That could more easily let you set up bulk tagging, which could be useful for having different settings for dev, test, and production. You can use the tag editor to bulk tag instances. You can convert UTC to your local time using this tool. Note that the word "late" can be any string, "late" has no special meaning. For example if you want an instance to start at 1500 UTC and stop at 2400 UTC on Tuesday, Thursday and Friday you enter the following. If you want to have specific instance started and stopped on a different schedule you append additional information to the tag key and value. To do this find your EC2 instance in the console, click tags, and create this tag The simplest case requires you to tag each EC2 instance you want to be started and stopped according to the schedule. You control which instances are started and stopped by tagging your instances. This is covered in the documentation here, but it's not as simple as it could be. The script controls EC2 instances in any region, but it runs in one region. Select the region you want the resources deployed to at the top of the console. Right now the direct link is here, but it could change. Start by going to this page and clicking "launch solution". You can read about the architecture here. It's deployed using a Cloudformation template, which also sets up the necessary IAM roles and policies. This tool is a Lambda Function that works with Cloudwatch Events and DynamoDB. If you have a question based on this please start your own question. Note : if you have feedback or corrections comments are appreciated. It's like the documentation has been written by an engineer who wrote the tool and knows everything about it, rather than a technical writer. While it's a great tool the documentation is somewhat vague and confusing. You can choose which instances get controlled, you and you can specify different start and stop times for each instance using tags. The tool allows you to define default start and stop times when you set the tool up, which you can change later. The guide below will still work, but it's probably better to look at the instance scheduler for new installations.ĪWS have a tool called EC2 Scheduler that gives you very flexible control over starting and stopping EC2 instances. It looks to be an enhancement of the EC2 Scheduler I describe below, with a few more features, but it's essentially the same thing. #Aws auto shutdown ec2 instance full#
AWS have released a tool called the " Instance Scheduler", including a full configuration guide which is linked from that page.
0 kommentar(er)
