Auto-sync: 2026-04-20 00:02
This commit is contained in:
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions-Storage Cost Optimization - 20240305"
|
||||
type: source
|
||||
tags: [AWS, Storage, Cost-Optimization, FinOps]
|
||||
sources: []
|
||||
last_updated: 2026-04-19
|
||||
---
|
||||
|
||||
## Source File
|
||||
- [[raw/Cloud & DevOps/Public-Cloud-Learning-Sessions/05_FinOps/public-cloud-learning-sessions-storage-cost-optimization-20240305-160037-meeting.md]]
|
||||
|
||||
## Summary
|
||||
- 核心主题:AWS 存储服务成本优化最佳实践
|
||||
- 问题域:云成本优化、存储分层、存储服务选型
|
||||
- 方法/机制:存储类型选择、生命周期策略、数据分层、智能分层
|
||||
- 结论/价值:通过合理选择存储类型和使用生命周期策略可显著降低存储成本
|
||||
|
||||
## Key Claims
|
||||
- GP3 卷相比 GP2 成本降低 20%,且可独立扩展 IOPS 和吞吐量
|
||||
- EBS 快照归档层相比标准层成本降低 75%,但恢复时间更长,需保留 90 天
|
||||
- EFS 不频繁访问层最小计费对象大小为 128KB
|
||||
- S3 智能分层可自动根据访问模式将数据在不同存储层之间移动
|
||||
- ADM 迁移到 FSx for NetApp ONTAP 后成本降低 60%
|
||||
|
||||
## Key Quotes
|
||||
> "With GP3, you can scale IOPS and throughput independently of the volume size." — AWS Storage 最佳实践
|
||||
> "With intelligent tiering we can automatically move data from warmer to colder color storage tiers based on object access patterns." — S3 智能分层说明
|
||||
|
||||
## Key Concepts
|
||||
- [[EBS-GP3]]:通用型 SSD 卷,推荐作为默认存储类型,成本比 GP2 低 20%
|
||||
- [[EBS-Snapshot-Archive]]:EBS 快照归档层,成本比标准层低 75%
|
||||
- [[EFS-Inrequent-Access]]:EFS 不频繁访问层,适合很少访问的文件
|
||||
- [[S3-Intelligent-Tiering]]:S3 智能分层,自动根据访问模式移动数据
|
||||
- [[FSx-for-NetApp-ONTAP]]:AWS 文件存储服务,支持自动分层
|
||||
- [[Lifecycle-Policy]]:生命周期策略,自动转换存储层
|
||||
|
||||
## Key Entities
|
||||
- [[ADM]]:一家公司,通过多次迁移最终使用 FSx for NetApp ONTAP 实现 60% 成本降低
|
||||
- [[AWS]]:亚马逊云服务提供商
|
||||
|
||||
## Connections
|
||||
- [[EBS-GP3]] ← improves ← [[EBS-GP2]]
|
||||
- [[S3-Intelligent-Tiering]] ← implements ← [[Lifecycle-Policy]]
|
||||
- [[EFS-Inrequent-Access]] ← implements ← [[Lifecycle-Policy]]
|
||||
- [[FSx-for-NetApp-ONTAP]] ← extends ← [[AWS-FSx]]
|
||||
- [[ADM]] ← migrated_to ← [[FSx-for-NetApp-ONTAP]]
|
||||
|
||||
## Contradictions
|
||||
- 无
|
||||
Reference in New Issue
Block a user