Savings Plans 完全指南

EC2 SP 折扣
42-72%
vs On-Demand
Compute SP 折扣
40-70%
跨服务
灵活性
极高
Instance Family
期限
1/3年
承诺类型

$ aws savingsplans create-savings-plan

如果你觉得 Reserved Instance 太死板(锁定 1-3 年),Spot 又太冒险(随时中断),那么 Savings Plans 可能就是你要的"中间道路"。AWS 2019 年推出的 Savings Plans 比 RI 更灵活,但折扣依然诱人。

Savings Plans 三种类型

1. Compute Savings Plans(计算 Savings Plans)

最灵活的选项:

2. EC2 Instance Savings Plans(EC2 实例 Savings Plans)

专注于 EC2:

3. SageMaker Savings Plans

机器学习专用:

Savings Plans vs Reserved Instances 对比

对比维度Savings PlansStandard RIConvertible RI
灵活性高(Compute)
覆盖范围跨 instance family(Compute)固定类型+AZ可转换
折扣42-72%36-78%31-66%
付款选项全预付/无预付三种选项全预付/无预付
账户共享仅区域内可转让不可转让
Compute Savings Plans 是推荐给大多数用户的方案——灵活度最高,折扣也很可观。

何时选 Savings Plans vs RI?

选择 Savings Plans 的场景

选择 RI 的场景

如何购买 Savings Plans

# 查看可用的 Savings Plans
aws savingsplans describe-savings-plan-offerings \
  --filters region=us-east-1
# 创建 Compute Savings Plans
aws savingsplans create-savings-plan \
  --savings-plan-offering-id spoxxxxx

Savings Plans 使用技巧

1. 先 Right-Sizing,再买 Plans

Savings Plans 的折扣是基于承诺金额,不是基于你当前的使用量。所以:

2. 覆盖率计算

# 查看当前 Savings Plans 覆盖率
aws savingsplans describe-savings-plan-rates \
  --savings-plan-id sp-xxxxx

建议覆盖率:

3. 混合使用策略

最佳实践是用多种工具组合:

Savings Plans 计费机制

Savings Plans 工作流程:

  1. 你承诺支付每小时 $X
  2. 你的实际使用自动从 Savings Plans 扣除
  3. 如果使用量低于承诺,剩余容量浪费
  4. 如果使用量超过承诺,超出部分按 On-Demand 计费
建议: 承诺金额设为当前平均使用量的 70-80%,留 20-30% 作为弹性缓冲。

案例分析

假设你的 Web 应用平均使用 m5.xlarge 20 台,每台 $0.192/h:

最佳实践

Savings Plans 是云成本优化的"灵活盾牌"——既保持了灵活性,又锁定了相当不错的折扣!

$ share --net https://981263.xyz/S-003-Savings-Plans-Explained.html

Practical review before using this page

The S 003 Savings Plans Explained resource should be read together with the rest of Cloud Cost Optimization Dashboard, not as an isolated shortcut. Before acting on the page, write down the current baseline, the assumption you are making, and the result you expect to see. This makes the page more useful for comparison and reduces the chance of changing several variables at once.

For FinOps planning, cloud cost allocation, rightsizing, tagging governance, and monthly cost review, a good review habit is to separate stable facts from estimates. Stable facts might include dates, page URLs, account names, measured values, or the exact checklist items you completed. Estimates should be labeled as estimates and revisited later. If the result affects money, health, safety, compliance, or operational risk, use the page as preparation for a more careful review rather than as the final authority.

Common mistakes to avoid

Use this page as a planning reference before changing cloud accounts. Confirm pricing, contracts, and technical limits in the relevant provider console because cloud terms can change.