Bearse Feature - Start Stop Resource Schedules

The 0.1.0 release of the Start Stop feature introduces a massive code refactor to improve performance and reliability of the start-stop functionality with AWS infrastructure.

It also includes a new capability to define schedules for individual supported AWS resources not associated with cloudformation stacks.

Configuration

The following block contains an example of configuring AWS resources outside of cloudformation stacks to be managed by the start-stop feature.

{
  "name": "test-environment-1",
  "account": 123456789123,
  "interface_listener": "arn:aws:elasticloadbalancing:ap-southeast-2:123456789123:listener/app/testa-LoadB-1234/5678/9876",
  "stacks": [
    {
      "stack_name": "TestStack1",
      "start": "cron(0 5 * * ? *)",
      "stop": "cron(0 10 * * ? *)"
    },
    {
      "stack_name": "TestStack2",
      "start": "cron(0 6 * * ? *)",
      "stop": "cron(0 8 * * ? *)"
    }
  ],
  "resources": [
    {
      "AWS::EC2::Instance": [
        {
          "name": "i-123456789123",
          "start": "cron(0 10 * * ? *)",
          "stop": "cron(0 4 * * ? *)"
        },
        {
          "name": "i-987654321321",
          "start": "cron(0 7 * * ? *)",
          "stop": "cron(0 3 * * ? *)"
        }
      ]
    }
  ]
}

#Bearse