Auto-sync: 2026-04-19 00:02
This commit is contained in:
38
wiki/entities/AWS-Redshift.md
Normal file
38
wiki/entities/AWS-Redshift.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: "AWS Redshift"
|
||||
type: entity
|
||||
tags: [AWS, data-warehouse]
|
||||
sources: [ctp-topic-68-introduction-to-redshift]
|
||||
last_updated: 2026-04-18
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
AWS Redshift 是 Amazon 提供的完全托管的 PB 级云端数据仓库服务,专为数据仓库场景设计,支持 OLAP(在线分析处理)。
|
||||
|
||||
## Definition
|
||||
|
||||
- **类型**:数据仓库服务
|
||||
- **提供商**:AWS
|
||||
- **规模**:PB 级
|
||||
- **用途**:在线分析处理(OLAP),快速从大型数据集检索数据
|
||||
|
||||
## Key Attributes
|
||||
|
||||
- **架构类型**:Leader Node + Compute Node
|
||||
- **存储类型**:列式存储
|
||||
- **压缩**:支持 LZO 等压缩编码
|
||||
- **实例类型**:Dense Compute、Dense Storage、RA3
|
||||
|
||||
## Key Features
|
||||
|
||||
- 完全托管(Easy to install, maintain, backups)
|
||||
- 点时间恢复
|
||||
- 跨区域灾难恢复
|
||||
- 按使用量付费
|
||||
|
||||
## Connections
|
||||
|
||||
- [[AWS]] → 提供 → [[AWS-Redshift]]
|
||||
- [[AWS-Redshift]] → 管理通过 → [[Leader-Node]]
|
||||
- [[AWS-Redshift]] → 执行查询通过 → [[Compute-Node]]
|
||||
27
wiki/entities/Active-Directory.md
Normal file
27
wiki/entities/Active-Directory.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
title: "Active Directory"
|
||||
type: entity
|
||||
tags:
|
||||
- Identity
|
||||
- Microsoft
|
||||
- Authentication
|
||||
date-added: 2026-04-18
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- AD
|
||||
- Windows Server AD
|
||||
|
||||
## Description
|
||||
Microsoft 的目录服务,提供身份验证和资源访问控制。在 SaaS Landing Zone 中,Active Directory Account 包含两个 AD 节点,用于域加入和控制资源访问。
|
||||
|
||||
## Role in Architecture
|
||||
- 支持 Windows 实例域加入
|
||||
- 身份验证和访问控制
|
||||
- 两个 AD 节点提供高可用性
|
||||
- 远程访问通过 AD 进行身份验证(从 Checkpoint VPN 迁移到 Pulse VPN)
|
||||
|
||||
## Related
|
||||
- [[Microsoft]]:开发公司
|
||||
- [[Domain Join]]:通过 SRE-provided AMIs 实现自动化域加入
|
||||
- [[ctp-topic-17-active-directory-services-in-gruntwork-aws-lzs]]:Gruntwork AWS Landing Zones 中的 AD 服务集成
|
||||
16
wiki/entities/Amazon-Inspector.md
Normal file
16
wiki/entities/Amazon-Inspector.md
Normal file
@@ -0,0 +1,16 @@
|
||||
---
|
||||
title: "Amazon Inspector"
|
||||
type: entity
|
||||
tags: [AWS, Security]
|
||||
---
|
||||
|
||||
## Definition
|
||||
Amazon Inspector 是 AWS 的自动化安全漏洞扫描服务,用于评估 AWS 资源的安全性和合规性。
|
||||
|
||||
## Functions
|
||||
- 漏洞扫描
|
||||
- 安全合规评估
|
||||
- 自动化测试集成
|
||||
|
||||
## Connections
|
||||
- 与 Standard AMI 集成,用于镜像验证
|
||||
32
wiki/entities/CCOE.md
Normal file
32
wiki/entities/CCOE.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: "CCOE (Cloud Center of Excellence)"
|
||||
type: entity
|
||||
tags:
|
||||
- AWS
|
||||
- Cloud Governance
|
||||
aliases:
|
||||
- Cloud Center of Excellence
|
||||
---
|
||||
|
||||
## Definition
|
||||
CCOE(Cloud Center of Excellence,云端卓越中心)是推动云采纳和治理的核心组织单元,负责制定云标准、发布标准化 AMI、管理云最佳实践。
|
||||
|
||||
## Role in CTP
|
||||
- 每两个月发布一次符合安全标准的加固 AMI
|
||||
- 管理 AMI 路线图(Roadmap),规划新操作系统的添加
|
||||
- 通过 CCOE 通知邮件列表(PDL)发送 AMI 变更通知
|
||||
- 提供 Change Log,记录与上一版本的变更内容
|
||||
|
||||
## Key Activities
|
||||
- AMI 标准制定和安全加固
|
||||
- 操作系统生命周期管理(EOL 跟踪)
|
||||
- 新 AMI 集成验证流程
|
||||
- 与组织内各团队协调需求
|
||||
|
||||
## Related Concepts
|
||||
- [[Standard AMI]]
|
||||
- [[AMI-End-of-Life]]
|
||||
- [[EC2-Image-Builder]]
|
||||
|
||||
## Last Updated
|
||||
2026-04-18
|
||||
17
wiki/entities/Cloud-Technology-Design-Forum.md
Normal file
17
wiki/entities/Cloud-Technology-Design-Forum.md
Normal file
@@ -0,0 +1,17 @@
|
||||
---
|
||||
title: "Cloud Technology Design Forum"
|
||||
type: entity
|
||||
tags: [cloud, organization, micro-focus]
|
||||
---
|
||||
|
||||
## Summary
|
||||
Cloud Technology Design Forum 是微焦点(Micro Focus)内部的组织,旨在标准化和集中化其云交付产品,包括 Landing Zone 设计。
|
||||
|
||||
## Role
|
||||
- 组织内部用于推动云架构标准化的核心团队
|
||||
- 负责定义和维护企业级云交付标准
|
||||
|
||||
## Connections
|
||||
- [[Gruntwork Landing Zone]] — 提供参考架构标准
|
||||
- [[AWS]] — 云平台提供商
|
||||
- [[Gruntwork]] — Landing Zone 框架提供商
|
||||
24
wiki/entities/Compute-Node.md
Normal file
24
wiki/entities/Compute-Node.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: "Compute Node"
|
||||
type: entity
|
||||
tags: [AWS, Redshift]
|
||||
sources: [ctp-topic-68-introduction-to-redshift]
|
||||
last_updated: 2026-04-18
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
Redshift 架构中的计算节点,负责实际查询执行。
|
||||
|
||||
## Definition
|
||||
|
||||
Redshift 集群中执行查询的节点,查询在切片(slice)上处理数据。
|
||||
|
||||
## Key Attributes
|
||||
|
||||
- **职责**:执行查询、处理数据、返回结果到 Leader Node
|
||||
- **资源**:取决于实例类型(CPU、RAM、存储)
|
||||
|
||||
## Connections
|
||||
|
||||
- [[AWS-Redshift]] → 使用 → [[Compute-Node]]
|
||||
28
wiki/entities/Infoblox.md
Normal file
28
wiki/entities/Infoblox.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: "Infoblox"
|
||||
type: entity
|
||||
tags:
|
||||
- DNS
|
||||
- DHCP
|
||||
- Network
|
||||
---
|
||||
|
||||
## Definition
|
||||
Infoblox 是一家专注于 DNS、DHCP 和 IP 地址管理(IPAM)解决方案的企业软件公司。其核心产品包括 NIOS(Network Infrastructure Operating System)和 Infoblox Grid 架构。
|
||||
|
||||
## Key Products
|
||||
- **NIOS**:Infoblox 网络基础设施操作系统,运行在 Infoblox 设备上
|
||||
- **Infoblox Grid**:分布式架构,通过 Grid Master 统一管理全球分布的 DNS/DHCP 器具,确保配置的一致性和高可用性
|
||||
|
||||
## Key Capabilities
|
||||
- **DNS Anycast**:通过 DNS Anycast 技术实现全球范围内的低延迟和自动故障转移
|
||||
- **DNS Security**:防护 DNS 隧道攻击、数据外泄、缓存污染等高级威胁
|
||||
- **DHCP Automation**:自动化 IP 地址分配和管理
|
||||
|
||||
## Use Cases
|
||||
- 企业内网 DNS 服务
|
||||
- DNS 安全防护
|
||||
- IP 地址管理(IPAM)
|
||||
|
||||
## Connections
|
||||
- [[DNS-Anycast]] ← provided_by ← Infoblox
|
||||
25
wiki/entities/Jenkins.md
Normal file
25
wiki/entities/Jenkins.md
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: "Jenkins"
|
||||
type: entity
|
||||
tags:
|
||||
- CI/CD
|
||||
- Automation
|
||||
- DevOps
|
||||
date-added: 2026-04-18
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- Jenkins CI
|
||||
- Jenkins Server
|
||||
|
||||
## Description
|
||||
开源自动化服务器,主要用于持续集成(CI)和持续交付(CD)。在 SaaS Landing Zone 架构中,Shared Account 托管主 Jenkins 服务器,通过 Lambda 函数触发各账号的 Jenkins slaves 执行部署任务。
|
||||
|
||||
## Role in Architecture
|
||||
- 主 Jenkins 服务器位于 Shared Account,负责管理部署流程
|
||||
- 通过 Lambda 函数在各账号触发 Jenkins slaves
|
||||
- 增强安全性:主 Jenkins 不直接暴露给 jobs 或 credentials
|
||||
|
||||
## Related
|
||||
- [[Terraform]]:用于基础设施即代码部署
|
||||
- [[Gruntwork Landing Zone]]:参考架构
|
||||
22
wiki/entities/Kishore-Garlopati.md
Normal file
22
wiki/entities/Kishore-Garlopati.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
title: Kishore Garlopati
|
||||
type: entity
|
||||
tags: [person]
|
||||
date: 2026-04-14
|
||||
---
|
||||
|
||||
## Summary
|
||||
- 角色:讲师
|
||||
- 组织:Micro Focus
|
||||
- 贡献:介绍 Azure Landing Zone 架构设计与实现
|
||||
|
||||
## Key Facts
|
||||
- 在 CTP Topic 34 中讲解 Azure Landing Zone Architecture Overview
|
||||
- 阐述了在 Micro Focus 实施 Azure Landing Zone 的目标和策略
|
||||
|
||||
## Connections
|
||||
- [[Micro Focus]] ← works_at ← [[Kishore Garlopati]]
|
||||
- [[Kishore Garlopati]] ← presents ← [[Azure Landing Zone]]
|
||||
|
||||
## Aliases
|
||||
- Kishore
|
||||
23
wiki/entities/Leader-Node.md
Normal file
23
wiki/entities/Leader-Node.md
Normal file
@@ -0,0 +1,23 @@
|
||||
---
|
||||
title: "Leader Node"
|
||||
type: entity
|
||||
tags: [AWS, Redshift]
|
||||
sources: [ctp-topic-68-introduction-to-redshift]
|
||||
last_updated: 2026-04-18
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
Redshift 集群中的领导节点,负责 schema 管理、元数据存储和查询规划。
|
||||
|
||||
## Definition
|
||||
|
||||
Redshift 架构中的主节点,负责协调查询规划和结果返回。
|
||||
|
||||
## Key Attributes
|
||||
|
||||
- **职责**:Schema 管理、元数据存储、查询规划、指令分发、结果存储
|
||||
|
||||
## Connections
|
||||
|
||||
- [[AWS-Redshift]] → 使用 → [[Leader-Node]]
|
||||
24
wiki/entities/Pradeep.md
Normal file
24
wiki/entities/Pradeep.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
id: Pradeep
|
||||
title: "Pradeep"
|
||||
type: entity
|
||||
tags:
|
||||
- AWS
|
||||
- Landing-Zone
|
||||
- CTP
|
||||
- Checkpoint
|
||||
date_added: 2026-04-18
|
||||
---
|
||||
|
||||
## Profile
|
||||
- **Role:** AWS Landing Zone 技术分享主讲人
|
||||
- **Affiliation:** Cloud Transformation Program (CTP)
|
||||
- **Topic:** Checkpoint 防火墙的有序层逻辑
|
||||
|
||||
## Notes
|
||||
- 在 CTP Topic 10 中演示 Checkpoint 防火墙的 Ordered Layer 逻辑
|
||||
- 讲解防火墙如何根据标签对流量进行分层过滤
|
||||
- 包括地理屏蔽、BU 隔离、产品隔离及环境隔离
|
||||
|
||||
## Aliases
|
||||
- Pradeep
|
||||
24
wiki/entities/Route-53.md
Normal file
24
wiki/entities/Route-53.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: "Route 53"
|
||||
type: entity
|
||||
tags:
|
||||
- DNS
|
||||
- AWS
|
||||
date-added: 2026-04-18
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- Amazon Route 53
|
||||
- AWS DNS
|
||||
|
||||
## Description
|
||||
Amazon 的 DNS 服务,在 SaaS Landing Zone 中,DNS Account 托管 Route 53,每个产品拥有自己的托管区域(Hosted Zone)用于管理 DNS 记录。
|
||||
|
||||
## Role in Architecture
|
||||
- 集中式 DNS 管理
|
||||
- 每个产品拥有独立的托管区域
|
||||
- 支持公有和私有托管区域
|
||||
|
||||
## Related
|
||||
- [[AWS]]:云服务提供商
|
||||
- [[ctp-topic-7-saas-landing-zone-design]]:SaaS Landing Zone 设计
|
||||
26
wiki/entities/Standard-AMI.md
Normal file
26
wiki/entities/Standard-AMI.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
title: "Standard AMI"
|
||||
type: entity
|
||||
tags: [AWS, Cloud, Infrastructure]
|
||||
---
|
||||
|
||||
## Definition
|
||||
Standard AMI (Amazon Machine Image) 是 AWS 的标准化机器镜像,包含 OS 加固、最新安全补丁和补丁更新,并支持域集成、安全工具、端点保护、SSM agent、DNS 设置。
|
||||
|
||||
## Specifications
|
||||
- 每两个月构建、测试并发布
|
||||
- 支持 23 种不同操作系统
|
||||
- 最新三个版本在 12 个区域可用
|
||||
- 旧版本存档 12 个月
|
||||
|
||||
## Functions
|
||||
- OS 加固
|
||||
- 安全更新
|
||||
- 域集成
|
||||
- SSM agent 集成
|
||||
- DNS 设置
|
||||
|
||||
## Connections
|
||||
- 构建工具:[[EC2 Image Builder]]
|
||||
- 测试工具:[[Amazon Inspector]]
|
||||
- CI/CD:[[Jenkins]]
|
||||
23
wiki/entities/Steve-Jarman.md
Normal file
23
wiki/entities/Steve-Jarman.md
Normal file
@@ -0,0 +1,23 @@
|
||||
---
|
||||
id: Steve-Jarman
|
||||
title: "Steve Jarman"
|
||||
type: entity
|
||||
tags:
|
||||
- AWS
|
||||
- Landing-Zone
|
||||
- CTP
|
||||
date_added: 2026-04-18
|
||||
---
|
||||
|
||||
## Profile
|
||||
- **Role:** AWS Landing Zone 技术分享主讲人
|
||||
- **Affiliation:** Cloud Transformation Program (CTP)
|
||||
- **Topic:** AWS Landing Zones 部署流程、数据收集策略、标签安全控制
|
||||
|
||||
## Notes
|
||||
- 在 CTP Topic 10 中介绍 Landing Zone 的规划与自动化
|
||||
- 强调在部署前必须深入了解业务部门(BU)的资产清单、IP 地址空间及数据敏感性
|
||||
- 提及 DNS、Transit Gateway 等基础服务的创建已通过 SRE 团队实现了高度自动化
|
||||
|
||||
## Aliases
|
||||
- Steve Jarman
|
||||
Reference in New Issue
Block a user