A financial services startup is deploying two workloads on Amazon EC2. The first is a core transaction ledger database that must run continuously with predictable performance and cannot tolerate any service interruptions. The second is a high-throughput, containerized credit-scoring batch analysis job that is stateless, can be safely paused and resumed, and is scheduled to run overnight. Which two of the following EC2 pricing models should the company select to minimize costs for these workloads?
- Savings Plans to host the core transaction ledger database to benefit from reduced rates for a consistent amount of compute usage.Answer
- Spot Instances to run the credit-scoring batch analysis to take advantage of spare EC2 capacity at steep discounts.Answer
- COn-Demand Instances to run the credit-scoring batch analysis to prevent any interruption or termination of the overnight jobs.
- DDedicated Hosts to run the credit-scoring batch analysis to ensure complete physical isolation and the lowest possible hourly compute rate.
- EReserved Instances to host the credit-scoring batch analysis with a 3-year commitment to maximize cost savings for the batch workloads.
Answer
Savings Plans should be used for the core transaction ledger database to benefit from reduced rates for consistent usage, and Spot Instances should be used for the credit-scoring batch analysis to utilize spare compute capacity at a lower cost.
The correct pricing strategy uses Savings Plans for the continuous, steady-state transaction database, which provides a significant discount over On-Demand rates in exchange for a commitment to consistent compute usage. For the credit-scoring batch analysis, Spot Instances are the optimal choice because the job is stateless and can tolerate interruptions, allowing the company to run it at a fraction of the cost using spare capacity.
Step-by-Step Solution
Key Concept
Selecting the optimal Amazon EC2 pricing model based on workload characteristics (steady-state vs. fault-tolerant/intermittent).