Skip to content

Instantly share code, notes, and snippets.

@olivergeorge

olivergeorge/Makefile Secret

Created July 2, 2018 09:58
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save olivergeorge/d3d22e3d55d6f8b3179ff0bf4b49b149 to your computer and use it in GitHub Desktop.
Save olivergeorge/d3d22e3d55d6f8b3179ff0bf4b49b149 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Makefile
cloud-on:
aws autoscaling set-desired-capacity --auto-scaling-group-name og-condense-sandbox-Compute-XXX-TxAutoScalingGroup-XXX --desired-capacity 1
aws autoscaling set-desired-capacity --auto-scaling-group-name og-condense-sandbox-Compute-XXX-BastionAutoScalingGroup-XXX --desired-capacity 1
cloud-off:
aws autoscaling set-desired-capacity --auto-scaling-group-name og-condense-sandbox-Compute-XXX-TxAutoScalingGroup-XXX --desired-capacity 0
aws autoscaling set-desired-capacity --auto-scaling-group-name og-condense-sandbox-Compute-XXX-BastionAutoScalingGroup-XXX --desired-capacity 0
@miyamotosho
Copy link

Hi @olivergeorge, I was lucky to find this gist the other day and used it without any problem. Today I started just the compute instance with the scaling out command to deploy datomic ions, but this time I noticed that the auto scaling group got into the state of starting and terminating every 5 minutes. The reason for termination was that "an instance was taken out of service in response to a launch failure." After some firefighting on the EC2 management console, I gave up and recreated the CloudFormation stack. I'm puzzled why this has happened and plan to replicate the error when I have the time. Meanwhile, I leave my report here in case someone bumps into the same issue. Cheers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment