tvlk-dev Cost Optimization (part2)

Part1: https://tvlk.slack.com/files/U1LDZ08GL/FHUC0R6P2/tvlk-dev_Cost_Optimization

As mentioned in the previous post of tvlk-dev Cost Optimization part 1, we will change the behavior of the dailly stop-start schedule:

By default, all instances in tvlk-dev will be automatically registered to the daily stop-start schedule.
The schedule is as following:

Everyday at 12AM GMT+7, all instances will be stopped.
Every weekday at 8AM GMT+7, all stopped instances will be started. -> That means the instances will not be started at Saturday and Sunday morning.

If by any chance, you need your instances to run during the "off hours", you can use the new @new-sas-bot command to start your instances using ProductDomain or Service tag.

Ex1: @new-sas-bot start_instances {"ProductDomain":["xxx"]}
Ex2: @new-sas-bot start_instances {"Service":["xxxxx"]}

What you need to do:

If your service is running inside an ASG, you will need to modify your Minimum instance count setting into zero. Otherwise, your ASG will terminate the stopped instance.
If you want to put an exception on your instance to not included in the schedule, please update the list here and contact me @arief.halim. Please put your Service name (EC2 Service tag). I will wait until Tomorrow, 23 April 2019.