Update nexus: fix conflicts and sync local changes
This commit is contained in:
Shen Wei
@@ -1,102 +1,102 @@
|
||||
---
|
||||
title: "CTP Topic 13 Cloud FinOps Micro Focus Policies best practices to optimize the costs"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- FinOps
|
||||
- Cost-Optimization
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 13_ Cloud FinOps_ Micro Focus Policies _ best practices to optimize the costs.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 13 Cloud FinOps Micro Focus Policies best practices to optimize the costs
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 13_ Cloud FinOps_ Micro Focus Policies _ best practices to optimize the costs.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** ✅ 已完成（Gemini 摘要）
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
本次云转型学习会议的主题是"Cloud FinOps: Micro Focus 政策与成本优化最佳实践"。由 PCG（Public Cloud Governance）团队的 Uday 和 Vinay 主讲。
|
||||
|
||||
### 核心内容
|
||||
|
||||
1. **PCG 服务分层**
|
||||
- **成本管理**：账单支付、showback/chargeback、预算管理
|
||||
- **成本优化**：组织级和账户级优化，包括购买 Reserved Instances 和识别未充分利用的资源
|
||||
- **治理与自动化**：集中式上线、策略开发、自动报告
|
||||
|
||||
2. **核心策略**
|
||||
- **可见性**：确保账单可见
|
||||
- **标签合规**：强制标签要求
|
||||
- **预算责任**：账户负责人负责控制在预算内
|
||||
- **集中管理**：集中管理 Reserved Instances 和 Savings Plans
|
||||
- **区域限制**：限制区域使用以优化成本、安全和管理
|
||||
|
||||
3. **安全策略**
|
||||
- 预安装 Godrails
|
||||
- 通过联合身份管理访问（MFA 即将推出）
|
||||
- 供应商告警重定向到安全团队
|
||||
- 账户负责人需提供公共分发列表（PDL）用于告警
|
||||
- Cloud Security Postal Management 工具正在实施
|
||||
|
||||
4. **最佳实践**
|
||||
- 使用计算器了解成本
|
||||
- 检查资源清单
|
||||
- 监控月度账单
|
||||
- **Cloud Health**：关键工具，提供资源清单、成本分析和月度账单洞察
|
||||
- 标准化实例类型：
|
||||
- M 系列：通用场景
|
||||
- T 系列：突发性工作负载
|
||||
- C 系列：计算密集型应用
|
||||
- R/X 系列：内存优化工作负载
|
||||
- 使用 Graviton 实例节省成本
|
||||
|
||||
5. **研发环境优化**
|
||||
- 使用突发性实例
|
||||
- 使用实例调度器
|
||||
- 使用 Spot 实例
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
- **PCG (Public Cloud Governance)**：公共云治理框架，提供工作负载放置、成本和优化指导
|
||||
- **Showback/Chargeback**：成本分摊机制
|
||||
- **Cloud Health**：云成本分析和监控工具
|
||||
- **Godrails**：预安装安全控制
|
||||
- **Reserved Instances / Savings Plans**：承诺计划用于成本优化
|
||||
- **Graviton**：AWS ARM 处理器，比 Intel 更便宜
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
- [ ] 了解 Cloud Health 工具的使用
|
||||
- [ ] 审查并标准化实例类型选择
|
||||
- [ ] 确保所有资源使用正确的标签
|
||||
- [ ] 探索 Graviton 实例用于兼容的工作负载
|
||||
- [ ] 在研发环境中实施实例调度器
|
||||
- [ ] 检查月度账单并识别优化机会
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> [!info]+ 交叉引用
|
||||
> [[ctp-topic-63-optimise-resource-cost-using-automation]] — 深入讲解自动化调度优化资源成本
|
||||
> [[ctp-topic-27-aws-instance-scheduler]] — AWS 实例调度器详解
|
||||
> [[ctp-topic-71-pcgs-guide-to-rightsizing-why-how-when]] — Rightsizing 最佳实践
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-15*
|
||||
---
|
||||
title: "CTP Topic 13 Cloud FinOps Micro Focus Policies best practices to optimize the costs"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- FinOps
|
||||
- Cost-Optimization
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 13_ Cloud FinOps_ Micro Focus Policies _ best practices to optimize the costs.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 13 Cloud FinOps Micro Focus Policies best practices to optimize the costs
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 13_ Cloud FinOps_ Micro Focus Policies _ best practices to optimize the costs.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** ✅ 已完成（Gemini 摘要）
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
本次云转型学习会议的主题是"Cloud FinOps: Micro Focus 政策与成本优化最佳实践"。由 PCG（Public Cloud Governance）团队的 Uday 和 Vinay 主讲。
|
||||
|
||||
### 核心内容
|
||||
|
||||
1. **PCG 服务分层**
|
||||
- **成本管理**：账单支付、showback/chargeback、预算管理
|
||||
- **成本优化**：组织级和账户级优化，包括购买 Reserved Instances 和识别未充分利用的资源
|
||||
- **治理与自动化**：集中式上线、策略开发、自动报告
|
||||
|
||||
2. **核心策略**
|
||||
- **可见性**：确保账单可见
|
||||
- **标签合规**：强制标签要求
|
||||
- **预算责任**：账户负责人负责控制在预算内
|
||||
- **集中管理**：集中管理 Reserved Instances 和 Savings Plans
|
||||
- **区域限制**：限制区域使用以优化成本、安全和管理
|
||||
|
||||
3. **安全策略**
|
||||
- 预安装 Godrails
|
||||
- 通过联合身份管理访问（MFA 即将推出）
|
||||
- 供应商告警重定向到安全团队
|
||||
- 账户负责人需提供公共分发列表（PDL）用于告警
|
||||
- Cloud Security Postal Management 工具正在实施
|
||||
|
||||
4. **最佳实践**
|
||||
- 使用计算器了解成本
|
||||
- 检查资源清单
|
||||
- 监控月度账单
|
||||
- **Cloud Health**：关键工具，提供资源清单、成本分析和月度账单洞察
|
||||
- 标准化实例类型：
|
||||
- M 系列：通用场景
|
||||
- T 系列：突发性工作负载
|
||||
- C 系列：计算密集型应用
|
||||
- R/X 系列：内存优化工作负载
|
||||
- 使用 Graviton 实例节省成本
|
||||
|
||||
5. **研发环境优化**
|
||||
- 使用突发性实例
|
||||
- 使用实例调度器
|
||||
- 使用 Spot 实例
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
- **PCG (Public Cloud Governance)**：公共云治理框架，提供工作负载放置、成本和优化指导
|
||||
- **Showback/Chargeback**：成本分摊机制
|
||||
- **Cloud Health**：云成本分析和监控工具
|
||||
- **Godrails**：预安装安全控制
|
||||
- **Reserved Instances / Savings Plans**：承诺计划用于成本优化
|
||||
- **Graviton**：AWS ARM 处理器，比 Intel 更便宜
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
- [ ] 了解 Cloud Health 工具的使用
|
||||
- [ ] 审查并标准化实例类型选择
|
||||
- [ ] 确保所有资源使用正确的标签
|
||||
- [ ] 探索 Graviton 实例用于兼容的工作负载
|
||||
- [ ] 在研发环境中实施实例调度器
|
||||
- [ ] 检查月度账单并识别优化机会
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> [!info]+ 交叉引用
|
||||
> [[ctp-topic-63-optimise-resource-cost-using-automation]] — 深入讲解自动化调度优化资源成本
|
||||
> [[ctp-topic-27-aws-instance-scheduler]] — AWS 实例调度器详解
|
||||
> [[ctp-topic-71-pcgs-guide-to-rightsizing-why-how-when]] — Rightsizing 最佳实践
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-15*
|
||||
|
||||
@@ -1,62 +1,62 @@
|
||||
---
|
||||
title: "CTP Topic 27 AWS Instance Scheduler"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Instance-Scheduler
|
||||
- Cost-Optimization
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 27_ AWS Instance Scheduler.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 27 AWS Instance Scheduler
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 27_ AWS Instance Scheduler.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** ✅ 已完成（Gemini 摘要）
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 本次会议由 Gustavo 主讲，重点介绍了 **AWS Instance Scheduler**。这是一项由 AWS 官方提供并由 CCOE（云卓越中心）集成在 Guardrails 部署方案中的成本优化工具。该方案的核心目标是通过自动化的定时任务来控制 EC2 和 RDS 实例的运行状态，从而降低非生产环境（如开发和测试环境）的云端成本。
|
||||
|
||||
> 在技术实现上，该方案基于 CloudFormation 部署，利用 CloudWatch Events 每 15 分钟（默认配置）触发一次 Lambda 函数。Lambda 函数会读取存储在 DynamoDB 中的调度配置（包括时区、工作时间和周期），并根据实例上的特定标签（Tags）来决定是否执行启动或停止操作。Gustavo 在演示中展示了如何通过设置 `Schedule` 和 `Period` 标签来关联不同的办公时间（如西雅图或英国办公时间）。
|
||||
|
||||
> 会议还深入探讨了几个关键的运营细节：首先，实例的关机行为必须设置为“停止（Stop）”而非“终止（Terminate）”以保留数据；其次，针对 RDS 实例，该工具能智能处理每七天一次的强制维护窗口，确保维护完成后实例能恢复到预期的调度状态。在问答环节，Gustavo 澄清了该工具是基于“时间表”而非“空闲率（Idle time）”触发的，并确认了通过 Guardrails，该功能已自动覆盖了公司内部绝大多数月消费超过 10 美元的 AWS 账号。
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
- **AWS Instance Scheduler**: AWS 官方提供的解决方案，用于自动启动和停止 EC2 及 RDS 实例以节省成本。
|
||||
- **Guardrails**: 公司 CCOE 团队实施的一套自动化合规与治理框架，Instance Scheduler 作为其中的成本控制组件被自动部署。
|
||||
- **CloudWatch Events**: 系统的触发器，按照预设的时间间隔（如 15 分钟）激活 Lambda 函数。
|
||||
- **DynamoDB Config Table**: 用于存储调度定义（Schedules）和周期定义（Periods）的数据库，是调度的逻辑核心。
|
||||
- **Tagging (标签化)**: 用户通过在实例上添加特定的标签（如 `Schedule`）来将其关联到预定义的调度逻辑。
|
||||
- **RDS Maintenance Window**: RDS 特有的维护窗口，Instance Scheduler 能够识别并配合该窗口，确保数据库在维护后正确关闭。
|
||||
- **Override Status**: 一种高级配置，允许管理员强制将实例保持在停止状态，即使在预设的启动时间内也不启动。
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> [!info]+ 交叉引用
|
||||
> [[AWS Guardrails Overview]] — 了解 Instance Scheduler 赖以部署的底层治理框架
|
||||
> [[Cloud Cost Optimization Strategies]] — 探讨除定时开关机外的其他云成本优化手段
|
||||
> [[AWS Lambda and Serverless Architecture]] — 深入理解本方案中使用的 Lambda 触发机制方式
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
---
|
||||
title: "CTP Topic 27 AWS Instance Scheduler"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Instance-Scheduler
|
||||
- Cost-Optimization
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 27_ AWS Instance Scheduler.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 27 AWS Instance Scheduler
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 27_ AWS Instance Scheduler.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** ✅ 已完成（Gemini 摘要）
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 本次会议由 Gustavo 主讲，重点介绍了 **AWS Instance Scheduler**。这是一项由 AWS 官方提供并由 CCOE（云卓越中心）集成在 Guardrails 部署方案中的成本优化工具。该方案的核心目标是通过自动化的定时任务来控制 EC2 和 RDS 实例的运行状态，从而降低非生产环境（如开发和测试环境）的云端成本。
|
||||
|
||||
> 在技术实现上，该方案基于 CloudFormation 部署，利用 CloudWatch Events 每 15 分钟（默认配置）触发一次 Lambda 函数。Lambda 函数会读取存储在 DynamoDB 中的调度配置（包括时区、工作时间和周期），并根据实例上的特定标签（Tags）来决定是否执行启动或停止操作。Gustavo 在演示中展示了如何通过设置 `Schedule` 和 `Period` 标签来关联不同的办公时间（如西雅图或英国办公时间）。
|
||||
|
||||
> 会议还深入探讨了几个关键的运营细节：首先，实例的关机行为必须设置为“停止（Stop）”而非“终止（Terminate）”以保留数据；其次，针对 RDS 实例，该工具能智能处理每七天一次的强制维护窗口，确保维护完成后实例能恢复到预期的调度状态。在问答环节，Gustavo 澄清了该工具是基于“时间表”而非“空闲率（Idle time）”触发的，并确认了通过 Guardrails，该功能已自动覆盖了公司内部绝大多数月消费超过 10 美元的 AWS 账号。
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
- **AWS Instance Scheduler**: AWS 官方提供的解决方案，用于自动启动和停止 EC2 及 RDS 实例以节省成本。
|
||||
- **Guardrails**: 公司 CCOE 团队实施的一套自动化合规与治理框架，Instance Scheduler 作为其中的成本控制组件被自动部署。
|
||||
- **CloudWatch Events**: 系统的触发器，按照预设的时间间隔（如 15 分钟）激活 Lambda 函数。
|
||||
- **DynamoDB Config Table**: 用于存储调度定义（Schedules）和周期定义（Periods）的数据库，是调度的逻辑核心。
|
||||
- **Tagging (标签化)**: 用户通过在实例上添加特定的标签（如 `Schedule`）来将其关联到预定义的调度逻辑。
|
||||
- **RDS Maintenance Window**: RDS 特有的维护窗口，Instance Scheduler 能够识别并配合该窗口，确保数据库在维护后正确关闭。
|
||||
- **Override Status**: 一种高级配置，允许管理员强制将实例保持在停止状态，即使在预设的启动时间内也不启动。
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> [!info]+ 交叉引用
|
||||
> [[AWS Guardrails Overview]] — 了解 Instance Scheduler 赖以部署的底层治理框架
|
||||
> [[Cloud Cost Optimization Strategies]] — 探讨除定时开关机外的其他云成本优化手段
|
||||
> [[AWS Lambda and Serverless Architecture]] — 深入理解本方案中使用的 Lambda 触发机制方式
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
|
||||
@@ -1,97 +1,97 @@
|
||||
---
|
||||
title: "CTP Topic 63 Optimise resource cost using automation"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Cost-Optimization
|
||||
- Automation
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 63_ Optimise resource cost using automation.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 63 Optimise resource cost using automation
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 63_ Optimise resource cost using automation.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** ✅ 已完成（Gemini 摘要）
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
本次云转型学习会议的主题是"使用自动化优化资源成本"。会议重点介绍了如何通过标准化、合理选择实例类型、利用承诺计划以及实施自动化调度等方式来降低云资源成本。
|
||||
|
||||
### 核心内容
|
||||
|
||||
1. **批准区域（Approved Region）**
|
||||
- 推荐使用特定的云区域（AWS: Oregon, North Virginia, Frankfurt, London, Sydney, Singapore）
|
||||
- 好处：提高安全性、标准化管理、便于成本优化
|
||||
|
||||
2. **实例类型选择**
|
||||
- 通用型：M6i/M6g (ARM Graviton 比 Intel 便宜 20-25%)
|
||||
- 经济型：T3/T4g (适合 R&D 开发测试环境)
|
||||
- 计算型：C 系列
|
||||
- 内存型：R 系列/X 系列
|
||||
- **关键示例**：同配置从 M 系列切换到 R 系列可节省 35% on-demand 价格
|
||||
|
||||
3. **承诺计划（Commitment Plans）**
|
||||
- 1年承诺：约 40% 折扣
|
||||
- 3年承诺：约 60-64% 折扣
|
||||
- 可结合 EDP 进一步降低成本
|
||||
|
||||
4. **存储优化**
|
||||
- GP2 迁移到 GP3：直接节省 20%
|
||||
- 及时删除未使用的 EBS 卷和快照
|
||||
- 避免过度分配存储空间
|
||||
|
||||
5. **自动化调度（Scheduler）**
|
||||
- 基于标签的 EC2/RDS 启动/停止
|
||||
- 潜在节省：如果每天只运行 10 小时，可节省 70% 成本
|
||||
- 支持不同时区的团队需求
|
||||
- 通过 Lambda + EventBridge 实现
|
||||
|
||||
### 演示环节
|
||||
|
||||
Pushka 演示了如何使用 Terraform 模块配置 scheduler，通过设置标签（如 `auto shutdown = yes`）实现实例自动停止。
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
- **批准区域**: 建议使用的云资源部署区域，有助于提高安全性、标准化管理和优化成本。
|
||||
- **实例类型选择**: 根据工作负载选择合适的实例家族（如M系列、T系列、C系列、R系列），以优化性能和成本。
|
||||
- **承诺计划**: 通过预先承诺使用云资源一段时间（如一年或三年），获得折扣价格。
|
||||
- **自动化调度**: 通过设置定时任务，自动启动和停止云资源，以节省非工作时间的资源成本。
|
||||
- **存储优化**: 通过选择合适的存储类型（如GP3替代GP2），及时清理无用存储，合理分配存储空间来降低存储成本。
|
||||
- **Graviton**: AWS 自研 ARM 处理器，比同规格 Intel 便宜 20-25%，已成熟用于生产环境
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
- [ ] 评估现有云资源的使用情况，确定可以迁移到批准区域的资源。
|
||||
- [ ] 分析不同工作负载的资源需求，选择合适的实例类型，并进行成本效益分析。
|
||||
- [ ] 评估现有云资源的使用率，考虑购买承诺计划以降低成本。
|
||||
- [ ] 在研发环境中实施自动化调度，设置定时任务自动启动和停止实例。
|
||||
- [ ] 定期清理未使用的存储卷和快照，优化存储成本。
|
||||
- [ ] 探索 Graviton 实例用于兼容的工作负载
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> [!info]+ 交叉引用
|
||||
> [[ctp-topic-XX-instance-types.md]] — 详细介绍不同实例类型的适用场景和成本效益。
|
||||
> [[ctp-topic-XX-ri-savings-plan.md]] — 深入讲解承诺计划的类型和选择策略。
|
||||
> [[ctp-topic-XX-scheduler-demo.md]] — 演示如何使用自动化调度工具来优化资源成本。
|
||||
|
||||
---
|
||||
|
||||
---
|
||||
title: "CTP Topic 63 Optimise resource cost using automation"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Cost-Optimization
|
||||
- Automation
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 63_ Optimise resource cost using automation.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 63 Optimise resource cost using automation
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 63_ Optimise resource cost using automation.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** ✅ 已完成（Gemini 摘要）
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
本次云转型学习会议的主题是"使用自动化优化资源成本"。会议重点介绍了如何通过标准化、合理选择实例类型、利用承诺计划以及实施自动化调度等方式来降低云资源成本。
|
||||
|
||||
### 核心内容
|
||||
|
||||
1. **批准区域（Approved Region）**
|
||||
- 推荐使用特定的云区域（AWS: Oregon, North Virginia, Frankfurt, London, Sydney, Singapore）
|
||||
- 好处：提高安全性、标准化管理、便于成本优化
|
||||
|
||||
2. **实例类型选择**
|
||||
- 通用型：M6i/M6g (ARM Graviton 比 Intel 便宜 20-25%)
|
||||
- 经济型：T3/T4g (适合 R&D 开发测试环境)
|
||||
- 计算型：C 系列
|
||||
- 内存型：R 系列/X 系列
|
||||
- **关键示例**：同配置从 M 系列切换到 R 系列可节省 35% on-demand 价格
|
||||
|
||||
3. **承诺计划（Commitment Plans）**
|
||||
- 1年承诺：约 40% 折扣
|
||||
- 3年承诺：约 60-64% 折扣
|
||||
- 可结合 EDP 进一步降低成本
|
||||
|
||||
4. **存储优化**
|
||||
- GP2 迁移到 GP3：直接节省 20%
|
||||
- 及时删除未使用的 EBS 卷和快照
|
||||
- 避免过度分配存储空间
|
||||
|
||||
5. **自动化调度（Scheduler）**
|
||||
- 基于标签的 EC2/RDS 启动/停止
|
||||
- 潜在节省：如果每天只运行 10 小时，可节省 70% 成本
|
||||
- 支持不同时区的团队需求
|
||||
- 通过 Lambda + EventBridge 实现
|
||||
|
||||
### 演示环节
|
||||
|
||||
Pushka 演示了如何使用 Terraform 模块配置 scheduler，通过设置标签（如 `auto shutdown = yes`）实现实例自动停止。
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
- **批准区域**: 建议使用的云资源部署区域，有助于提高安全性、标准化管理和优化成本。
|
||||
- **实例类型选择**: 根据工作负载选择合适的实例家族（如M系列、T系列、C系列、R系列），以优化性能和成本。
|
||||
- **承诺计划**: 通过预先承诺使用云资源一段时间（如一年或三年），获得折扣价格。
|
||||
- **自动化调度**: 通过设置定时任务，自动启动和停止云资源，以节省非工作时间的资源成本。
|
||||
- **存储优化**: 通过选择合适的存储类型（如GP3替代GP2），及时清理无用存储，合理分配存储空间来降低存储成本。
|
||||
- **Graviton**: AWS 自研 ARM 处理器，比同规格 Intel 便宜 20-25%，已成熟用于生产环境
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
- [ ] 评估现有云资源的使用情况，确定可以迁移到批准区域的资源。
|
||||
- [ ] 分析不同工作负载的资源需求，选择合适的实例类型，并进行成本效益分析。
|
||||
- [ ] 评估现有云资源的使用率，考虑购买承诺计划以降低成本。
|
||||
- [ ] 在研发环境中实施自动化调度，设置定时任务自动启动和停止实例。
|
||||
- [ ] 定期清理未使用的存储卷和快照，优化存储成本。
|
||||
- [ ] 探索 Graviton 实例用于兼容的工作负载
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> [!info]+ 交叉引用
|
||||
> [[ctp-topic-XX-instance-types.md]] — 详细介绍不同实例类型的适用场景和成本效益。
|
||||
> [[ctp-topic-XX-ri-savings-plan.md]] — 深入讲解承诺计划的类型和选择策略。
|
||||
> [[ctp-topic-XX-scheduler-demo.md]] — 演示如何使用自动化调度工具来优化资源成本。
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-15*
|
||||
@@ -1,51 +1,51 @@
|
||||
---
|
||||
title: "CTP Topic 71 PCG's guide to RightSizing, why, how when"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- RightSizing
|
||||
- Cost-Optimization
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 71_ PCG's guide to RightSizing, why, how _ when.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 71 PCG's guide to RightSizing, why, how when
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 71_ PCG's guide to RightSizing, why, how _ when.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
---
|
||||
title: "CTP Topic 71 PCG's guide to RightSizing, why, how when"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- RightSizing
|
||||
- Cost-Optimization
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 71_ PCG's guide to RightSizing, why, how _ when.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 71 PCG's guide to RightSizing, why, how when
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 71_ PCG's guide to RightSizing, why, how _ when.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
|
||||
@@ -1,40 +1,40 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529 160242-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- EC2
|
||||
- Cost-Optimization
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529_160242-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529 160242-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529_160242-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## EC2 Cost Optimization in AWS: Best Practices
|
||||
|
||||
Mike Dukes and Steele Taylor, AWS experts, presented a learning session on EC2 cost optimization, covering compute efficiency, Graviton usage, EC2 spot leveraging, and cost-effective container deployments. The session emphasized interactive participation and welcomed questions.
|
||||
|
||||
Efficiency in the cloud involves architectural best practices and leveraging AWS services and instance types for optimal workload performance. Technical advantages include high availability, elastic usage, and innovation adoption. Benefits include cost efficiency, leveraging purchase options, and reducing carbon footprint. *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.*
|
||||
|
||||
EC2 offers over 750 instance types tailored for various workloads. AWS's Nitro system enhances efficiency by externalizing network, storage, and security components. AWS Graviton processors provide price performance benefits. Purchase options include on-demand, savings plans, and spot instances, each suited for different workload types.
|
||||
|
||||
Graviton instances offer up to 40% better price performance than comparable x86 instances. Graviton is based on ARM64 and has extensive software support across Linux OS, ISVs, and open-source software, with sustainability benefits through reduced power consumption. AWS now offers the fourth version of Graviton. Graviton supports various instance types, including compute-optimized, memory-optimized, and general-purpose. AWS services like RDS, Aurora, and Lambda also support Graviton. Migrating to Graviton for services like RDS Aurora is relatively straightforward. *Graviton Free actually uses up to 60% less power consumption than comparable X86-based instances.*
|
||||
|
||||
EC2 Spot instances offer up to 90% discounts compared to on-demand pricing, leveraging spare capacity. Key considerations for Spot instances include fault tolerance, flexibility, and statelessness. Diversification across instance types and availability zones is crucial for Spot usage. Spot instances can be interrupted when capacity is needed for on-demand instances, with notifications provided before termination. Integrations with AWS services like autoscaling, EKS, and ECS support automated responses to interruptions.
|
||||
|
||||
Spot instances are suitable for web services, containers, HPC batch processing, big data, and CI/CD, while Graviton is beneficial for most of these except stateful services like databases. Spot and Graviton can be used together with containers, provided instance pools are not overly restricted.
|
||||
|
||||
Spot Invaders, a fault-tolerant chaos engineering game powered by EKS and EC2 Spot, demonstrates best practices for running resilient applications on EKS while optimizing costs. The game involves shooting aliens to simulate pod failures and whales to trigger spot interruptions, showcasing the ability to maintain service availability despite disruptions.
|
||||
---
|
||||
title: "Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529 160242-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- EC2
|
||||
- Cost-Optimization
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529_160242-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529 160242-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529_160242-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## EC2 Cost Optimization in AWS: Best Practices
|
||||
|
||||
Mike Dukes and Steele Taylor, AWS experts, presented a learning session on EC2 cost optimization, covering compute efficiency, Graviton usage, EC2 spot leveraging, and cost-effective container deployments. The session emphasized interactive participation and welcomed questions.
|
||||
|
||||
Efficiency in the cloud involves architectural best practices and leveraging AWS services and instance types for optimal workload performance. Technical advantages include high availability, elastic usage, and innovation adoption. Benefits include cost efficiency, leveraging purchase options, and reducing carbon footprint. *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.*
|
||||
|
||||
EC2 offers over 750 instance types tailored for various workloads. AWS's Nitro system enhances efficiency by externalizing network, storage, and security components. AWS Graviton processors provide price performance benefits. Purchase options include on-demand, savings plans, and spot instances, each suited for different workload types.
|
||||
|
||||
Graviton instances offer up to 40% better price performance than comparable x86 instances. Graviton is based on ARM64 and has extensive software support across Linux OS, ISVs, and open-source software, with sustainability benefits through reduced power consumption. AWS now offers the fourth version of Graviton. Graviton supports various instance types, including compute-optimized, memory-optimized, and general-purpose. AWS services like RDS, Aurora, and Lambda also support Graviton. Migrating to Graviton for services like RDS Aurora is relatively straightforward. *Graviton Free actually uses up to 60% less power consumption than comparable X86-based instances.*
|
||||
|
||||
EC2 Spot instances offer up to 90% discounts compared to on-demand pricing, leveraging spare capacity. Key considerations for Spot instances include fault tolerance, flexibility, and statelessness. Diversification across instance types and availability zones is crucial for Spot usage. Spot instances can be interrupted when capacity is needed for on-demand instances, with notifications provided before termination. Integrations with AWS services like autoscaling, EKS, and ECS support automated responses to interruptions.
|
||||
|
||||
Spot instances are suitable for web services, containers, HPC batch processing, big data, and CI/CD, while Graviton is beneficial for most of these except stateful services like databases. Spot and Graviton can be used together with containers, provided instance pools are not overly restricted.
|
||||
|
||||
Spot Invaders, a fault-tolerant chaos engineering game powered by EKS and EC2 Spot, demonstrates best practices for running resilient applications on EKS while optimizing costs. The game involves shooting aliens to simulate pod failures and whales to trigger spot interruptions, showcasing the ability to maintain service availability despite disruptions.
|
||||
|
||||
@@ -1,50 +1,50 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529 160242-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- EC2
|
||||
- Cost-Optimization
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529_160242-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529 160242-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529_160242-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
---
|
||||
title: "Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529 160242-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- EC2
|
||||
- Cost-Optimization
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529_160242-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529 160242-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Best practices for EC2 cost optimization in AWS - 20240529_160242-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
|
||||
@@ -1,52 +1,52 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions - Budget Control - 20240319 160204-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Budget-Control
|
||||
- FinOps
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions - Budget Control - 20240319_160204-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions - Budget Control - 20240319 160204-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions - Budget Control - 20240319_160204-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## Budget Control Automation
|
||||
|
||||
The SRE Core team (Daniela, Evan, and Alan) presented a learning session on budget control, a new automation providing detailed data to manage budgets and costs within AWS accounts. The session covered the new budget control's value, diagrams, detailed cost reports, AWS budget alerts/actions, and source identity implementation.
|
||||
|
||||
The budget control automation aims to address uncontrolled AWS account sprawl and unsustainable cost reduction efforts. It provides account owners with detailed alerts, including information on account spending and cost drivers, enabling them to identify areas for cost reduction. Enforcement will involve attaching an SCP to block new resource creation. The initial scope is limited to lab accounts, with other accounts continuing to receive standard out-of-budget alerts.
|
||||
|
||||
An example alert email includes account details, alert details, warning messages, and detailed reports. There are four types of email alerts: forecast, actual, severe, and enforcement. The alert flow includes forecast alerts at 100% threshold with no action, and actual alerts at 80%, 90%, 95%, and 98% thresholds with escalating recipient lists. At 100%, a severe or enforcement alert is triggered based on a scoring system, with enforcement initially via manual approval and later automated. Budget increases can be requested through an Oli workflow.
|
||||
|
||||
*The source identity must be tracked.* Challenges during development included tracking source identity, customizing AWS budget alerts, choosing an enforcement method (SCP), and providing a grace period before enforcement. Budgets are evaluated every eight hours, and disabled budget actions result in no spend control until the next month. Currently, 80 lab accounts exceed their budgets, and around 100 are expected to exceed 80% of their budget threshold.
|
||||
|
||||
The implementation will be gradual, starting with alerts only on April 1st. Manual enforcement will follow upon FinOps' approval, with automatic enforcement as the next step.
|
||||
|
||||
## Diagrams and Detailed Cost Reports
|
||||
|
||||
Daniel discussed diagrams and cost reports attached to email alerts, explaining their creation and content. Libraries for lambdas were created to improve code visibility and simplify deployment. The *top services of recent months* report helps managers understand cost drivers, showing the percentage of budget spent on specific services over time. The *top users of current months* diagram allows account owners to monitor daily spending by users. A detailed Excel report provides granular information on resource IDs, creators, and associated costs, separated by month.
|
||||
|
||||
*This is the first time that we were able to get to this level of granularity.* Data for the top services report is generated from Athena, while the user's diagram uses data from Cost Explorer.
|
||||
|
||||
## AWS Budget Alerts and Actions
|
||||
|
||||
Alan discussed the implementation of AWS budget alerts and actions. The AWS budget service is primitive in terms of customization, so the team had to parse the bodies of the emails received from it. The budget alert system sends messages to an SNS topic, which triggers a Lambda function. The Lambda extracts data from the email and uses it to create a more detailed message. The step function enriches the data with account information, budget details, and owner/manager contacts.
|
||||
|
||||
AWS allows actions to be applied based on alert thresholds. A budget action on 100% triggers either a severe or enforcement email, depending on the scoring system. If budget enforcement is enabled, an SCP is applied to block resource creation. The FINOPS group receives a notification and decides whether to apply the action immediately or negotiate with the account owner.
|
||||
|
||||
The scoring system and grace period calculations aim to avoid penalizing accounts that slightly exceed their budget near the end of the month. The scoring considers account size and proximity to the end of the month. Smaller accounts have a better grace period.
|
||||
|
||||
FinOps has classified accounts based on cost range. The budgets were last updated on February 23rd. The source identity attribute was implemented to track user activity within AWS accounts, even when assuming different roles. Federated logins use NetIQ access manager to authenticate users and provide access to AWS accounts. The source identity ensures that the original login identity is maintained across role changes, allowing CloudTrail and other services to track user activity accurately.
|
||||
---
|
||||
title: "Public Cloud Learning Sessions - Budget Control - 20240319 160204-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Budget-Control
|
||||
- FinOps
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions - Budget Control - 20240319_160204-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions - Budget Control - 20240319 160204-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions - Budget Control - 20240319_160204-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## Budget Control Automation
|
||||
|
||||
The SRE Core team (Daniela, Evan, and Alan) presented a learning session on budget control, a new automation providing detailed data to manage budgets and costs within AWS accounts. The session covered the new budget control's value, diagrams, detailed cost reports, AWS budget alerts/actions, and source identity implementation.
|
||||
|
||||
The budget control automation aims to address uncontrolled AWS account sprawl and unsustainable cost reduction efforts. It provides account owners with detailed alerts, including information on account spending and cost drivers, enabling them to identify areas for cost reduction. Enforcement will involve attaching an SCP to block new resource creation. The initial scope is limited to lab accounts, with other accounts continuing to receive standard out-of-budget alerts.
|
||||
|
||||
An example alert email includes account details, alert details, warning messages, and detailed reports. There are four types of email alerts: forecast, actual, severe, and enforcement. The alert flow includes forecast alerts at 100% threshold with no action, and actual alerts at 80%, 90%, 95%, and 98% thresholds with escalating recipient lists. At 100%, a severe or enforcement alert is triggered based on a scoring system, with enforcement initially via manual approval and later automated. Budget increases can be requested through an Oli workflow.
|
||||
|
||||
*The source identity must be tracked.* Challenges during development included tracking source identity, customizing AWS budget alerts, choosing an enforcement method (SCP), and providing a grace period before enforcement. Budgets are evaluated every eight hours, and disabled budget actions result in no spend control until the next month. Currently, 80 lab accounts exceed their budgets, and around 100 are expected to exceed 80% of their budget threshold.
|
||||
|
||||
The implementation will be gradual, starting with alerts only on April 1st. Manual enforcement will follow upon FinOps' approval, with automatic enforcement as the next step.
|
||||
|
||||
## Diagrams and Detailed Cost Reports
|
||||
|
||||
Daniel discussed diagrams and cost reports attached to email alerts, explaining their creation and content. Libraries for lambdas were created to improve code visibility and simplify deployment. The *top services of recent months* report helps managers understand cost drivers, showing the percentage of budget spent on specific services over time. The *top users of current months* diagram allows account owners to monitor daily spending by users. A detailed Excel report provides granular information on resource IDs, creators, and associated costs, separated by month.
|
||||
|
||||
*This is the first time that we were able to get to this level of granularity.* Data for the top services report is generated from Athena, while the user's diagram uses data from Cost Explorer.
|
||||
|
||||
## AWS Budget Alerts and Actions
|
||||
|
||||
Alan discussed the implementation of AWS budget alerts and actions. The AWS budget service is primitive in terms of customization, so the team had to parse the bodies of the emails received from it. The budget alert system sends messages to an SNS topic, which triggers a Lambda function. The Lambda extracts data from the email and uses it to create a more detailed message. The step function enriches the data with account information, budget details, and owner/manager contacts.
|
||||
|
||||
AWS allows actions to be applied based on alert thresholds. A budget action on 100% triggers either a severe or enforcement email, depending on the scoring system. If budget enforcement is enabled, an SCP is applied to block resource creation. The FINOPS group receives a notification and decides whether to apply the action immediately or negotiate with the account owner.
|
||||
|
||||
The scoring system and grace period calculations aim to avoid penalizing accounts that slightly exceed their budget near the end of the month. The scoring considers account size and proximity to the end of the month. Smaller accounts have a better grace period.
|
||||
|
||||
FinOps has classified accounts based on cost range. The budgets were last updated on February 23rd. The source identity attribute was implemented to track user activity within AWS accounts, even when assuming different roles. Federated logins use NetIQ access manager to authenticate users and provide access to AWS accounts. The source identity ensures that the original login identity is maintained across role changes, allowing CloudTrail and other services to track user activity accurately.
|
||||
|
||||
@@ -1,50 +1,50 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions - Budget Control - 20240319 160204-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Budget-Control
|
||||
- FinOps
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions - Budget Control - 20240319_160204-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions - Budget Control - 20240319 160204-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions - Budget Control - 20240319_160204-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
---
|
||||
title: "Public Cloud Learning Sessions - Budget Control - 20240319 160204-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Budget-Control
|
||||
- FinOps
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions - Budget Control - 20240319_160204-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions - Budget Control - 20240319 160204-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions - Budget Control - 20240319_160204-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
|
||||
@@ -1,42 +1,42 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318 170100-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Cost-Optimization
|
||||
- FinOps
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318_170100-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318 170100-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318_170100-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## Reducing Cloud Costs
|
||||
|
||||
Vinay from the FINOPS team presented a session on reducing cloud costs, focusing on workload and rate optimization. The session covered modernization, right sizing, and best practices for cost reduction.
|
||||
|
||||
### Workload Optimization via Modernization and Right Sizing
|
||||
|
||||
Modernization involves using newer generations of services, like EC2 instances. While there's a perception that newer instances are more expensive, the latest families are generally cheaper and offer better performance. *Whenever there's a new family launched by the hyperscale, the latest families are almost cheaper.* However, AWS has slightly changed its pricing model after M6, making M7 and M8 somewhat more expensive. Moving from Intel to AMD can save around 6-10% on on-demand prices for Windows and Linux workloads. Graviton instances can offer even greater savings (20-25% reduction in on-demand cost) for Linux workloads, combined with EDP discounts and commitment plans.
|
||||
|
||||
Upgrading storage from GP2 to GP3 offers a 20% direct cost benefit without downtime. For Amazon EKS clusters, upgrading to the latest versions is crucial to avoid extended support costs, which are significantly higher. *Rather than spending up unnecessary moment on the extended support, you can deploy additional four or five cluster, right.* Spot instances can provide up to 90% discount compared to on-demand, suitable for big data, CI/CD pipelines, web servers, and HPC.
|
||||
|
||||
Right sizing involves identifying the correct resource configuration for workload performance and capacity needs. The EC2 right sizing recommendation report captures CPU usage, memory, and network data to provide recommendations. Configuring instance schedules is useful for non-production environments, allowing instances to be powered on/off based on business hours, potentially reducing costs to 40% of on-demand prices. Identifying and deleting idle load balancers, unassociated elastic IPs, and underutilized EBS volumes are also key to cost savings. Old snapshots and CloudWatch logs also contribute to unnecessary costs. Using cheaper regions like Oregon or North Virginia can reduce costs if there are no specific regional requirements.
|
||||
|
||||
### Rate Optimization
|
||||
|
||||
Rate optimization involves commitment-based discounts. Hyperscalers offer discounts for committing to resource usage or spending for a term (1-3 years). There are two categories: resource-level commitment (better discount with limitations) and flexible commitment (standard discount with flexibility). AWS offers Savings Plans (EC2 and Compute) and reservations for various services like RDS, ElastiCache, and CloudFront.
|
||||
|
||||
The rate optimization workflow includes pre-work (right sizing), analysis (identifying workloads requiring 24/7 uptime), communication (sharing details with finance), approval (from account owner), and reporting (monitoring utilization). Only the Phenop's team can implement commitment plans. All commitment plans will be purchased with no upfront payment options only. The minimum transaction value is 5k per annum.
|
||||
---
|
||||
title: "Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318 170100-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Cost-Optimization
|
||||
- FinOps
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318_170100-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318 170100-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318_170100-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## Reducing Cloud Costs
|
||||
|
||||
Vinay from the FINOPS team presented a session on reducing cloud costs, focusing on workload and rate optimization. The session covered modernization, right sizing, and best practices for cost reduction.
|
||||
|
||||
### Workload Optimization via Modernization and Right Sizing
|
||||
|
||||
Modernization involves using newer generations of services, like EC2 instances. While there's a perception that newer instances are more expensive, the latest families are generally cheaper and offer better performance. *Whenever there's a new family launched by the hyperscale, the latest families are almost cheaper.* However, AWS has slightly changed its pricing model after M6, making M7 and M8 somewhat more expensive. Moving from Intel to AMD can save around 6-10% on on-demand prices for Windows and Linux workloads. Graviton instances can offer even greater savings (20-25% reduction in on-demand cost) for Linux workloads, combined with EDP discounts and commitment plans.
|
||||
|
||||
Upgrading storage from GP2 to GP3 offers a 20% direct cost benefit without downtime. For Amazon EKS clusters, upgrading to the latest versions is crucial to avoid extended support costs, which are significantly higher. *Rather than spending up unnecessary moment on the extended support, you can deploy additional four or five cluster, right.* Spot instances can provide up to 90% discount compared to on-demand, suitable for big data, CI/CD pipelines, web servers, and HPC.
|
||||
|
||||
Right sizing involves identifying the correct resource configuration for workload performance and capacity needs. The EC2 right sizing recommendation report captures CPU usage, memory, and network data to provide recommendations. Configuring instance schedules is useful for non-production environments, allowing instances to be powered on/off based on business hours, potentially reducing costs to 40% of on-demand prices. Identifying and deleting idle load balancers, unassociated elastic IPs, and underutilized EBS volumes are also key to cost savings. Old snapshots and CloudWatch logs also contribute to unnecessary costs. Using cheaper regions like Oregon or North Virginia can reduce costs if there are no specific regional requirements.
|
||||
|
||||
### Rate Optimization
|
||||
|
||||
Rate optimization involves commitment-based discounts. Hyperscalers offer discounts for committing to resource usage or spending for a term (1-3 years). There are two categories: resource-level commitment (better discount with limitations) and flexible commitment (standard discount with flexibility). AWS offers Savings Plans (EC2 and Compute) and reservations for various services like RDS, ElastiCache, and CloudFront.
|
||||
|
||||
The rate optimization workflow includes pre-work (right sizing), analysis (identifying workloads requiring 24/7 uptime), communication (sharing details with finance), approval (from account owner), and reporting (monitoring utilization). Only the Phenop's team can implement commitment plans. All commitment plans will be purchased with no upfront payment options only. The minimum transaction value is 5k per annum.
|
||||
|
||||
@@ -1,50 +1,50 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318 170100-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Cost-Optimization
|
||||
- FinOps
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318_170100-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318 170100-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318_170100-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
---
|
||||
title: "Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318 170100-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Cost-Optimization
|
||||
- FinOps
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318_170100-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318 170100-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Reducing Cloud Costs - 20250318_170100-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
|
||||
@@ -1,46 +1,46 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions-Storage Cost Optimization - 20240305 160037-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Storage
|
||||
- Cost-Optimization
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions-Storage Cost Optimization - 20240305_160037-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions-Storage Cost Optimization - 20240305 160037-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions-Storage Cost Optimization - 20240305_160037-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## Storage Cost Optimization
|
||||
|
||||
This session covers storage cost optimization best practices across various AWS storage services: Amazon EBS, Amazon EFS, Amazon FSx, and Amazon S3. It includes an optimization example from ADM.
|
||||
|
||||
Key points include choosing the right storage for your workload, considering API costs and data transfer costs in addition to price per gigabyte, and understanding the different tiers available within each service.
|
||||
|
||||
### Amazon EBS
|
||||
|
||||
EBS has SSD and HDD volumes. GP3 volumes are recommended as the default for general-purpose SSD due to being 20% more cost-effective than GP2. *With GP3, you can scale IOPS and throughput independently of the volume size.* For migration from GP2 to GP3, automation tools should be updated to create GP3 volumes by default. EBS snapshots have standard and archive tiers, with the archive tier offering 75% lower costs but higher restore times and a 90-day retention period. Automation via Data Lifecycle Management (DLM) or AWS Backup is recommended for managing snapshots, including setting retention policies and migrating to the archive tier.
|
||||
|
||||
### Amazon EFS and FSx
|
||||
|
||||
FSx considerations include data deduplication, compression, and tiering. EFS offers standard, one-zone, and infrequent access tiers, with lifecycle policies to move files between tiers. The infrequent tier has a minimum billable object size of 128KB. EFS archive is a new tier, similar to Glacier, with a 90-day minimum duration and a 128KB minimum billable object size. FSx for NetApp ONTAP has SSD and HDD tiers (capacity pool), with automatic tiering between them.
|
||||
|
||||
### Amazon S3
|
||||
|
||||
Choosing the right storage class is crucial for S3 cost optimization. S3 Standard is for frequently accessed objects, with no retrieval fees, minimum retention, or minimum billable object size. Glacier tiers (Instant Retrieval, Flexible Retrieval, Deep Archive) are for rarely accessed data, with varying retrieval times and costs. Intelligent Tiering automatically moves data between tiers based on access patterns, with no transition fees between tiers within Intelligent Tiering. *With intelligent hearing we can automatically move data from warmer to colder color storage tiers and it will be based on the object less access data.* Lifecycle policies can transition objects between tiers, expire non-current versions, and delete incomplete multi-part uploads. Data transfer charges should be considered, and PrivateLink can be leveraged to stay within the AWS network. Storage Lens, CloudWatch, S3 Inventory, and access logs can be used to monitor and optimize S3 usage.
|
||||
|
||||
### ADM Optimization Example
|
||||
|
||||
ADM migrated NetApp file shares from on-premises to AWS. The initial migration to OpenZFS was inefficient. A second migration to a self-managed NetApp on EC2 instances incurred high data transfer costs. The final migration to AWS FSx for NetApp ONTAP resulted in a 60% cost reduction.
|
||||
---
|
||||
title: "Public Cloud Learning Sessions-Storage Cost Optimization - 20240305 160037-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Storage
|
||||
- Cost-Optimization
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions-Storage Cost Optimization - 20240305_160037-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions-Storage Cost Optimization - 20240305 160037-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions-Storage Cost Optimization - 20240305_160037-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## Storage Cost Optimization
|
||||
|
||||
This session covers storage cost optimization best practices across various AWS storage services: Amazon EBS, Amazon EFS, Amazon FSx, and Amazon S3. It includes an optimization example from ADM.
|
||||
|
||||
Key points include choosing the right storage for your workload, considering API costs and data transfer costs in addition to price per gigabyte, and understanding the different tiers available within each service.
|
||||
|
||||
### Amazon EBS
|
||||
|
||||
EBS has SSD and HDD volumes. GP3 volumes are recommended as the default for general-purpose SSD due to being 20% more cost-effective than GP2. *With GP3, you can scale IOPS and throughput independently of the volume size.* For migration from GP2 to GP3, automation tools should be updated to create GP3 volumes by default. EBS snapshots have standard and archive tiers, with the archive tier offering 75% lower costs but higher restore times and a 90-day retention period. Automation via Data Lifecycle Management (DLM) or AWS Backup is recommended for managing snapshots, including setting retention policies and migrating to the archive tier.
|
||||
|
||||
### Amazon EFS and FSx
|
||||
|
||||
FSx considerations include data deduplication, compression, and tiering. EFS offers standard, one-zone, and infrequent access tiers, with lifecycle policies to move files between tiers. The infrequent tier has a minimum billable object size of 128KB. EFS archive is a new tier, similar to Glacier, with a 90-day minimum duration and a 128KB minimum billable object size. FSx for NetApp ONTAP has SSD and HDD tiers (capacity pool), with automatic tiering between them.
|
||||
|
||||
### Amazon S3
|
||||
|
||||
Choosing the right storage class is crucial for S3 cost optimization. S3 Standard is for frequently accessed objects, with no retrieval fees, minimum retention, or minimum billable object size. Glacier tiers (Instant Retrieval, Flexible Retrieval, Deep Archive) are for rarely accessed data, with varying retrieval times and costs. Intelligent Tiering automatically moves data between tiers based on access patterns, with no transition fees between tiers within Intelligent Tiering. *With intelligent hearing we can automatically move data from warmer to colder color storage tiers and it will be based on the object less access data.* Lifecycle policies can transition objects between tiers, expire non-current versions, and delete incomplete multi-part uploads. Data transfer charges should be considered, and PrivateLink can be leveraged to stay within the AWS network. Storage Lens, CloudWatch, S3 Inventory, and access logs can be used to monitor and optimize S3 usage.
|
||||
|
||||
### ADM Optimization Example
|
||||
|
||||
ADM migrated NetApp file shares from on-premises to AWS. The initial migration to OpenZFS was inefficient. A second migration to a self-managed NetApp on EC2 instances incurred high data transfer costs. The final migration to AWS FSx for NetApp ONTAP resulted in a 60% cost reduction.
|
||||
|
||||
@@ -1,50 +1,50 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions-Storage Cost Optimization - 20240305 160037-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Storage
|
||||
- Cost-Optimization
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions-Storage Cost Optimization - 20240305_160037-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions-Storage Cost Optimization - 20240305 160037-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions-Storage Cost Optimization - 20240305_160037-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
---
|
||||
title: "Public Cloud Learning Sessions-Storage Cost Optimization - 20240305 160037-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/05_FinOps"
|
||||
tags:
|
||||
- AWS
|
||||
- Storage
|
||||
- Cost-Optimization
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions-Storage Cost Optimization - 20240305_160037-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions-Storage Cost Optimization - 20240305 160037-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions-Storage Cost Optimization - 20240305_160037-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 05_FinOps
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
|
||||
Reference in New Issue
Block a user