Production compute usage is nearly constant each month and will continue for a year.
The discount should remain flexible across compute services rather than being tied to one instance family.
Which purchasing model should be evaluated?
A Compute Savings Plan commits to a consistent hourly spend and can apply flexibly to eligible compute usage such as EC2 and Fargate.
Detailed explanation
Health checks are DNS monitoring and do not discount compute.
Health checks are DNS monitoring and do not discount compute.
Storage classes do not discount compute usage.
Storage classes do not discount compute usage.
A Compute Savings Plan can discount steady usage with more flexibility than a single instance-family commitment.
A Compute Savings Plan can discount steady usage with more flexibility than a single instance-family commitment.
It avoids a commitment discount despite predictable usage.
It avoids a commitment discount despite predictable usage.
Check official documentation
Compare the following points with the official documentation.
AWS Savings Plansの種類と適用範囲の公式説明を確認する。
What to confirm
安定利用と柔軟な計算割引をSavings Plansへ対応付けられる。
Key points
- Compute Savings Plans
- Commitment
- Compute discount
Notes
- Environment: AWS公式Savings Plansドキュメントの確認
- Confirm current AWS pricing and service behavior in the official documentation.
Foundation review
Steady demand
A predictable baseline can justify a commitment while retaining flexibility for the service or instance choice.
Commitment trade-off
The discount is exchanged for a usage commitment, so the forecast should be credible.