Helping people save money at scale on the @awscloud using EC2 Spot Instances as Principal Developer Advocate for EC2 Spot. Husband. Father. Having a blast.
@pepastach The service quota API should reflect accurate EC2 Spot limits, and you should be able to request increases as necessary with the same API. Let me know what you see. https://t.co/uPaYTEyZBu
@teresacarlson Thank you for being a great leader @teresacarlson! Very much enjoyed being a part of the AWS public sector team and supporting the mission! Best wishes on your next chapter.
It is time for us to plan what to build next! Please tell us what open source frameworks you want integrated with EC2 Spot Instances! https://t.co/wc0GKW9Vgx @awscloud#EC2Spot#SaveAtScale#SpotInstances
EC2 Spot customers have overwhelmingly told us that the best way for them to get started quickly is to see complete workload configuration examples in infrastructure as code templates for AWS CloudFormation and Hashicorp Terraform. @awscloud@HashiCorp#ec2spot#SpotInstances
Yep - you can generate complete infrastructure as code workload templates for some of the most popular services used with Spot Instances: Amazon EC2 Auto Scaling, Amazon EMR, AWS Batch, and Amazon EKS!
@TalawahTech@awscloud It has to do with the Spot Instance request being tied to a given Availability Zone. In theory you could delete all the capacity and launch into a different AZ using the same placement group, but that Spot Instance request couldn't move.
hello world. I'm a developer advocate for the @awscloud EC2 Spot team. My job is to help you save at scale on your compute costs. I'd love to hear how you are using Spot Instances today, or how we can help you save more with Spot. You can also reach me at [email protected].
@TalawahTech@awscloud Considering using EC2 Fleet, which will give you more flexibility when requesting Spot capacity. You can also use EC2 Fleet with placement groups: https://t.co/9OpDaIpe2P
@TalawahTech@awscloud Hi Marc, since a persistent Spot Instance request requires selecting an Availability Zone, that request can't be flexible to change Availability Zones if needed according to the other capacity in the placement group. That is why they cannot be combined.
This includes monitoring for rebalance recommendations, attempting to proactively launch replacement capacity for existing Spot Instances when they are at elevated risk of interruption, detaching from Elastic Load Balancing if necessary, and running lifecycle hooks as configured.
Thrilled to announce Capacity Rebalancing for EC2 Auto Scaling, a new feature for proactively managing the Amazon EC2 Spot Instance lifecycle in an Auto Scaling group: https://t.co/WCDh4sT41z @awscloud#EC2Spot#SpotInstances#Spot
Capacity Rebalancing for EC2 Auto Scaling provides a seamless and automated experience for maintaining desired capacity through the Spot Instance lifecycle.