This message was deleted.

sparse-intern-71089

07/21/2021, 3:52 PM

This message was deleted.

bumpy-grass-54508

07/21/2021, 5:06 PM

i'm not sure what your use case it, but it sounds like you might want to use an AutoScalingGroup with Spot instances, instead of just using a spot request. you can create a

LaunchTemplate

and then a

AutoScalingGroup

that references the template. your ASG can say it wants X number of instances and will do its best to keep that many spot instances up and running (depending on your spot price limit which you can control). then when you delete the ASG it will also remove the instances it has under its control

bumpy-grass-54508

07/21/2021, 5:07 PM

then on top of that, the LaunchTemplate has

TagSpecifications

where you can specify certain tags that will get applied to the instances, the volumes, and the spot-instance-requests all seperately

bumpy-grass-54508

07/21/2021, 5:10 PM

i will say that for years i have been confused on the ever-converging set of features between

spot fleet

ec2-fleet

spot-requests

/ and

autoscaling groups

but for my current use cases, autoscaling groups (with spot instances) is the best option for me. instance weighting, keeping capacity at a certain amount, and using spot pricing make for a good time

great-sunset-355

07/22/2021, 9:45 AM

I do not have much experience with EC2 but I've learned that using AutoScaling group even for 1 instance is the best solution in most cases

☝️ 1

3 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.