Skip to content
#

spot-instances

Here are 78 public repositories matching this topic...

Saves up to 90% of AWS EC2 costs by automating the use of spot instances on existing AutoScaling groups. Installs in minutes using CloudFormation or Terraform. Convenient to deploy at scale using StackSets. Uses tagging to avoid launch configuration changes. Automated spot termination handling. Reliable fallback to on-demand instances.

  • Updated Jan 5, 2022
  • Go
bwagner5
bwagner5 commented Nov 17, 2020

NTH Queue-Processor should catch the ASG Launch Lifecycle Hook and complete it once the node has joined the k8s cluster successfully. Since ASG considers the instance ready when EC2 health checks pass rather than when it actually joins the k8s cluster, if ASG performs Launch-Before-Terminate, a node could be terminated before the new node is ready to go.

9e3fce0a
9e3fce0a commented Feb 2, 2022

Pretty frustrating trying to debug an issue only to have the EC2 instance self-destruct.

I've been manually applying this hack to the build.sh script, and it has worked really well for me. I figured I'd share it so that others may benefit...

--- templates/generated_vars_and_funcs.sh-dist	2022-02-02 03:13:55.177621726 +0000
+++ templates/generated_vars_and_funcs.sh	2022-02-02 03:18:
narenaryan
narenaryan commented Sep 9, 2021

Hi,

We are using terraform-aws-gitlab-runnner to spin up GitLab runners on our AWS account. As part of security auditing, there was a severe alert raised on this policy created by terraform module: https://github.com/npalm/terraform-aws-gitlab-runner/blob/develop/policies/instance-docker-machine-policy.json#L21

The problem lies with permitting IamPassrole action on all resources. As per

Improve this page

Add a description, image, and links to the spot-instances topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the spot-instances topic, visit your repo's landing page and select "manage topics."

Learn more