A large batch workload can be interrupted and retried, and its completion deadline has flexibility.
Reduce the compute price compared with On-Demand Instances.
Which choice is most appropriate?
Spot Instances use spare EC2 capacity at a discount and fit retryable, interruption-tolerant batch workloads when used with a queue or batch scheduler.
Detailed explanation
Root credentials do not control the Spot pricing model.
Root credentials do not control the Spot pricing model.
Lifecycle manages object storage and does not reduce compute execution time.
Lifecycle manages object storage and does not reduce compute execution time.
Spot pricing is suited to workloads that can tolerate interruption and retry.
Spot pricing is suited to workloads that can tolerate interruption and retry.
Using only On-Demand misses the discount opportunity for interruptible work.
Using only On-Demand misses the discount opportunity for interruptible work.
Check official documentation
Compare the following points with the official documentation.
Amazon EC2 Spot InstancesとAWS Batchの公式説明を確認する。
What to confirm
可用性要件が低いバッチへSpotを選び、中断時の再実行を設計できる。
Key points
- Spot Instances
- AWS Batch
- Interruption
- Retry
Notes
- Environment: AWS公式EC2・Batchドキュメントの確認
- Confirm current AWS pricing and service behavior in the official documentation.
Foundation review
Workload tolerance
Checkpointing, queues, and retries make batch work suitable for interruptible capacity.
Price versus certainty
Spot reduces cost but cannot provide the same continuity as committed or on-demand capacity.