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:
45
wiki/concepts/AWS-Nitro.md
Normal file
45
wiki/concepts/AWS-Nitro.md
Normal file
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: "AWS Nitro"
|
||||
type: concept
|
||||
tags:
|
||||
- AWS
|
||||
- EC2
|
||||
- Virtualization
|
||||
- Performance
|
||||
aliases:
|
||||
- Nitro
|
||||
- AWS Nitro System
|
||||
- Nitro Hypervisor
|
||||
last_updated: 2026-05-12
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
AWS Nitro 是 AWS 自研的专用虚拟化平台，通过将网络、存储和安全组件从主机处理器卸载到专用硬件（Nitro 卡），大幅提升 EC2 实例的效率和性能。
|
||||
|
||||
## Architecture
|
||||
|
||||
Nitro 系统由多个专用组件组成：
|
||||
- **Nitro Hypervisor**：轻量级 Type-1 hypervisor，负责 CPU 和内存虚拟化
|
||||
- **Nitro Card for VPC**：提供 ENI（Elastic Network Interface）和 VPC 网络
|
||||
- **Nitro Card for EBS**：提供 EBS 卷和网络存储
|
||||
- **Nitro Card for Instance Storage**：提供本地 NVMe 存储
|
||||
- **Nitro Enclaves**：提供隔离的执行环境（用于处理敏感数据）
|
||||
|
||||
## Benefits
|
||||
|
||||
- **性能提升**：减少虚拟化开销，提升网络和存储 I/O 性能
|
||||
- **更强的隔离性**：Nitro Enclaves 提供硬件级隔离的独立计算环境
|
||||
- **更高的安全性**：安全组件卸载到专用硬件，减少攻击面
|
||||
- **更大的实例灵活性**：支持更多实例类型和更大实例规格
|
||||
|
||||
## Graviton on Nitro
|
||||
|
||||
所有 Graviton 实例均运行于 Nitro 系统之上，享受 Nitro 带来的性能和安全优势，同时结合 ARM64 架构的成本效益。
|
||||
|
||||
## Related Pages
|
||||
|
||||
- [[Graviton]]：运行于 Nitro 的 ARM 处理器
|
||||
- [[EC2-Spot-Instances]]：可在 Nitro 实例上使用
|
||||
- [[FinOps]]：云成本优化
|
||||
- [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]
|
||||
64
wiki/concepts/EC2-Spot-Instances.md
Normal file
64
wiki/concepts/EC2-Spot-Instances.md
Normal file
@@ -0,0 +1,64 @@
|
||||
---
|
||||
title: "EC2 Spot Instances"
|
||||
type: concept
|
||||
tags:
|
||||
- AWS
|
||||
- EC2
|
||||
- Cost-Optimization
|
||||
- FinOps
|
||||
aliases:
|
||||
- Spot Instances
|
||||
- EC2 Spot
|
||||
- 竞价实例
|
||||
last_updated: 2026-05-12
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
EC2 Spot Instances（竞价实例）是 AWS 利用闲置计算容量提供的折扣实例，相比 On-Demand 价格最高可享 **90% 折扣**。当 AWS 需要回收容量时，Spot 实例会被中断，因此需要工作负载具备容错能力。
|
||||
|
||||
## Core Characteristics
|
||||
|
||||
- **折扣幅度**：比 On-Demand 价格低 60-90%
|
||||
- **中断机制**：AWS 可在需要时终止实例，提前 2 分钟发出 Spot 中断通知
|
||||
- **适用场景**：容错、灵活、无状态的工作负载
|
||||
|
||||
## Best Practices
|
||||
|
||||
### 工作负载要求
|
||||
- **容错（Fault Tolerance）**：应用需能处理实例中断
|
||||
- **灵活（Flexible）**：可接受不同实例类型
|
||||
- **无状态（Stateless）**：不依赖单点实例状态
|
||||
|
||||
### 策略
|
||||
- **跨实例类型多样化**：不过度限制实例池
|
||||
- **跨可用区分布**：提高可用性
|
||||
- **自动化中断响应**：集成 Auto Scaling、EKS、ECS
|
||||
- **Spot + On-Demand 组合**：核心组件用 On-Demand，可中断组件用 Spot
|
||||
|
||||
### EKS/ECS 集成
|
||||
- **EKS**：支持 Spot 中断通知，自动响应
|
||||
- **ECS**：支持 Spot 实例自动化管理
|
||||
- **Auto Scaling Groups**：配合 ASG 实现弹性
|
||||
|
||||
## Use Cases
|
||||
|
||||
- Web 服务（容错设计）
|
||||
- 容器化工作负载（配合 Spot Fleet）
|
||||
- HPC 批处理
|
||||
- 大数据分析
|
||||
- CI/CD 构建
|
||||
|
||||
## Spot + Graviton 组合
|
||||
|
||||
Spot 和 Graviton 可同时用于容器化工作负载，只要不过度限制实例池，即可获得双重成本优化（Spot 折扣 + Graviton 高性价比）。
|
||||
|
||||
## Related Pages
|
||||
|
||||
- [[Graviton]]：ARM 处理器，高性价比
|
||||
- [[FinOps]]：云财务管理
|
||||
- [[SavingsPlans]]：另一种成本优化购买选项
|
||||
- [[AWS-Nitro]]：底层虚拟化平台
|
||||
- [[Spot-Invaders]]：Spot 实例容错实践案例
|
||||
- [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]
|
||||
- [[ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co]]
|
||||
51
wiki/concepts/ECS.md
Normal file
51
wiki/concepts/ECS.md
Normal file
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: "Amazon ECS"
|
||||
type: concept
|
||||
tags:
|
||||
- AWS
|
||||
- ECS
|
||||
- Containers
|
||||
- Orchestration
|
||||
aliases:
|
||||
- ECS
|
||||
- Elastic Container Service
|
||||
- Amazon ECS
|
||||
last_updated: 2026-05-12
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Amazon ECS（Elastic Container Service）是 AWS 提供的完全托管式容器编排服务，用于在 AWS 上运行 Docker 容器。支持 Fargate（无服务器模式）和 EC2（自管理虚拟机模式）两种启动类型。
|
||||
|
||||
## Key Features
|
||||
|
||||
- **完全托管**：AWS 自动管理容器编排基础设施
|
||||
- **Fargate 启动类型**：无需管理服务器或集群
|
||||
- **EC2 启动类型**：对底层计算资源有更多控制
|
||||
- **与 AWS 服务深度集成**：IAM、VPC、CloudWatch、Spot 实例等
|
||||
|
||||
## Spot Instance Integration
|
||||
|
||||
ECS 与 EC2 Spot 实例深度集成：
|
||||
- 支持 Spot 实例池多样化
|
||||
- 支持 Spot 中断处理自动化
|
||||
- 可配合 Auto Scaling 实现弹性
|
||||
- Spot + Graviton 可实现双重成本优化
|
||||
|
||||
## ECS vs EKS
|
||||
|
||||
| 特性 | ECS | EKS |
|
||||
|------|-----|-----|
|
||||
| 控制复杂度 | 低（AWS 原生） | 高（Kubernetes 标准） |
|
||||
| 迁移性 | AWS 锁定 | 跨云可移植 |
|
||||
| 功能丰富度 | 基础够用 | 生态丰富 |
|
||||
| Spot 支持 | ✅ | ✅ |
|
||||
| 适用场景 | AWS 优先，简单需求 | 多云策略，复杂需求 |
|
||||
|
||||
## Related Pages
|
||||
|
||||
- [[EC2-Spot-Instances]]：Spot 实例集成
|
||||
- [[EKS]]：另一种容器编排选择
|
||||
- [[Graviton]]：可与 ECS 配合使用降低成本
|
||||
- [[FinOps]]：成本优化
|
||||
- [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]
|
||||
53
wiki/concepts/Graviton.md
Normal file
53
wiki/concepts/Graviton.md
Normal file
@@ -0,0 +1,53 @@
|
||||
---
|
||||
title: "Graviton"
|
||||
type: concept
|
||||
tags:
|
||||
- AWS
|
||||
- Cost-Optimization
|
||||
- ARM
|
||||
aliases:
|
||||
- Graviton
|
||||
- Graviton ARM
|
||||
- AWS Graviton
|
||||
last_updated: 2026-05-12
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Graviton 是 AWS 基于 ARM 架构自研的处理器，相比 Intel/AMD x86 实例提供更高的性价比（最高 40%）和更低的功耗（减少高达 60%）。
|
||||
|
||||
## Benefits
|
||||
|
||||
- **成本更低**：相比同等配置 Intel 实例便宜 20-25%
|
||||
- **能效更高**：功耗显著降低
|
||||
- **性能提升**：对于支持 ARM 的工作负载性能更好
|
||||
|
||||
## Instance Types
|
||||
|
||||
- **M系列**：通用型（M6g/M7g）
|
||||
- **T系列**：突发性（T4g）
|
||||
- **C系列**：计算型（C6g/C7g）
|
||||
- **R系列**：内存优化（R6g/R7g）
|
||||
- **X系列**：内存优化（X2gd）
|
||||
|
||||
## Compatibility
|
||||
|
||||
适用于大多数工作负载：
|
||||
- Web 服务
|
||||
- 容器化应用（EKS/ECS）
|
||||
- 大数据处理
|
||||
- CI/CD 构建
|
||||
- 机器学习推理
|
||||
|
||||
排除场景：
|
||||
- 有状态服务（某些数据库）
|
||||
- 需要特定 x86 指令的应用
|
||||
- Windows 工作负载
|
||||
|
||||
## Related Pages
|
||||
|
||||
- [[FinOps]]
|
||||
- [[SpotInstances]]
|
||||
- [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]：Mike Dukes 和 Steele Taylor 详解 Graviton 性价比优势（40% 提升）和能耗优势（60% 降低）
|
||||
- [[ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co]]
|
||||
- [[ctp-topic-63-optimise-resource-cost-using-automation]]
|
||||
40
wiki/concepts/SpotInstances.md
Normal file
40
wiki/concepts/SpotInstances.md
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: "Spot Instances"
|
||||
type: concept
|
||||
tags:
|
||||
- AWS
|
||||
- Cost-Optimization
|
||||
- FinOps
|
||||
aliases:
|
||||
- Spot Instances
|
||||
- Spot
|
||||
- 竞价实例
|
||||
last_updated: 2026-05-12
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Spot Instances（竞价实例）是 AWS 提供的按需计算容量，价格基于供需动态调整，可比 On-Demand 价格低 60-90%。适用于容错、可中断的工作负载。
|
||||
|
||||
## Use Cases
|
||||
|
||||
- 批处理作业
|
||||
- CI/CD 构建
|
||||
- 大数据分析
|
||||
- 机器学习训练
|
||||
- 容器化工作负载（配合 Spot Instance Interruption Handling）
|
||||
|
||||
## Best Practices
|
||||
|
||||
- 实现优雅关闭处理（Graceful Shutdown）
|
||||
- 使用 Spot Fleet 或 Spot Block（固定时间段）
|
||||
- 结合 Auto Scaling Groups 实现弹性
|
||||
- 与 On-Demand 或 Reserved Instances 配合用于核心工作负载
|
||||
|
||||
## Related Pages
|
||||
|
||||
- [[FinOps]]
|
||||
- [[Graviton]]
|
||||
- [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]：Mike Dukes 和 Steele Taylor 详解 Spot 最佳实践（含 Spot Invaders 案例）
|
||||
- [[ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co]]
|
||||
- [[ctp-topic-63-optimise-resource-cost-using-automation]]
|
||||
33
wiki/entities/Mike-Dukes.md
Normal file
33
wiki/entities/Mike-Dukes.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: "Mike Dukes"
|
||||
type: entity
|
||||
tags:
|
||||
- AWS
|
||||
- FinOps
|
||||
- Cost-Optimization
|
||||
aliases:
|
||||
- Mike Dukes
|
||||
last_updated: 2026-05-12
|
||||
---
|
||||
|
||||
# Mike Dukes
|
||||
|
||||
**Role:** AWS 专家，AWS Public Cloud Learning Sessions 讲师
|
||||
|
||||
## Overview
|
||||
Mike Dukes 是 AWS 专家，与 Steele Taylor 共同主讲"Best practices for EC2 cost optimization in AWS"（2024-05-29）公开云学习会议。主题涵盖 AWS 云效率原则、Graviton 实例、EC2 Spot 竞价实例、Nitro 系统和容器化成本优化。
|
||||
|
||||
## Expertise
|
||||
- AWS EC2 成本优化
|
||||
- Graviton ARM 处理器
|
||||
- EC2 Spot 实例
|
||||
- 云财务管理（FinOps）
|
||||
|
||||
## Sessions
|
||||
- [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]（2024-05-29）
|
||||
|
||||
## Connections
|
||||
- [[Steele-Taylor]]：共同讲师
|
||||
- [[AWS]]：所属机构
|
||||
- [[Graviton]]：演讲主题
|
||||
- [[EC2-Spot-Instances]]：演讲主题
|
||||
36
wiki/entities/Spot-Invaders.md
Normal file
36
wiki/entities/Spot-Invaders.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
title: "Spot Invaders"
|
||||
type: entity
|
||||
tags:
|
||||
- AWS
|
||||
- EKS
|
||||
- Spot-Instances
|
||||
- Chaos-Engineering
|
||||
aliases:
|
||||
- Spot Invaders
|
||||
last_updated: 2026-05-12
|
||||
---
|
||||
|
||||
# Spot Invaders
|
||||
|
||||
**Type:** EKS + EC2 Spot 容错混沌工程游戏
|
||||
|
||||
## Overview
|
||||
Spot Invaders 是一款基于 Amazon EKS 和 EC2 Spot 实例的容错混沌工程游戏，直观展示如何在 EKS 上运行具有弹性的应用，同时优化成本。游戏机制包括射击外星人（模拟 Pod 故障）和鲸鱼（触发 Spot 中断），生动展现即使在发生中断的情况下也能维持服务可用性的最佳实践。
|
||||
|
||||
## Game Mechanics
|
||||
- **射击外星人**：模拟 Pod 故障，展示应用容错能力
|
||||
- **射击鲸鱼**：触发 Spot 实例中断，演示 Spot 中断通知机制
|
||||
- **存活挑战**：在持续的 Pod 故障和 Spot 中断下维持游戏运行
|
||||
|
||||
## Key Lessons
|
||||
- Spot 实例可用于生产级有弹性要求的应用
|
||||
- 跨实例类型和可用区多样化是关键
|
||||
- EKS 提供内置 Spot 中断通知（2 分钟预警）
|
||||
- 自动化中断响应可实现零停机
|
||||
|
||||
## Connections
|
||||
- [[AWS]]：托管平台
|
||||
- [[EKS]]：容器编排平台
|
||||
- [[EC2-Spot-Instances]]：底层计算资源
|
||||
- [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]：演示来源
|
||||
33
wiki/entities/Steele-Taylor.md
Normal file
33
wiki/entities/Steele-Taylor.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: "Steele Taylor"
|
||||
type: entity
|
||||
tags:
|
||||
- AWS
|
||||
- FinOps
|
||||
- Cost-Optimization
|
||||
aliases:
|
||||
- Steele Taylor
|
||||
last_updated: 2026-05-12
|
||||
---
|
||||
|
||||
# Steele Taylor
|
||||
|
||||
**Role:** AWS 专家，AWS Public Cloud Learning Sessions 讲师
|
||||
|
||||
## Overview
|
||||
Steele Taylor 是 AWS 专家，与 Mike Dukes 共同主讲"Best practices for EC2 cost optimization in AWS"（2024-05-29）公开云学习会议。主题涵盖 EC2 实例选型策略、Graviton 使用、Spot 竞价实例最佳实践和容器化部署成本优化。
|
||||
|
||||
## Expertise
|
||||
- AWS EC2 成本优化
|
||||
- Graviton ARM 处理器
|
||||
- EC2 Spot 实例策略
|
||||
- 云财务管理（FinOps）
|
||||
|
||||
## Sessions
|
||||
- [[public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2]]（2024-05-29）
|
||||
|
||||
## Connections
|
||||
- [[Mike-Dukes]]：共同讲师
|
||||
- [[AWS]]：所属机构
|
||||
- [[Graviton]]：演讲主题
|
||||
- [[EC2-Spot-Instances]]：演讲主题
|
||||
@@ -4,6 +4,23 @@
|
||||
- [Overview](overview.md) — living synthesis
|
||||
|
||||
## Sources
|
||||
- [2026-04-29] [Public Cloud Learning Sessions - Reducing Cloud Costs - 20250318](sources/public-cloud-learning-sessions-reducing-cloud-costs-20250318-170100-meeting-reco.md)
|
||||
- [2026-04-29] [CTP Topic 13 Cloud FinOps Micro Focus Policies best practices to optimize the costs](sources/ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co.md)
|
||||
- [2026-04-29] [CTP Topic 15 Working with Renovatebot](sources/ctp-topic-15-working-with-renovatebot.md)
|
||||
- [2026-04-29] [CTP Topic 56 Automated Infrastructure Testing](sources/ctp-topic-56-automated-infrastructure-testing.md)
|
||||
- [2026-04-29] [Public Cloud Learning Sessions - Ollie Workflow and The Demand Process - 20240416](sources/public-cloud-learning-sessions-ollie-workflow-and-the-demand-process-20240416-16.md)
|
||||
- [2026-04-29] [CTP Topic 33 An Introduction to GitOps](sources/ctp-topic-33-an-introduction-to-gitops.md)
|
||||
- [2026-04-29] [CTP Topic 3 Deploy and Maintain Infrastructure](sources/ctp-topic-3-deploy-and-maintain-infrastructure.md)
|
||||
- [2026-04-29] [CTP Topic 9 CI CD with Gruntwork](sources/ctp-topic-9-ci-cd-with-gruntwork.md)
|
||||
- [2026-04-29] [CTP Topic 32 Using Atlantis CICD for Infrastructure Deployments](sources/ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments.md)
|
||||
- [2026-04-29] [CTP Topic 2 Git](sources/ctp-topic-2-git.md)
|
||||
- [2026-04-29] [CTP Topic 24 Micro Focus Product Privacy Framework](sources/ctp-topic-24-micro-focus-product-privacy-framework.md)
|
||||
- [2026-04-29] [CTP Topic 49 Container Lifecycle Hardening Standards](sources/ctp-topic-49-container-lifecycle-hardening-standards.md)
|
||||
- [2026-04-29] [CTP Topic 21 Supply Chain Security in Micro Focus](sources/ctp-topic-21-supply-chain-security-in-micro-focus.md)
|
||||
- [2026-04-29] [CTP Topic 52 3 Lines of Defence (3LoD) framework Cloud Security Posture Management (CSPM)](sources/ctp-topic-52-3-lines-of-defence-3lod-framework-cloud-security-posture-management.md)
|
||||
- [2026-04-28] [CTP Topic 55 AWS Firewall Manager](sources/ctp-topic-55-aws-firewall-manager.md)
|
||||
- [2026-04-28] [CTP Topic 37 Secrets Certificates Management](sources/ctp-topic-37-secrets-certificates-management.md)
|
||||
- [2026-04-28] [CTP Topic 62 AWS Secrets Manager](sources/ctp-topic-62-aws-secrets-manager.md)
|
||||
- [2026-04-28] [Public Cloud Learning Sessions - OpenText GIS Security Policies - 20241015](sources/public-cloud-learning-sessions-opentext-gis-security-policies-20241015-160257-me.md)
|
||||
- [2026-04-28] [CTP Topic 64 Scaling out with Amazon EKS](sources/ctp-topic-64-scaling-out-with-amazon-eks.md)
|
||||
- [2026-04-28] [CTP Topic 67 Cloud native observability using OpenTelemetry](sources/ctp-topic-67-cloud-native-observability-using-opentelemetry.md)
|
||||
@@ -197,7 +214,7 @@
|
||||
- [2026-04-26] [万字讲透OpenClaw Workspace深度解析](sources/万字讲透openclaw-workspace深度解析-2026-03-21.md)
|
||||
- [2026-04-26] [How to get Youtube Channel ID](sources/how-to-get-youtube-channel-id.md)
|
||||
- [2026-04-26] [TikTok PM - Python Django 项目](sources/tiktok-pm-python-django-project.md)
|
||||
- [2026-04-26] [Dataview——让我从笔记黑洞里逃出来的 Obsidian 神器](sources/dataview-让我从"笔记黑洞"里逃出来的-obsidian-神器-1.md)
|
||||
- [2026-04-26] [dataview-让我从“笔记黑洞”里逃出来的-obsidian-神器-1](sources/dataview-让我从“笔记黑洞”里逃出来的-obsidian-神器-1.md) — (expected: wiki/sources/dataview-让我从“笔记黑洞”里逃出来的-obsidian-神器-1.md — source missing)
|
||||
- [2026-04-26] [Obsidian 高效指南：我常用的插件与实用技巧](sources/obsidian-高效指南-我常用的插件与实用技巧.md)
|
||||
- [2026-04-26] [Obsidian最有必要安装的10款插件是这些](sources/obsidian最有必要安装的10款插件是这些.md)
|
||||
- [2026-04-26] [Obsidian Tasks 插件：这可能是最适合懒人的任务管理方式](sources/obsidian-tasks-插件-这可能是最适合懒人的任务管理方式.md)
|
||||
@@ -272,29 +289,12 @@
|
||||
- [Public Cloud Learning Sessions (OpenText) - Event Driven Architecture Part 1](sources/public-cloud-learning-sessions-opentext-event-driven-architecture-part-1-2024091.md)
|
||||
- [Public Cloud Learning Sessions (OpenText) - AI Use Cases - 20241126 160106](sources/public-cloud-learning-sessions-opentext-ai-use-cases-20241126-160106-meeting-rec.md)
|
||||
- [Public Cloud Learning Sessions - Introduction to AI/ML with AWS](sources/public-cloud-learning-sessions-introduction-to-artificial-intelligence-ai-machin.md)
|
||||
- [CTP Topic 62 AWS Secrets Manager](sources/ctp-topic-62-aws-secrets-manager.md)
|
||||
- [CTP Topic 55 AWS Firewall Manager](sources/ctp-topic-55-aws-firewall-manager.md)
|
||||
- [CTP Topic 52 3 Lines of Defence (3LoD) framework Cloud Security Posture Management (CSPM)](sources/ctp-topic-52-3-lines-of-defence-3lod-framework-cloud-security-posture-management.md)
|
||||
- [CTP Topic 49 Container Lifecycle Hardening Standards](sources/ctp-topic-49-container-lifecycle-hardening-standards.md)
|
||||
- [CTP Topic 37 Secrets Certificates Management](sources/ctp-topic-37-secrets-certificates-management.md)
|
||||
- [CTP Topic 24 Micro Focus Product Privacy Framework](sources/ctp-topic-24-micro-focus-product-privacy-framework.md)
|
||||
- [CTP Topic 21 Supply Chain Security in Micro Focus](sources/ctp-topic-21-supply-chain-security-in-micro-focus.md)
|
||||
- [Public Cloud Learning Sessions - Ollie Workflow and The Demand Process - 20240416](sources/public-cloud-learning-sessions-ollie-workflow-and-the-demand-process-20240416-16.md)
|
||||
- [CTP Topic 9 CI CD with Gruntwork](sources/ctp-topic-9-ci-cd-with-gruntwork.md)
|
||||
- [CTP Topic 56 Automated Infrastructure Testing](sources/ctp-topic-56-automated-infrastructure-testing.md)
|
||||
- [CTP Topic 33 An Introduction to GitOps](sources/ctp-topic-33-an-introduction-to-gitops.md)
|
||||
- [CTP Topic 32 Using Atlantis CICD for Infrastructure Deployments](sources/ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments.md)
|
||||
- [CTP Topic 3 Deploy and maintain infrastructure](sources/ctp-topic-3-deploy-and-maintain-infrastructure.md)
|
||||
- [CTP Topic 2 Git](sources/ctp-topic-2-git.md)
|
||||
- [CTP Topic 15 Working with Renovatebot](sources/ctp-topic-15-working-with-renovatebot.md)
|
||||
- [Public Cloud Learning Sessions - Storage Cost Optimization - 20240305](sources/public-cloud-learning-sessions-storage-cost-optimization-20240305-160037-meeting.md)
|
||||
- [Public Cloud Learning Sessions - Reducing Cloud Costs - 20250318](sources/public-cloud-learning-sessions-reducing-cloud-costs-20250318-170100-meeting-reco.md)
|
||||
- [Public Cloud Learning Sessions - Budget Control - 20240319](sources/public-cloud-learning-sessions-budget-control-20240319-160204-meeting-recording.md)
|
||||
- [Public Cloud Learning Sessions - Best practices for EC2 cost optimization in AWS - 20240529](sources/public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2.md)
|
||||
- [2024-05-29] [Public Cloud Learning Sessions - Best practices for EC2 cost optimization in AWS - 20240529](sources/public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2.md) — AWS EC2 成本优化最佳实践：Graviton（40% 性价比提升）、Spot 竞价（90% 折扣）、Nitro 系统、购买选项策略
|
||||
- [CTP Topic 71 PCG's guide to RightSizing, why, how when](sources/ctp-topic-71-pcgs-guide-to-rightsizing-why-how-when.md)
|
||||
- [CTP Topic 63 Optimise resource cost using automation](sources/ctp-topic-63-optimise-resource-cost-using-automation.md)
|
||||
- [CTP Topic 27 AWS Instance Scheduler](sources/ctp-topic-27-aws-instance-scheduler.md)
|
||||
- [CTP Topic 13 Cloud FinOps Micro Focus Policies best practices to optimize the costs](sources/ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co.md)
|
||||
- [Learning Sessions ECS Deployment using IAC - 20230808](sources/learning-sessions-ecs-deployment-using-iac-20230808-183322-meeting-recording.md)
|
||||
- [Learning Sessions Cloud Transformation Programme-Deploying RDS via Terraform](sources/learning-sessions-cloud-transformation-programme-deploying-rds-via-terraform.md)
|
||||
- [Learning Sessions Cloud Transformation Programme-20230808 183322-Meeting Recording](sources/learning-sessions-cloud-transformation-programme-20230808-183322-meeting-recordi.md)
|
||||
@@ -613,6 +613,7 @@
|
||||
- [Calibre](entities/Calibre.md)
|
||||
- [Canva](entities/Canva.md)
|
||||
- [CapCut-Pro](entities/CapCut-Pro.md)
|
||||
- [CCLE](entities/CCLE.md)
|
||||
- [CCOE](entities/CCOE.md)
|
||||
- [ChatGPT](entities/ChatGPT.md)
|
||||
- [Checkpoint](entities/Checkpoint.md)
|
||||
@@ -646,6 +647,7 @@
|
||||
- [CrewAI](entities/CrewAI.md)
|
||||
- [Cursor](entities/Cursor.md)
|
||||
- [Curve-Finance](entities/Curve-Finance.md)
|
||||
- [CyberArk](entities/CyberArk.md)
|
||||
- [Damian](entities/Damian.md)
|
||||
- [DanielStefanovic](entities/DanielStefanovic.md)
|
||||
- [Databunker](entities/Databunker.md)
|
||||
@@ -681,6 +683,7 @@
|
||||
- [fireworks-tech-graph](entities/fireworks-tech-graph.md)
|
||||
- [Flux](entities/Flux.md)
|
||||
- [FMOD](entities/FMOD.md)
|
||||
- [FPNA-Team](entities/FPNA-Team.md)
|
||||
- [Frontend-Developer](entities/Frontend-Developer.md)
|
||||
- [frp](entities/frp.md)
|
||||
- [Gamma-AI](entities/Gamma-AI.md)
|
||||
@@ -693,6 +696,7 @@
|
||||
- [GitLab](entities/GitLab.md)
|
||||
- [Gitmoji](entities/Gitmoji.md)
|
||||
- [glances](entities/glances.md)
|
||||
- [Godrails](entities/Godrails.md)
|
||||
- [gog](entities/gog.md)
|
||||
- [gog-CLI](entities/gog-CLI.md)
|
||||
- [Google](entities/Google.md)
|
||||
@@ -774,11 +778,13 @@
|
||||
- [Midjourney](entities/Midjourney.md)
|
||||
- [Mike](entities/Mike.md)
|
||||
- [MikeArmstrong](entities/MikeArmstrong.md)
|
||||
- [Mike-Dukes](entities/Mike-Dukes.md) — AWS 专家，EC2 成本优化讲师
|
||||
- [MikeOReily](entities/MikeOReily.md)
|
||||
- [Milvus](entities/Milvus.md)
|
||||
- [MinIO](entities/MinIO.md)
|
||||
- [mission-center](entities/mission-center.md)
|
||||
- [mnemox-ai](entities/mnemox-ai.md)
|
||||
- [MUI](entities/MUI.md)
|
||||
- [n8n](entities/n8n.md)
|
||||
- [n8n-mcp](entities/n8n-mcp.md)
|
||||
- [Nano Banana 2](entities/Nano Banana 2.md)
|
||||
@@ -819,6 +825,8 @@
|
||||
- [OWASP](entities/OWASP.md)
|
||||
- [PageLM](entities/PageLM.md)
|
||||
- [PaloAltoNetworks](entities/PaloAltoNetworks.md)
|
||||
- [Paul-Hopkins](entities/Paul-Hopkins.md)
|
||||
- [PCG](entities/PCG.md)
|
||||
- [PCGTeam](entities/PCGTeam.md)
|
||||
- [Peloton](entities/Peloton.md)
|
||||
- [Perplexica](entities/Perplexica.md)
|
||||
@@ -840,6 +848,7 @@
|
||||
- [Qalis](entities/Qalis.md)
|
||||
- [QALIS-Agent](entities/QALIS-Agent.md)
|
||||
- [Qdrant](entities/Qdrant.md)
|
||||
- [Qixi](entities/Qixi.md)
|
||||
- [Qwen](entities/Qwen.md)
|
||||
- [Qwen2.5-Coder](entities/Qwen2.5-Coder.md)
|
||||
- [RackNerd](entities/RackNerd.md)
|
||||
@@ -864,7 +873,9 @@
|
||||
- [Scrapy](entities/Scrapy.md)
|
||||
- [Sentinel-1](entities/Sentinel-1.md)
|
||||
- [Sergio](entities/Sergio.md)
|
||||
- [Shannon](entities/Shannon.md)
|
||||
- [shenwei](entities/shenwei.md)
|
||||
- [Steele-Taylor](entities/Steele-Taylor.md) — AWS 专家，EC2 成本优化讲师
|
||||
- [SilverPeak](entities/SilverPeak.md)
|
||||
- [Simon-Hoiberg](entities/Simon-Hoiberg.md)
|
||||
- [Slack](entities/Slack.md)
|
||||
@@ -873,6 +884,7 @@
|
||||
- [SONY](entities/SONY.md)
|
||||
- [Sora](entities/Sora.md)
|
||||
- [SparkryAI](entities/SparkryAI.md)
|
||||
- [Spot-Invaders](entities/Spot-Invaders.md) — EKS + Spot 实例容错混沌工程游戏
|
||||
- [Sprint-Prioritizer](entities/Sprint-Prioritizer.md)
|
||||
- [SRE-Team](entities/SRE-Team.md)
|
||||
- [SSE](entities/SSE.md)
|
||||
@@ -900,6 +912,7 @@
|
||||
- [tini](entities/tini.md)
|
||||
- [Todoist](entities/Todoist.md)
|
||||
- [TodoistRestApi](entities/TodoistRestApi.md)
|
||||
- [Tom-Bice](entities/Tom-Bice.md)
|
||||
- [Trae](entities/Trae.md)
|
||||
- [TranscriptAPI](entities/TranscriptAPI.md)
|
||||
- [Transmission](entities/Transmission.md)
|
||||
@@ -911,6 +924,7 @@
|
||||
- [TypeScript-Language-Server](entities/TypeScript-Language-Server.md)
|
||||
- [Ubuntu-Server](entities/Ubuntu-Server.md)
|
||||
- [UCMDB](entities/UCMDB.md)
|
||||
- [Uday](entities/Uday.md)
|
||||
- [UI-Designer](entities/UI-Designer.md)
|
||||
- [UnityGamingServices](entities/UnityGamingServices.md)
|
||||
- [UnityMultiplayerEngineer](entities/UnityMultiplayerEngineer.md)
|
||||
@@ -1068,6 +1082,7 @@
|
||||
- [Availability-Zone-ID](concepts/Availability-Zone-ID.md)
|
||||
- [AWS-Backup-Concepts](concepts/AWS-Backup-Concepts.md)
|
||||
- [AWS-End-User-Computing](concepts/AWS-End-User-Computing.md)
|
||||
- [AWS-Firewall-Manager](concepts/AWS-Firewall-Manager.md)
|
||||
- [AWS-Identity-Center](concepts/AWS-Identity-Center.md)
|
||||
- [AWS-Inspector](concepts/AWS-Inspector.md)
|
||||
- [AWS-Secrets-Manager](concepts/AWS-Secrets-Manager.md)
|
||||
@@ -1131,6 +1146,7 @@
|
||||
- [ChinaLaborLawCompliance](concepts/ChinaLaborLawCompliance.md)
|
||||
- [Choice-Architecture](concepts/Choice-Architecture.md)
|
||||
- [CI-CD-Pipeline](concepts/CI-CD-Pipeline.md)
|
||||
- [CI-CD-Secrets](concepts/CI-CD-Secrets.md)
|
||||
- [CICDPipeline](concepts/CICDPipeline.md)
|
||||
- [CIDR-审批流程](concepts/CIDR-审批流程.md)
|
||||
- [CircuitBreaker](concepts/CircuitBreaker.md)
|
||||
@@ -1157,6 +1173,7 @@
|
||||
- [cloud-security](concepts/cloud-security.md)
|
||||
- [Cloud-Security-Maturity-Model](concepts/Cloud-Security-Maturity-Model.md)
|
||||
- [Cloud-Service-Delivery](concepts/Cloud-Service-Delivery.md)
|
||||
- [CloudHealth](concepts/CloudHealth.md)
|
||||
- [CloudWatch-Agent](concepts/CloudWatch-Agent.md)
|
||||
- [Cluster-Autoscaler](concepts/Cluster-Autoscaler.md)
|
||||
- [CMDB](concepts/CMDB.md)
|
||||
@@ -1239,8 +1256,10 @@
|
||||
- [Defuddle](concepts/Defuddle.md)
|
||||
- [Delegation-Chain](concepts/Delegation-Chain.md)
|
||||
- [Delivery-Traceability](concepts/Delivery-Traceability.md)
|
||||
- [Demand-Management](concepts/Demand-Management.md)
|
||||
- [Demo-Engineering](concepts/Demo-Engineering.md)
|
||||
- [Dengbao-2.0](concepts/Dengbao-2.0.md)
|
||||
- [Dependency-Dashboard](concepts/Dependency-Dashboard.md)
|
||||
- [Dependency-Management](concepts/Dependency-Management.md)
|
||||
- [Deployment-Automation](concepts/Deployment-Automation.md)
|
||||
- [Deployment-vs-Release](concepts/Deployment-vs-Release.md)
|
||||
@@ -1281,12 +1300,15 @@
|
||||
- [Earnings-Beat-Miss](concepts/Earnings-Beat-Miss.md)
|
||||
- [Earnings-Calendar](concepts/Earnings-Calendar.md)
|
||||
- [EC2-Purchase-Options](concepts/EC2-Purchase-Options.md)
|
||||
- [EC2-Spot-Instances](concepts/EC2-Spot-Instances.md) — 竞价实例，Spot 折扣高达 90%
|
||||
- [Economy-Balance](concepts/Economy-Balance.md)
|
||||
- [efibootmgr](concepts/efibootmgr.md)
|
||||
- [EFS-vs-EBS](concepts/EFS-vs-EBS.md)
|
||||
- [EKS-Auto-Mode](concepts/EKS-Auto-Mode.md)
|
||||
- [EKS-Custom-Networking](concepts/EKS-Custom-Networking.md)
|
||||
- [AWS-Nitro](concepts/AWS-Nitro.md) — AWS 虚拟化平台，网络/存储/安全组件外部化
|
||||
- [ELK-Stack](concepts/ELK-Stack.md)
|
||||
- [ECS](concepts/ECS.md) — Amazon Elastic Container Service，托管容器编排
|
||||
- [Email-Triage](concepts/Email-Triage.md)
|
||||
- [Embedding](concepts/Embedding.md)
|
||||
- [Emergency-Change](concepts/Emergency-Change.md)
|
||||
@@ -1365,6 +1387,7 @@
|
||||
- [GPG-密钥验证](concepts/GPG-密钥验证.md)
|
||||
- [GPT分区表](concepts/GPT分区表.md)
|
||||
- [Grandes-Ecoles](concepts/Grandes-Ecoles.md)
|
||||
- [Graviton](concepts/Graviton.md)
|
||||
- [Green-Computing](concepts/Green-Computing.md)
|
||||
- [Growth-Loop](concepts/Growth-Loop.md)
|
||||
- [GrowthFunnelOptimization](concepts/GrowthFunnelOptimization.md)
|
||||
@@ -1430,8 +1453,10 @@
|
||||
- [IP纯净度](concepts/IP纯净度.md)
|
||||
- [ISO-27001](concepts/ISO-27001.md)
|
||||
- [ISOHybrid镜像](concepts/ISOHybrid镜像.md)
|
||||
- [ITIL-Service-Management](concepts/ITIL-Service-Management.md)
|
||||
- [ITSM](concepts/ITSM.md)
|
||||
- [ITSM-2.0](concepts/ITSM-2.0.md)
|
||||
- [JDBCWrapper](concepts/JDBCWrapper.md)
|
||||
- [Jenkins-Multi-Branch-Pipeline](concepts/Jenkins-Multi-Branch-Pipeline.md)
|
||||
- [JFFS双清](concepts/JFFS双清.md)
|
||||
- [Jira-Gate](concepts/Jira-Gate.md)
|
||||
@@ -1559,6 +1584,7 @@
|
||||
- [Obsidian-CLI](concepts/Obsidian-CLI.md)
|
||||
- [Obsidian-Tasks](concepts/Obsidian-Tasks.md)
|
||||
- [ObsidianRecurringTasks](concepts/ObsidianRecurringTasks.md)
|
||||
- [Oli-Workflow](concepts/Oli-Workflow.md)
|
||||
- [OpenClaw-Deployment-Expert](concepts/OpenClaw-Deployment-Expert.md)
|
||||
- [OpenTelemetry](concepts/OpenTelemetry.md)
|
||||
- [OpenText-Tagging-Standard](concepts/OpenText-Tagging-Standard.md)
|
||||
@@ -1611,6 +1637,7 @@
|
||||
- [Post-Processing](concepts/Post-Processing.md)
|
||||
- [PRD生成工作流](concepts/PRD生成工作流.md)
|
||||
- [Pre-Build-Validation](concepts/Pre-Build-Validation.md)
|
||||
- [Pre-commit-Hooks](concepts/Pre-commit-Hooks.md)
|
||||
- [PreBuildValidation](concepts/PreBuildValidation.md)
|
||||
- [Predictive-Maintenance](concepts/Predictive-Maintenance.md)
|
||||
- [Prisma-Access](concepts/Prisma-Access.md)
|
||||
@@ -1618,12 +1645,14 @@
|
||||
- [Private-Context](concepts/Private-Context.md)
|
||||
- [Private-Hosted-Zone](concepts/Private-Hosted-Zone.md)
|
||||
- [Private-Subnet-Architecture](concepts/Private-Subnet-Architecture.md)
|
||||
- [Privileged-Access-Management](concepts/Privileged-Access-Management.md)
|
||||
- [Proactive-Agent-Recommendation](concepts/Proactive-Agent-Recommendation.md)
|
||||
- [Proactive-AI](concepts/Proactive-AI.md)
|
||||
- [ProactiveAI](concepts/ProactiveAI.md)
|
||||
- [Problem-Management](concepts/Problem-Management.md)
|
||||
- [Procedural-Level-Design](concepts/Procedural-Level-Design.md)
|
||||
- [process-management](concepts/process-management.md)
|
||||
- [Product-Backlog](concepts/Product-Backlog.md)
|
||||
- [Product-Hierarchy](concepts/Product-Hierarchy.md)
|
||||
- [ProductLedGrowth](concepts/ProductLedGrowth.md)
|
||||
- [Program-Demand-Process](concepts/Program-Demand-Process.md)
|
||||
@@ -1650,6 +1679,7 @@
|
||||
- [Quick-Capture](concepts/Quick-Capture.md)
|
||||
- [RACI](concepts/RACI.md)
|
||||
- [RAG](concepts/RAG.md)
|
||||
- [Rate-Limiting](concepts/Rate-Limiting.md)
|
||||
- [Reality-Signal](concepts/Reality-Signal.md)
|
||||
- [RealityKit-SwiftUI-Integration](concepts/RealityKit-SwiftUI-Integration.md)
|
||||
- [RealitySignal](concepts/RealitySignal.md)
|
||||
@@ -1675,6 +1705,7 @@
|
||||
- [Replication-Graph](concepts/Replication-Graph.md)
|
||||
- [Repo-Mirroring](concepts/Repo-Mirroring.md)
|
||||
- [Requirements-Gathering](concepts/Requirements-Gathering.md)
|
||||
- [ReservedInstances](concepts/ReservedInstances.md)
|
||||
- [Resolver-Rules](concepts/Resolver-Rules.md)
|
||||
- [Resource-Allocation](concepts/Resource-Allocation.md)
|
||||
- [Resource-Tagging](concepts/Resource-Tagging.md)
|
||||
@@ -1702,6 +1733,7 @@
|
||||
- [Sandboxed-Persona](concepts/Sandboxed-Persona.md)
|
||||
- [SAST](concepts/SAST.md)
|
||||
- [Savings-Plans](concepts/Savings-Plans.md)
|
||||
- [SavingsPlans](concepts/SavingsPlans.md)
|
||||
- [SCA](concepts/SCA.md)
|
||||
- [Scalability](concepts/Scalability.md)
|
||||
- [Scheduled-Reminder](concepts/Scheduled-Reminder.md)
|
||||
@@ -1715,10 +1747,13 @@
|
||||
- [SDDC](concepts/SDDC.md)
|
||||
- [SE-Linux-Enforcing](concepts/SE-Linux-Enforcing.md)
|
||||
- [Second-Renaissance](concepts/Second-Renaissance.md)
|
||||
- [SecretRotation](concepts/SecretRotation.md)
|
||||
- [Secrets-Management](concepts/Secrets-Management.md)
|
||||
- [SecretsManagement](concepts/SecretsManagement.md)
|
||||
- [Secure-Dynamic-Updates](concepts/Secure-Dynamic-Updates.md)
|
||||
- [Security Awareness Training](concepts/Security Awareness Training.md)
|
||||
- [Security-and-Compliance](concepts/Security-and-Compliance.md)
|
||||
- [Security-Group-Policy](concepts/Security-Group-Policy.md)
|
||||
- [Self-Education](concepts/Self-Education.md)
|
||||
- [Self-Healing](concepts/Self-Healing.md)
|
||||
- [Self-Healing-Systems](concepts/Self-Healing-Systems.md)
|
||||
@@ -1761,6 +1796,7 @@
|
||||
- [SkillToolset](concepts/SkillToolset.md)
|
||||
- [SLR](concepts/SLR.md)
|
||||
- [SLS](concepts/SLS.md)
|
||||
- [SMACs](concepts/SMACs.md)
|
||||
- [SmartBidding](concepts/SmartBidding.md)
|
||||
- [SnapMirror](concepts/SnapMirror.md)
|
||||
- [Social-Media-Giveaway](concepts/Social-Media-Giveaway.md)
|
||||
@@ -1783,6 +1819,7 @@
|
||||
- [Speedrun-Design](concepts/Speedrun-Design.md)
|
||||
- [Split](concepts/Split.md)
|
||||
- [Spot-Instances](concepts/Spot-Instances.md)
|
||||
- [SpotInstances](concepts/SpotInstances.md)
|
||||
- [SPREAD-Strategy](concepts/SPREAD-Strategy.md)
|
||||
- [SprintPlanning](concepts/SprintPlanning.md)
|
||||
- [SRE](concepts/SRE.md)
|
||||
|
||||
129
wiki/log.md
129
wiki/log.md
@@ -1,3 +1,105 @@
|
||||
## [2026-05-12] ingest | Public Cloud Learning Sessions - Best practices for EC2 cost optimization in AWS - 20240529
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/05_FinOps/public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: AWS EC2 成本优化最佳实践：Graviton（40% 性价比提升/60% 功耗降低）、Spot 竞价实例（90% 折扣）、AWS Nitro 虚拟化、Nitro Enclave；Mike Dukes 和 Steele Taylor 主讲；Spot Invaders 游戏演示容错混沌工程
|
||||
- Concepts created/updated: [[AWS-Nitro]]（新建）、[[EC2-Spot-Instances]]（新建）、[[ECS]]（新建）；[[Graviton]]（已有，已追加来源链接）、[[SpotInstances]]（已有，已追加来源链接）
|
||||
- Entities created/updated: [[Mike-Dukes]]（新建）、[[Steele-Taylor]]（新建）、[[Spot-Invaders]]（新建）
|
||||
- Source page: wiki/sources/public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2.md
|
||||
- Notes: 步骤3完成：新建 source page（含 frontmatter、Summary、Key Claims、Key Quotes、Key Concepts、Key Entities、Connections、Contradictions 八节）；步骤4完成：index.md 第294行添加日期前缀和摘要；步骤5完成：overview.md 第397行已有该来源详细摘要，无需修订；步骤6完成：新建 Mike-Dukes.md/Steele-Taylor.md/Spot-Invaders.md Entity 页面；步骤7完成：新建 AWS-Nitro.md/EC2-Spot-Instances.md/ECS.md Concept 页面；更新 Graviton.md/SpotInstances.md 添加来源引用；步骤8完成：记录与 CTP Topic 13 的潜在冲突点（Graviton 适用场景，已协调）；步骤9完成：log.md 追加记录
|
||||
|
||||
## [2026-05-12] ingest | CTP Topic 13 Cloud FinOps Micro Focus Policies best practices to optimize the costs
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/05_FinOps/ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Cloud FinOps 治理框架：PCG 三层服务模型（成本管理/成本优化/治理自动化）、5 大核心策略（账单可见性/标签合规/预算责任/RI集中管理/区域限制）、安全控制（Godrails/联合身份管理）、Cloud Health 监控工具、实例选型标准化（M/T/C/R/X+Graviton）、研发环境三合一优化（突发性+Spot+调度器）
|
||||
- Concepts created/updated: [[Graviton]]（新建）、[[CloudHealth]]（新建）、[[ReservedInstances]]（新建）、[[SpotInstances]]（已有，已链接）、[[SavingsPlans]]（已有，已链接）、[[FinOps]]（已有，已更新链接）
|
||||
- Entities created/updated: [[PCGTeam]]（已存在，已更新）、[[Uday]]（新建）、[[Vinay]]（已存在）、[[Godrails]]（新建）
|
||||
- Source page: wiki/sources/ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co.md
|
||||
- Notes: 步骤3完成：新建 source page（含 frontmatter、Summary、Key Claims、Key Quotes、Key Concepts、Key Entities、Connections、Contradictions 八节）；步骤4完成：index.md 第297行添加日期前缀和摘要；步骤5完成：overview.md 修正5处 wikilinks（从 ctp-topic-13-cloud-finops-policies 更正为 ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co）；步骤6完成：新建 Uday.md/Godrails.md Entity 页面，更新 PCGTeam.md；步骤7完成：新建 Graviton.md/CloudHealth.md/ReservedInstances.md Concept 页面，FinOps/SpotInstances/SavingsPlans 已存在；步骤8完成：无冲突；步骤9完成：log.md 追加记录
|
||||
|
||||
## [2026-05-11] ingest | CTP Topic 15 Working with Renovatebot
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/06_CI_CD_GitOps/ctp-topic-15-working-with-renovatebot.md
|
||||
- Status: ✅ 成功摄入（补充新建缺失 Entity/Concept 页面）
|
||||
- Summary: Renovate Bot 自动化管理云原生基础设施依赖项更新——解决"依赖地狱"问题，实时扫描 Docker 镜像/Terraform 模块/Terragrunt 配置/pre-commit 钩子版本标签，自动发起 Pull Request；通过 Dependency Dashboard 提供全局依赖状态视图；集成 Jenkins 流水线，使用 Podman 容器化运行并配置 Rate Limiting 避免 PR 风暴。
|
||||
- Concepts created/updated: [[Dependency-Dashboard]]（新建）、[[Rate-Limiting]]（新建）、[[Pre-commit-Hooks]]（新建）
|
||||
- Entities created: [[Paul-Hopkins]]（新建，作为关键人物创建）
|
||||
- Source page: wiki/sources/ctp-topic-15-working-with-renovatebot.md
|
||||
- Notes: 步骤3完成：source page 已存在（之前已摄入）；步骤4完成：index.md 补充 Dependency-Dashboard/Rate-Limiting/Pre-commit-Hooks 到 Concepts 节、Paul-Hopkins 到 Entities 节；步骤5完成：overview.md 第249行已有该来源详细摘要，内容一致无需修订；步骤6完成：新建 Paul-Hopkins.md Entity 页面；步骤7完成：新建 Dependency-Dashboard.md/Rate-Limiting.md/Pre-commit-Hooks.md Concept 页面；步骤8完成：无新冲突；步骤9完成：log.md 追加记录。Renovate-Bot.md/Semantic-Versioning.md/Dependency-Management.md/Gruntwork.md/Jenkins.md/Terragrunt.md 均已存在，本次无需新建。
|
||||
|
||||
## [2026-05-11] ingest | Public Cloud Learning Sessions - Ollie Workflow and The Demand Process - 20240416
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Oli Workflow（超大规模云厂商支出审批流程）与需求管理端到端全链路——三阶段审批工作流（FinOps→Cloud Services→FPNA）和 OpenText 需求管理流程（Octane/Qixi 提交→主服务目录→SMACs 嵌入→自动化履约），目标是 80% 场景业务单元自助完成需求
|
||||
- Concepts created: Demand-Management.md, ITIL-Service-Management.md, SMACs.md, FinOps.md, Product-Backlog.md, Oli-Workflow.md
|
||||
- Entities created: Tom-Bice.md, FPNA-Team.md, MUI.md, Shannon.md, Octane.md, Qixi.md
|
||||
- Source page: wiki/sources/public-cloud-learning-sessions-ollie-workflow-and-the-demand-process-20240416-16.md
|
||||
- Notes: 步骤3完成：source page 已存在（步骤1确认）；步骤4完成：index.md 第287行已有条目；步骤5完成：overview.md 第379行已有该来源详细摘要，无需修订；步骤6完成：新建 Tom-Bice.md/FPNA-Team.md/MUI.md/Shannon.md/Octane.md/Qixi.md Entity 页面（均符合≥2次提及的创建条件）；步骤7完成：新建 Demand-Management.md/ITIL-Service-Management.md/SMACs.md/FinOps.md/Product-Backlog.md/Oli-Workflow.md Concept 页面（均符合可抽象/可复用/非具体实例的创建条件）；步骤8完成：无新冲突；步骤9完成：log.md 追加记录
|
||||
|
||||
## [2026-05-08] ingest | CTP Topic 3 Deploy and maintain infrastructure
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/06_CI_CD_GitOps/ctp-topic-3-deploy-and-maintain-infrastructure.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Landing Zone 多账号架构下基础设施部署与维护——核心区分 Service Module（业务视角，满足业务需求的一组模块组合）与 Regular Module（技术视角）；Terragrunt HCL 通过版本锁定引用模块而非 master 分支；Service Catalog 支持三级复用（单账户→产品团队→跨团队）；类 OO 继承原则：抽象层级越高，配置选项越少
|
||||
- Concepts created: （无新建 — Terraform/Terragrunt/Service-Catalog/Landing-Zone/Module/Infrastructure-as-Code 均已存在）
|
||||
- Entities created: （无新建 — Terraform/Terragrunt/Gruntwork/Jenkins 均已存在）
|
||||
- Source page: wiki/sources/ctp-topic-3-deploy-and-maintain-infrastructure.md
|
||||
- Notes: 步骤3完成：新建 source page（含 frontmatter、Summary、Key Claims、Key Quotes、Key Concepts、Key Entities、Connections、Contradictions 八节）；步骤4完成：index.md 条目补充日期前缀和一行摘要；步骤5完成：overview.md 第221行已有该来源详细摘要，内容一致无需修订；步骤6完成：无新建 Entity（Terraform/Terragrunt/Gruntwork/Jenkins 均已存在，DevTools 仅1次提及未达阈值）；步骤7完成：无新建 Concept（Service-Catalog/Terraform/Terragrunt/Landing-Zone 等均已存在）；步骤8完成：Contradictions 记录与 ctp-topic-1（框架vs自主）和 ctp-topic-48（Terragrunt对比）的视角关系；步骤9完成：log.md 追加记录
|
||||
|
||||
## [2026-04-29] ingest | CTP Topic 32 Using Atlantis CICD for Infrastructure Deployments
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/06_CI_CD_GitOps/ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Atlantis 替代 Jenkins 用于 Terraform IaC 部署的 CTP 视频，核心痛点：Jenkins 流水线初始化慢（多次代码克隆/顺序测试/ECS 预配置）和架构复杂（持续叠加功能导致脆弱）。Atlantis 提供 PR 评论式协作模型，支持模块 Locking、并行构建、跨账户 IAM 角色访问，merge 前 Apply 确保代码与基础设施同步。
|
||||
- Concepts created: [[GitOps]]（已存在，本次更新扩充内容，新增 Pull vs Push 模型对比和工具生态表）
|
||||
- Entities created: [[Atlantis]]（新建 Entity 页面，含核心功能、架构说明）、[[Jenkins]]（新建 Entity 页面，含痛点对比表）
|
||||
- Source page: wiki/sources/ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments.md
|
||||
- Notes: 步骤3完成：新建 source page（含 frontmatter、Summary、Key Claims、Key Quotes、Key Concepts、Key Entities、Connections、Contradictions 八节）；步骤4完成：index.md 第287行已有条目，以正确格式补充日期和一行摘要；步骤5完成：overview.md 第245行已有详细条目，本次无需修订；步骤6完成：新建 Atlantis.md 和 Jenkins.md Entity 页面（均符合出现≥2次的创建条件）；步骤7完成：GitOps.md 概念页已存在，本次扩充 Pull vs Push 模型对比和工具生态表；步骤8完成：无新冲突（Atlantis vs Jenkins 的 pre-merge-apply vs post-merge-deploy 差异已在 Contradictions 节记录）；步骤9完成：log.md 追加记录
|
||||
|
||||
## [2026-05-04] ingest | CTP Topic 9 CI CD with Gruntwork
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/06_CI_CD_GitOps/ctp-topic-9-ci-cd-with-gruntwork.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: CTP Topic 9 — CI/CD 与 Gruntwork IaC 集成视频（状态：待 Whisper 转录）。源文件仅有 frontmatter 元数据，含 tags: [CI/CD, Gruntwork, IaC, CTP]，视频尚未转录，Summary/Key Claims/Key Quotes 均标记为待补充。已与 Gruntwork Entity、CI/CD Concept、同分类其他 CTP 来源建立 Connections 链接。
|
||||
- Concepts created: （无新建 — CI/CD、GitOps、Infrastructure-as-Code Concept 页面均已存在，直接引用）
|
||||
- Entities created: [[Gruntwork]]（已存在，直接引用）
|
||||
- Source page: wiki/sources/ctp-topic-9-ci-cd-with-gruntwork.md
|
||||
- Notes: 步骤3完成：新建 source page（含 frontmatter、Summary、Key Claims、Key Quotes、Key Concepts、Key Entities、Connections、Contradictions 八节）；步骤4完成：index.md 第285行已有条目，以正确格式补充日期 2026-04-14；步骤5完成：overview.md 第223行已有该主题条目，本次无需修订；步骤6完成：Gruntwork Entity 页面已存在，直接引用；步骤7完成：CI/CD、GitOps、Infrastructure-as-Code Concept 页面均已存在，直接引用；步骤8完成：无冲突；步骤9完成：log.md 追加记录。⚠️ 视频待 Whisper 转录后需重新补充 Summary/Key Claims/Key Quotes 内容。
|
||||
|
||||
## [2026-05-04] ingest | CTP Topic 2 Git
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/06_CI_CD_GitOps/ctp-topic-2-git.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Git 版本控制基础与实践学习视频（状态：待 Whisper 转录）。源文件仅有 frontmatter 元数据，含 tags: [Git, VCS, CTP]，视频未转录，Summary/Key Claims/Key Quotes 均标记为待补充。已与同分类下其他 CTP CI/CD GitOps 来源建立 Connections 链接。
|
||||
- Concepts created: [[GitOps]]（已存在，引用）
|
||||
- Entities created: （无新建 — 源文件未提及具体人物）
|
||||
- Source page: wiki/sources/ctp-topic-2-git.md
|
||||
- Notes: 步骤3完成：新建 source page（含 frontmatter、Summary、Key Claims、Key Quotes、Key Concepts、Key Entities、Connections、Contradictions 八节）；步骤4完成：index.md 第288行已有条目，以正确格式补充日期和一行摘要；步骤5完成：overview.md 无需修订（该来源属于 CTP DevOps 系列，overview 中 Git 相关内容不涉及 CTP 上下文）；步骤6完成：无新建 Entity 页面（源文件无具体人物）；步骤7完成：GitOps Concept 页面已存在，直接引用；步骤8完成：无冲突；步骤9完成：log.md 追加记录。⚠️ 视频待 Whisper 转录后需重新补充 Summary/Key Claims/Key Quotes 内容。
|
||||
|
||||
## [2026-04-29] ingest | CTP Topic 49 Container Lifecycle Hardening Standards
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/07_Security/ctp-topic-49-container-lifecycle-hardening-standards.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Micro Focus 容器镜像构建阶段 11 项安全加固标准，涵盖基础镜像选择、Init 系统、只读文件系统、私有服务账号等
|
||||
- Concepts created: Container Lifecycle Hardening（已存在）, Read-Only Root Filesystem（已存在）, Init System in Containers（已存在）, Kubernetes Security Context（已存在）, Container Image Scanning（已存在）, Principle of Least Privilege（已存在）, Network Isolation（已存在）
|
||||
- Entities created: Ashish（已存在）, Micro Focus（已存在）, Kubernetes（已存在）, Product Security Group（已存在）
|
||||
- Source page: wiki/sources/ctp-topic-49-container-lifecycle-hardening-standards.md
|
||||
- Notes: Entity 和 Concept 页面在之前的 batch ingest 中已创建，本次仅生成 source 页面
|
||||
|
||||
## [2026-05-04] ingest | CTP Topic 55 AWS Firewall Manager
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/07_Security/ctp-topic-55-aws-firewall-manager.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: AWS Firewall Manager 在 Grand Torque 多 Landing Zone 环境中的集中化安全策略管理实践。核心动机：跨 RLABS/R&D/SAS/CAT 多个 Landing Zone 管理安全策略的复杂性；原有 Checkpoint Firewall 无法完全覆盖公网子网流量安全。核心方案：①在独立 Firewall Manager 账户创建安全组策略，指定目标账户或 OU，自动将基线安全组附加到现有和新实例；②三种策略类型——通用安全组（允许产品团队自增）、审计与强制安全组规则（拒绝过度宽松规则，支持手动或自动修复）、清理未使用冗余安全组；③通过 RAM Prefix List 跨账户共享规则，支持 Atlantis CI/CD 流水线部署。Demo 演示了策略创建后 EC2 实例的自动附加与策略删除后的自动移除。前提条件：OU 内管理员权限 + AWS Config 全账户启用。
|
||||
- Concepts touched: [[AWS Firewall Manager]], [[Security Group Policy]], [[AWS Config]], [[AWS Lambda]], [[Prefix List]], [[AWS RAM]], [[Landing Zone]]
|
||||
- Entities touched: [[Grand Torque Landing Zone]], [[LAPS Landing Zone]], [[SAS Landing Zone]], [[Digital Factory Landing Zone]], [[Atlantis Server]], [[QALIS]]
|
||||
- Concepts created: [[AWS Firewall Manager]], [[Security Group Policy]]
|
||||
- Entities created: (无新建 — Landing Zone Entity 页面待后续批量整理)
|
||||
- Source page: wiki/sources/ctp-topic-55-aws-firewall-manager.md
|
||||
- Notes: 步骤3完成：新建 source page（严格按 Source Page Format，含 frontmatter、Summary、Key Claims、Key Quotes、Key Concepts、Key Entities、Connections、Contradictions 八节）；步骤4完成：index.md 第277行已有条目，本次补充日期和一行摘要；步骤5完成：overview.md 第319行已有详细条目，本次无需修订；步骤6完成：无新建 Entity 页面（Landing Zone Entity 页面待后续批量整理 CTP Security 相关实体）；步骤7完成：新建2个 Concept 页面（AWS-Firewall-Manager、Security-Group-Policy）；步骤8完成：无冲突（Firewall Manager 与 Checkpoint Firewall 为互补关系，非竞争替代，详见 source page Contradictions 节）；步骤9完成：log.md 追加记录
|
||||
|
||||
## [2026-05-04] ingest | CTP Topic 62 AWS Secrets Manager
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/07_Security/ctp-topic-62-aws-secrets-manager.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: AWS Secrets Manager 企业实施与标准化——Nurit 和 Daniel 主讲。是前一年 7 月学习会议的续篇，介绍了 AWS Secrets Management Standard 文档，分享了实施机会。核心内容：①Secrets 管理平台选型（HashiCorp Vault vs AWS Secrets Manager，后者因成本更低被选中）；②三阶段实施方法（集中 Secrets → 调整自动化获取 → 启动轮换）；③Lambda 函数配合 JDBC Wrapper 实现无密码 Oracle 数据库访问；④SendGrid API Key 集中轮换方案；⑤通过 Control Tower 实现企业级 Secrets 标准化管理。
|
||||
- Concepts touched: [[SecretsManagement]], [[SecretRotation]], [[JDBCWrapper]], [[ControlTower]]
|
||||
- Entities touched: [[Nurit]], [[Daniel]], [[Victor]], [[HashiCorpVault]], [[AWSControlTower]], [[SendGrid]]
|
||||
- Concepts created: [[SecretsManagement]], [[SecretRotation]], [[JDBCWrapper]]
|
||||
- Entities created: (无新建 — Entity 页面待后续整理)
|
||||
- Source page: wiki/sources/ctp-topic-62-aws-secrets-manager.md
|
||||
- Notes: 步骤3完成：新建 source page；步骤4完成：index.md 条目已存在（第275行），本次以正确格式更新并补充摘要；步骤5完成：overview.md 无需修订（该来源属于 CTP Security 系列，overview 中有相关上下文）；步骤6完成：无新建 Entity 页面（待后续批量整理 CTP Security 相关人物）；步骤7完成：新建3个 Concept 页面（SecretsManagement、SecretRotation、JDBCWrapper）；步骤8完成：无冲突（与 HashiCorp Vault 的对比属技术选型视角差异，已记录于 Contradictions 节）；步骤9完成：log.md 追加记录
|
||||
|
||||
## [2026-04-28] ingest | CTP Topic 65 Tracing the Value Delivered in Cloud Transformation
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/10_OpenText-Series/ctp-topic-65-tracing-the-value-delivered-in-cloud-transformation.md
|
||||
- Status: ✅ 成功摄入
|
||||
@@ -5172,6 +5274,22 @@
|
||||
- Key Concepts 中 Kubernetes/Atlantis 已有 wikilink 指向其他 Source page
|
||||
- 冲突检测：与 ctp-topic-39（Atlantis 不支持 EKS）存在 Atlantis + Kubernetes 实践约束差异，已记录于 Source page Contradictions
|
||||
|
||||
## [2026-05-09] ingest | CTP Topic 33 An Introduction to GitOps (re-ingest)
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/06_CI_CD_GitOps/ctp-topic-33-an-introduction-to-gitops.md
|
||||
- Status: ✅ 成功摄入（re-ingest）
|
||||
- Summary: Source page 已存在（2026-04-25 初版）。本次补充 `last_updated: 2026-05-09` 到 source page frontmatter；index.md 条目补充日期前缀 [2026-04-14] 和一行摘要；overview.md 第247行已有该来源详细摘要，内容一致无需修订；GitOps.md Concept 页面已存在且 sources 列表已包含本来源，无需重复更新；Victor Etkin 和 Weaveworks Entity 页面仍未达 ≥2 次条件，保持 wikilink 引用。
|
||||
- Concepts created: （无新建 — [[GitOps]] Concept 页面已存在且已引用本来源）
|
||||
- Entities identified: （无新建 — Victor Etkin 和 Weaveworks 仅出现 1 次，未达 ≥2 次条件）
|
||||
- Source page: wiki/sources/ctp-topic-33-an-introduction-to-gitops.md
|
||||
- Notes:
|
||||
- 步骤3完成：Source page 已存在（2026-04-25 初版，62行），内容完整，本次补充 last_updated: 2026-05-09
|
||||
- 步骤4完成：index.md 第288行条目补充日期前缀 [2026-04-14] 和一行摘要
|
||||
- 步骤5完成：overview.md 第247行已有该来源详细摘要，内容一致无需修订
|
||||
- 步骤6完成：无新建 Entity 页面（Victor Etkin/Weaveworks 仅出现 1 次，未达阈值）
|
||||
- 步骤7完成：无新建 Concept 页面（GitOps.md 已存在且已引用本来源为 source）
|
||||
- 步骤8完成：冲突已在原 source page Contradictions 节记录（与 ctp-topic-39 Atlantis + EKS 实践约束差异）
|
||||
- 步骤9完成：log.md 追加本次 re-ingest 记录
|
||||
|
||||
## [2026-04-24] ingest | CTP Topic 56 Automated Infrastructure Testing
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/06_CI_CD_GitOps/ctp-topic-56-automated-infrastructure-testing.md
|
||||
- Status: ✅ 成功摄入
|
||||
@@ -6111,3 +6229,14 @@
|
||||
- Entities created: [[Mike]], [[Ed]], [[BrightCloud]]
|
||||
- Source page: wiki/sources/public-cloud-learning-sessions-opentext-gis-security-policies-20241015-160257-me.md
|
||||
- Notes: 步骤3完成：source page 已存在，内容确认/更新；步骤4完成：index.md 条目已存在（第274行），无需更新；步骤5完成：overview.md 无需修订（OpenText 安全专题系列，overview 已覆盖）；步骤6完成：新建3个 Entity 页面（Mike.md、Ed.md、BrightCloud.md）；步骤7完成：新建6个 Concept 页面（GISP、ISO-27001、Security Awareness Training、Third Party Penetration Testing、Threat Intelligence、FedRAMP）；步骤8完成：与 CTP-Topic-10 和 CTP-Topic-52 互补而非冲突；步骤9完成：log.md 追加记录
|
||||
|
||||
## [2026-05-11] ingest | CTP Topic 37 Secrets Certificates Management
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/07_Security/ctp-topic-37-secrets-certificates-management.md
|
||||
- Status: ✅ 成功摄入（re-ingest：规范化 Source 页面引用 + 补充缺失 Entity/Concept）
|
||||
- Summary: CCLE 团队主导的密钥与证书管理解决方案选型——评估 AWS Secrets Manager、HashiCorp Vault、CYBERARK Micro Focus PAM 三款产品，30天试点选定 AWS Secrets Manager。实施阶段从 Control Tower + CI/CD 流程清除明文密码。属 [[SecretsManagement]] 选型评估原始记录，与 [[ctp-topic-62-aws-secrets-manager]] 构成"评估→实施"完整链路。
|
||||
- Concepts touched: [[SecretsManagement]], [[SecretRotation]], [[Privileged-Access-Management]], [[CI/CD-Secrets]], [[HashiCorp]]
|
||||
- Entities touched: [[MicroFocus]], [[CCLE]], [[AWS]], [[HashiCorp]], [[CyberArk]]
|
||||
- Concepts created: [[Privileged-Access-Management]], [[CI/CD-Secrets]]
|
||||
- Entities created: [[CCLE]], [[CyberArk]]
|
||||
- Source page: wiki/sources/ctp-topic-37-secrets-certificates-management.md
|
||||
- Notes: 步骤3完成：规范化 Source 页面 Key Concepts/Key Entities 引用格式，修正 HashiCorp-Vault（应属 Entity 而非 Concept）；步骤4完成：index.md 条目已存在（第279行），无需更新；步骤5完成：overview.md 补充 Topic 37 独立条目（与 Topic 62 构成"评估→实施"两阶段链路）；步骤6完成：新建2个 Entity 页面（CCLE.md、CYBERArk.md）；步骤7完成：新建2个 Concept 页面（Privileged-Access-Management.md、CI/CD-Secrets.md）；步骤8完成：与 [[ctp-topic-62-aws-secrets-manager]] 存在视角差异但非冲突（前者快速试点 vs 后者深度实施），已在 Contradictions 节记录；步骤9完成：log.md 追加记录
|
||||
|
||||
@@ -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