57 lines
2.5 KiB
Markdown
57 lines
2.5 KiB
Markdown
---
|
||
title: "CTP Topic 58 AWS EC2 Image Builder"
|
||
type: source
|
||
tags: [AWS, EC2, Image Builder, CTP]
|
||
date: 2026-04-14
|
||
---
|
||
|
||
## Source File
|
||
- [[raw/Cloud & DevOps/Public-Cloud-Learning-Sessions/01_AWS-Landing-Zone/ctp-topic-58-aws-ec2-image-builder.md]]
|
||
|
||
## Summary
|
||
|
||
- **核心主题**: AWS EC2 Image Builder 服务，用于自动创建、管理和分发 AMIs 和 Docker 镜像
|
||
- **问题域**: 企业镜像构建标准化、CI/CD 流程优化、安全加固自动化
|
||
- **方法/机制**:
|
||
- Image Pipeline 定义 AMI 发布方式，包括安装、安全加固和发布计划
|
||
- Image Recipe（YAML 格式）定义源 AMI 和输出 AMI 规格
|
||
- Component 定义在源 AMI 中执行的具体步骤（安装包或 shell 命令）
|
||
- Infrastructure Configuration 定义实例属性（实例类型、VPC、子网、安全组）
|
||
- Distribution Settings 管理跨区域和账号的 AMI 分发
|
||
|
||
## Key Claims
|
||
|
||
- Image Builder 通过自动化提高生产力，在构建过程中集成测试，加载安全加固标准
|
||
- 与 AWS Organizations 和 AWS RAM 集成，支持跨托管账号分发 AMI
|
||
- 当前 AMI 发布流程存在缺陷：修改周转时间长、AMI 不兼容、手动流程自动化程度低
|
||
|
||
## Key Quotes
|
||
|
||
> "A component is basically just a particular step that you want to execute in order to achieve the output AMI."
|
||
|
||
> "Due to these limitations, product teams try to cater to their requirements by developing their own workflow or CI/CD pipelines, consuming the CCOE AMI and installing their required packages."
|
||
|
||
## Key Concepts
|
||
|
||
- [[EC2 Image Builder]]: AWS 托管服务，用于自动化创建、管理和分发 AMIs 和 Docker 镜像
|
||
- [[Standard AMI]]: 包含 OS 加固脚本、安全补丁的标准化机器镜像
|
||
- [[Infrastructure as Code]]: 通过 Terraform 模块创建和管理 Image Builder 资源
|
||
|
||
## Key Entities
|
||
|
||
- [[AWS]]: Amazon Web Services，云服务提供商
|
||
- [[Terraform]]: 基础设施即代码工具，用于创建和管理 Image Builder 资源
|
||
- [[CTP]]: Cloud Transformation Program，云转型计划项目
|
||
|
||
## Connections
|
||
|
||
- [[AWS]] ← provides ← [[EC2 Image Builder]]
|
||
- [[EC2 Image Builder]] ← uses ← [[Terraform]] ← manages_infrastructure ← [[Standard AMI]]
|
||
- [[CTP]] ← consumes ← [[Standard AMI]]
|
||
|
||
## Contradictions
|
||
|
||
- **与手动 AMI 构建流程**:
|
||
- **冲突点**: 手动 AMI 构建和 EC2 Image Builder 的取舍
|
||
- **当前观点**: 手动流程效率低，周转时间长，不适合大规模自动化
|
||
- **对方观点**: 手动流程提供更多控制，适合特定场景 |