Answers: <p>Anything that "needs" to happen in a given time frame is not a candidate for spot instances, including spot blocks.</p>
  
  <p>Spot capacity is, by definition, surplus/idle capacity, subject to availability, so your spot block may simply fail to start, as capacity may not be available.  It is less expensive for exactly that reason -- AWS is selling surplus capacity for which no one is currently willing to pay more.</p>
  
  <p>Information about the pool of compute capacity that is currently flagged internally as eligible for participation in the spot market is not publicly accessible, and although it was possible to make some reasonable assumptions in the past about capacity based on signals you could obtain from the real-time pricing, the spot pricing algorithm was modified in 2017 in a way that largely masks those signals (and the change, in my opinion, was a good thing for any customer who was not aggressively gaming the system).</p>
  
  <p>Spot blocks are intended to run for a committed period of time, so they are less likely to be interrupted than other spot instances, but they can initially start up successfully and then subsequently be interrupted at any time.</p>
  
  <blockquote>
    <p>In rare situations, Spot blocks may be interrupted due to Amazon EC2 capacity needs. In these cases, we provide a two-minute warning before we terminate an instance, and you are not charged for the terminated instances even if you used them.</p>
    
    <p><a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-requests.html#fixed-duration-spot-instances" rel="nofollow noreferrer">https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-requests.html#fixed-duration-spot-instances</a></p>
  </blockquote>
  
Answers: CC BY-SA 4.0
Answers: 2019-05-26T17:35:21.813Z
Answers: 2019-05-26T17:35:21.813Z
Answers: Michael - sqlbot
Body: <p>Let's say we have a continuous process where each two hours we receive some data which has to be analysed by a fleet of workers on AWS EC2 instances which always complete their job within two hours (let's say normally within 90 minutes).</p>
  
  <p>What would be the most cost-effective solution in this case?</p>
  
  <ol>
  <li><p>Use Spot blocks with finite duration of 2 hours?</p></li>
  <li><p>Use fleet of reserved EC2 instances?</p></li>
  </ol>
  
  <p>Though spot blocks seem to be less expensive, I am concerned about their availability as data has to be processed immediately after receiving within the next 2 hours.</p>
  
Tags: <amazon-web-services><amazon-ec2>
Title: Spot block vs reserved instances
UserDisplayName: Andremoniy
ThreadText: # Spot block vs reserved instances
  
  (Asked by: username_0 on 2019-05-26)
  
  Let's say we have a continuous process where each two hours we receive some data which has to be analysed by a fleet of workers on AWS EC2 instances which always complete their job within two hours (let's say normally within 90 minutes).
  
  What would be the most cost-effective solution in this case?
  
  1. Use Spot blocks with finite duration of 2 hours?
  2. Use fleet of reserved EC2 instances?
  
  Though spot blocks seem to be less expensive, I am concerned about their availability as data has to be processed immediately after receiving within the next 2 hours.
  
  **Tags:** amazon-web-services, amazon-ec2
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-05-26. Score: 1 | Accepted answer
  
  Anything that "needs" to happen in a given time frame is not a candidate for spot instances, including spot blocks.
  
  Spot capacity is, by definition, surplus/idle capacity, subject to availability, so your spot block may simply fail to start, as capacity may not be available. It is less expensive for exactly that reason -- AWS is selling surplus capacity for which no one is currently willing to pay more.
  
  Information about the pool of compute capacity that is currently flagged internally as eligible for participation in the spot market is not publicly accessible, and although it was possible to make some reasonable assumptions in the past about capacity based on signals you could obtain from the real-time pricing, the spot pricing algorithm was modified in 2017 in a way that largely masks those signals (and the change, in my opinion, was a good thing for any customer who was not aggressively gaming the system).
  
  Spot blocks are intended to run for a committed period of time, so they are less likely to be interrupted than other spot instances, but they can initially start up successfully and then subsequently be interrupted at any time.
  
  > In rare situations, Spot blocks may be interrupted due to Amazon EC2 capacity needs. In these cases, we provide a two-minute warning before we terminate an instance, and you are not charged for the terminated instances even if you used them.
  >
  > <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-requests.html#fixed-duration-spot-instances>
  
  
  ---
  
  