ingest: Public Cloud Learning Sessions - EC2 Cost Optimization AWS (2024-05-29)
Source: Cloud & DevOps/Public-Cloud-Learning-Sessions/05_FinOps/public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2.md Entities: Mike-Dukes, Steele-Taylor, Spot-Invaders Concepts: AWS-Nitro, EC2-Spot-Instances, ECS Concepts updated: Graviton, SpotInstances (added source reference)
This commit is contained in:
@@ -7,60 +7,54 @@ tags:
|
||||
- Cost-Optimization
|
||||
- Graviton
|
||||
- Spot-Instances
|
||||
date: 2026-04-14
|
||||
date: 2024-05-29
|
||||
---
|
||||
|
||||
## Source File
|
||||
- [[raw/Cloud & DevOps/Public-Cloud-Learning-Sessions/05_FinOps/public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2.md]]
|
||||
- [[Cloud & DevOps/Public-Cloud-Learning-Sessions/05_FinOps/public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]
|
||||
|
||||
## Summary(用中文描述)
|
||||
- 核心主题:AWS EC2 成本优化最佳实践
|
||||
- 问题域:云成本管理、FinOps、计算效率优化
|
||||
- 方法/机制:
|
||||
- AWS Nitro 系统外部化网络/存储/安全组件提升效率
|
||||
- Graviton ARM 处理器实例提供高达 40% 性价比提升
|
||||
- Spot 实例利用闲置容量提供高达 90% 折扣
|
||||
- 购买选项:On-Demand、Savings Plans、Spot Instances
|
||||
- 结论/价值:云效率优化需结合架构最佳实践 + 正确的实例类型选择 + 合适的购买选项
|
||||
- 核心主题:AWS EC2 成本优化最佳实践,涵盖实例选型、购买策略和容器化部署
|
||||
- 问题域:企业云成本管理(FinOps),如何在保证工作负载可用性的前提下最大化成本效益
|
||||
- 方法/机制:Graviton ARM 架构实例(40% 性价比提升)、EC2 Spot 竞价实例(90% 折扣)、AWS Nitro 虚拟化、Nitro Enclave 安全计算
|
||||
- 结论/价值:云效率的核心是"按使用量付费"——通过架构最佳实践和正确的实例购买策略,企业可显著降低 EC2 成本,同时提升性能和可持续性
|
||||
|
||||
## Key Claims(用中文描述)
|
||||
- Graviton 实例比同等 x86 实例提供高达 40% 更好的性价比
|
||||
- Graviton Free 功耗比同等 x86 实例减少高达 60%
|
||||
- EC2 Spot 实例提供高达 90% 的按需定价折扣
|
||||
- Spot + Graviton + 容器可实现最大化成本节省(适用于 Web 服务、容器、HPC 批处理、大数据和 CI/CD)
|
||||
- Spot 实例可与 EKS/ECS 自动扩展集成,支持自动响应中断
|
||||
- AWS 云效率原则:按实际使用量付费,只有在使用 AWS 时才支付成本
|
||||
- Graviton 实例:基于 ARM64 架构,性价比最高比同类 x86 实例高 40%;功耗比同类 x86 实例低 60%
|
||||
- EC2 Spot 实例:相比按需定价最高可享 90% 折扣;适合容错、灵活、无状态的工作负载
|
||||
- Spot + Graviton 组合:Spot 和 Graviton 可同时用于容器化工作负载,只要不过度限制实例池
|
||||
- Spot 中断处理:AWS 提供中断前通知;集成 Auto Scaling、EKS、ECS 支持自动化响应中断
|
||||
|
||||
## Key Quotes
|
||||
> "When we start talking about architecting and using best practice efficiency in the cloud, you effectively only pay for what you use when you use AWS." — 云效率核心理念
|
||||
|
||||
> "Graviton Free actually uses up to 60% less power consumption than comparable X86-based instances." — Graviton 能效优势
|
||||
> "When we start talking about architecting and using best practice efficiency in the cloud, you effectively only pay for what you use when you use AWS." — Mike Dukes,AWS 云效率核心理念
|
||||
> "Graviton Free actually uses up to 60% less power consumption than comparable X86-based instances." — 演讲者,Graviton 能耗优势
|
||||
|
||||
## Key Concepts
|
||||
- [[Graviton]]:基于 ARM64 的 AWS 自研处理器,提供更高的每瓦性能,支持计算优化型、内存优化型和通用型实例
|
||||
- [[Spot Instances]]:利用 AWS 闲置容量的竞价型实例,提供高达 90% 的按需价格折扣
|
||||
- [[Nitro-System]]:将网络、存储和安全功能从 CPU 卸载到专用硬件,提升 EC2 实例效率
|
||||
- [[Savings Plans]]:AWS 承诺使用量的定价选项,提供低于按需价格的折扣
|
||||
- [[EC2-Purchase-Options]]:On-Demand(按需)、Savings Plans(节约计划)、Spot Instances(竞价实例)三种购买选项
|
||||
- [[FinOps]]:云财务管理实践,平衡云成本与业务价值
|
||||
- [[Graviton]]:AWS 基于 ARM64 架构的自研处理器,提供更高性价比和更低功耗(比 x86 低 60%)
|
||||
- [[EC2-Spot-Instances]]:利用空闲容量的竞价实例,最高可享 90% 折扣,需具备容错能力
|
||||
- [[AWS-Nitro]]:AWS 虚拟化平台,将网络、存储和安全组件外部化,提升效率
|
||||
- [[FinOps]]:云财务管理,平衡云成本与业务价值
|
||||
- [[Savings-Plans]]:AWS 预留实例计划,提供按需价格的折扣
|
||||
- [[EKS]]:Amazon Elastic Kubernetes Service,Spot 中断通知已集成
|
||||
- [[ECS]]:Amazon Elastic Container Service,支持 Spot 实例自动化管理
|
||||
|
||||
## Key Entities
|
||||
- [[AWS]]:亚马逊云服务提供商,提供 EC2 计算服务
|
||||
- [[Mike Dukes]]:AWS 专家,分享 EC2 成本优化实践
|
||||
- [[Steele Taylor]]:AWS 专家,分享 EC2 成本优化实践
|
||||
- [[Amazon-EKS]]:Elastic Kubernetes Service,Spot 实例可与 EKS 集成实现自动扩展
|
||||
- [[Amazon-ECS]]:Elastic Container Service,Spot 实例支持容器工作负载
|
||||
- [[Mike-Dukes]]:AWS 专家,演讲者,EC2 成本优化最佳实践主题
|
||||
- [[Steele-Taylor]]:AWS 专家,演讲者,EC2 成本优化最佳实践主题
|
||||
- [[AWS]]:Amazon Web Services,云服务提供商
|
||||
- [[Spot-Invaders]]:基于 EKS 和 EC2 Spot 的容错混沌工程游戏,展示 Spot 最佳实践
|
||||
|
||||
## Connections
|
||||
- [[public-cloud-learning-sessions-reducing-cloud-costs-20250318-170100-meeting-reco]] ← related_to ← [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]
|
||||
- [[ctp-topic-13-cloud-finops-policies]] ← extends ← [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]
|
||||
- [[ctp-topic-71-pcgs-guide-to-rightsizing]] ← extends ← [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]
|
||||
- [[ctp-topic-63-optimise-resource-cost-using-automation]] ← extends ← [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]
|
||||
- [[public-cloud-learning-sessions-eks-optimization-part-1-of-3-compute-optimization]] ← extends ← [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]
|
||||
- [[public-cloud-learning-sessions-eks-optimization-part-3-of-3-introduction-to-eks]] ← extends ← [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]
|
||||
- [[Graviton]] ← extends ← [[AWS-Nitro]](Graviton 实例运行于 Nitro 系统)
|
||||
- [[EC2-Spot-Instances]] ← extends ← [[EKS]](EKS 提供 Spot 中断通知集成)
|
||||
- [[EC2-Spot-Instances]] ← extends ← [[ECS]](ECS 支持 Spot 实例自动化管理)
|
||||
- [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]] ← relates_to ← [[FinOps]](同属 FinOps 系列会话)
|
||||
- [[Spot-Invaders]] ← demonstrates ← [[EC2-Spot-Instances]](游戏演示 Spot 最佳实践)
|
||||
|
||||
## Contradictions
|
||||
- 与 [[ctp-topic-14-octane-hub-on-aws]] 可能的冲突:
|
||||
- 冲突点:Graviton 对有状态服务(如数据库)的适用性
|
||||
- 当前观点:[[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]] 建议 Graviton 适用于大多数场景,但排除有状态服务如数据库
|
||||
- 对方观点:Octane Hub 案例中提到 MSSQL→Postgres 迁移,可能涉及对 Graviton 的进一步评估
|
||||
- 补充说明:[[ctp-topic-66-rds-vs-aurora]] 提到 Aurora PostgreSQL 迁移到 Graviton 相对简单,表明有状态服务也在逐步支持 Graviton
|
||||
- 与 [[ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co]] 可能的冲突点:
|
||||
- 冲突点:Graviton 适用场景
|
||||
- 当前观点(本来源):Graviton 适合大多数场景,有数据库类例外
|
||||
- 对方观点(CTP Topic 13):明确建议 RDS Aurora 迁移到 Graviton "相对简单"
|
||||
- 协调:两者并不真正冲突——CTP Topic 13 专注文档数据库场景的 Graviton 迁移,本来源强调的是通用指导;Aurora 属于可迁移类别,非"数据库例外"中的有状态高要求场景
|
||||
|
||||
Reference in New Issue
Block a user