All geek questions in one place

What is the advantage of using Autoscaling Spot Fleet instead of AutoScaling spot pricing groups?

Amazon AWS recently released Auto Scaling for Spot Fleets ( https://aws.amazon.com/blogs/aws/new-auto-scaling-for-ec2-spot-fleets/ ). Auto Scaling groups have already allowed you to set the spot price to get Spot Instances at a discount instead of reserved instances.

As far as I could see, Spot Fleets let you define fleet throughput in terms of vCPUs by mixing different types of instances to achieve this. I do not think that this can be done using automatic scaling, as far as I know.

My use case is pretty simple: use Spot Fleets (or Auto Scaling with Spot instances) to increase the capacity of my cluster at a reduced price, while preserving the minimum necessary reserved instances just in case. I could duplicate my ASG, set a spot price, and I would, but apparently this functionality now also exists as part of Spot Fleets.

What is the advantage of one over the other? Are there any main reasons for switching?

+4
source share
3 answers

, , Spot: / , .

, , ECS, , .

: -, Spot Fleets CreationPolicies, ASG, WaitConditions, .

+2

Spot Fleet , , AZ . , ASG , .

, , , Spot Fleets , ASG. , .

, Spot Fleet , ASG, .

+3

Spot- vCPU, , - EC2.

But the spot fleet is not mature enough as an ASG. We cannot add tags to spot fleet instances from the user interface, so we had to write a script to take care of this. In addition, instances running SpotFleet do not support the kernel for initial code loading through CodeDeploy. To deploy the code for the first time, we had to create our own scripts and pass them as userdata.

+2
source

Source: https://habr.com/ru/post/1653793/

More articles:


All Articles