Thank you for including the information about the COST. Is like... you need a clock, but all they can provide is a complex Rolex with barometer and altitude measures where you have to struggle to read the time.
Thankyou, Yes, seems so but once you get the knowledge to operate that complex Rolex, everything seems so simple and understanding. And you will feel Iike you have an awesome Rolex.
I have the same project topic from my college - Propose and implement a Scheduler on AWS solution which canautomates the starting and stopping of Amazon Elastic Compute Cloud(Amazon EC2) and Amazon Relational Database Service (Amazon RDS)instances. But there is also some requirements for the project -- Solution Requirements: a) All resources required should be deployed in custom VirtualPrivate Cloud b) Solution must create the AWS Identity and AccessManagement (IAM) roles necessary to start and stopinstances. c) Scheduler should automatically add tags to all instances itstarts or stops. The solution also includes macros that allowyou to add variable information to the tags. d) Solution should have the ability to use SSM maintenancewindows defined in the same Region as the instances andstart and stop the instances for the maintenance window. e) Solution should monitor key performance metric and logs. --- So can you please tell me that your video is matching the same solution requirements or not ?
AWESOME. The following are the answers to your questions: a) For this you have to tweak the cloudformation template and choose the same VPC to create the AWS schedular resources. b) IAM roles required are created automatically. c) Scheduler adds the tags automatically (You can define custom tags to add while creating the scheduler using the cloudformation template) d) The current scheduler uses the AWS eventbridge and custom event rule to initiate the starting and stopping of the resources. e) You can use the cloudwatch metrics to view the metrics and logs of the each services involved in this operation. Please go through this doc once to get more insight. aws.amazon.com/solutions/implementations/instance-scheduler-on-aws/
Solid information and demo ... thanks !!! Also, the cost can drop significantly depending on the CloudFormation Scheduling Frequency (1 minute to 1 hr)
Thank you, yes you are right the cost can be dropped by increasing the Scheduling frequency but keep in mind if the changing of the time affects your use case.
Could you please upload a video regarding the explanation of template which was used for creating this stack. The template was very difficult to understand.
I have tried to explain it in this blog post. Hope it will help. medium.com/@deshdeepakdhobi/aws-instance-scheduler-start-stop-ec2-and-rds-instances-automatically-641cfe4786ac
If you start the instance outside the start or end time, the instance will be started till the next stop lap of time arrives. For example: If you have set up the instance stop time to be from 6:00 PM to 9:00 AM and someone started the server at 8:00 PM, then the server will remain in the start state only, and for it to be stopped automatically, it must reach the time of 6:00 PM of the next day. And similarly, it works for the Starting process also.
I want to set a stopper for this scheduler on a particular date how to do it? for Example, I want to start and stop an instance from 25 August to 31 August only. Thanks in advance.
Hello Chethan, Thank you for an awesome question. Yes, it is possible to do so using the AWS instance scheduler. I have included the answer for this on my blog site. Please scroll below this blog link finding the Questions section to find the answer. onecloudhelper.com/2021/07/11/aws-instance-scheduler-start-stop-ec2-and-rds-instances-automatically/ In case if there are any further queries on this, feel free to make me know.
Yes, we can do that using the "weekdays" option on the config table created by the Instnace scheduler template on dynamodb. Just add/remove the name of days in a week on which you want to perform the starting and stopping actions onto your instances. For example: If you want your instances to be performing no actions of start and stop at weekends, you can choose the weekdays option to be {"mon-sat"}. This means that there will be no actions performed on a day not mentioned i.e. Sunday. You can also choose a specific date in a month (that consists of a holiday) to skip the actions. For example: If there is a holiday in the month of November from 2 to 4. Then we can use the "months" and "monthdays" sections to do that. Please view the below link of mine on the Questions section on how to do so. medium.com/@deshdeepakdhobi/aws-instance-scheduler-start-stop-ec2-and-rds-instances-automatically-641cfe4786ac And please make me know if you have any further queries regarding this.
AWS instance scheduler is meant to stop and start the EC2 and RDS servers automatically at a specified time without manual intervention. For example, if you want to stop your EC2 server after office hours end and start the server before the office hour starts automatically. And how you are going to use it totally depends on your use case and requirement.
The instance scheduler is designed for the automation of the stopping and staring of the EC2 and RDS instances. If you want to implement patching to the running instance you can use the AWS Systems Manager Patch manager service for it. aws.amazon.com/blogs/mt/getting-started-with-patch-manager-and-amazon-ec2-systems-manager/
