Reserved Instance 完全指南

AWS 折扣
30-72%
vs On-Demand
Azure 折扣
36-75%
1-3年期
GCP CUD 折扣
57-70%
资源承诺
最小承诺期
1年
AWS 标准 RI

$ aws ec2 purchase-reserved-instance-offerings --instance-count 10

对于稳定运行的工作负载,Reserved Instance(RI)是省钱利器。但 RI 购买也有很多坑——选错类型、买错范围、承诺过长……都可能让你省了小钱丢了大钱。今天我们来聊聊怎么科学地买 RI。

RI 基础概念

Reserved Instance 本质上是一种"预付费折扣合同":

AWS RI 类型详解

1. Standard RI(标准预留实例)

2. Convertible RI(可转换 RI)

3. Scheduled RI(计划 RI)

付款选项对比

选项预付款折扣幅度风险
全预付(All Upfront)100%最高高(承诺锁定)
部分预付(Partial Upfront)约 30-50%中高
无预付(No Upfront)0%中等
财务建议: 如果你的现金流充足,全预付能获得最大折扣。但如果预算紧张,无预付也是好选择——省下的钱可以做其他投资。

RI 范围(Scope)选择

Regional vs AZ Scope

建议:优先选择 Regional,除非你需要保证特定 AZ 的容量。

何时买 RI?买多少?

1. 先 Right-Sizing,再买 RI

买 RI 之前,确保你的实例大小是合适的。买了一个过大的 RI 3 年,就是浪费了 3 年。

2. 覆盖率计算公式

RI Coverage = RI Hours / Total Hours
# 建议目标:
# - 稳定基线负载:70-80% coverage via RI
# - 波动负载:结合 Savings Plans

3. 购买时机

Azure Reserved Instances

Azure 的 Reserved Instances(RI)机制类似 AWS:

# Azure CLI 购买 RI
az reservation purchase \
  --plan "ComputeSg_1yr" \
  --sku "Standard_D2s_v3" \
  --location eastus \
  --quantity 2

GCP Committed Use Discounts (CUDs)

GCP 的 CUD 不同于 AWS RI:

gcloud compute commitments create comm-1 \
  --project=my-project \
  --resources=vcpu=64,memory=128GB \
  --plan 12-month

RI vs Savings Plans vs Spot 选择

场景推荐方案理由
稳定运行的数据库服务器Regional RI不能中断,需要稳定容量
Web 应用,有一定波动Savings Plans更灵活,覆盖计算密集型
批处理作业Spot + Savings Plans价格敏感,可接受中断
机器学习训练Compute Savings Plans按秒计费,灵活性高
开发测试环境On-Demand使用率低,不值得锁定

购买策略总结

Reserved Instance 是云成本优化的基础配置,用好了能帮你省下 30-72% 的计算费用!

$ share --net https://981263.xyz/S-003-Reserved-Instance-Purchase.html

Practical review before using this page

The S 003 Reserved Instance Purchase 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.