Auto-sync: update nexus workspace
This commit is contained in:
55
wiki/concepts/Tagging.md
Normal file
55
wiki/concepts/Tagging.md
Normal file
@@ -0,0 +1,55 @@
|
||||
---
|
||||
title: "Tagging"
|
||||
type: concept
|
||||
tags:
|
||||
- AWS
|
||||
- Resource-Management
|
||||
- Governance
|
||||
- Cost-Optimization
|
||||
sources:
|
||||
- ctp-topic-27-aws-instance-scheduler
|
||||
- ctp-topic-28-aws-tag-validation-tool
|
||||
last_updated: 2026-05-12
|
||||
---
|
||||
|
||||
## Tagging
|
||||
|
||||
AWS 资源标签化(Tagging)是通过在 AWS 资源上附加键值对元数据来实现资源分组、归类和自动化策略关联的管理机制。
|
||||
|
||||
## Role in AWS Instance Scheduler
|
||||
|
||||
Instance Scheduler 通过实例上的特定标签来关联调度逻辑:
|
||||
|
||||
| 标签键 | 说明 | 示例值 |
|
||||
|--------|------|--------|
|
||||
| `Schedule` | 关联调度名称 | `Seattle-9-5` |
|
||||
| `Period` | 关联周期名称 | `Weekdays-Business-Hours` |
|
||||
| `Override` | 覆盖状态 | `true`(强制停止)/ `false`(正常调度) |
|
||||
|
||||
## Key Tags for Instance Scheduler
|
||||
|
||||
- **`Schedule`**:将实例关联到 DynamoDB Config Table 中的调度定义
|
||||
- **`Period`**:将实例关联到具体的周期(开始/结束时间、工作日)
|
||||
- **`InstanceType`**:标识实例类型(EC2/RDS),影响调度行为差异
|
||||
|
||||
## AWS Tagging Best Practices
|
||||
|
||||
- **一致性命名**:使用标准化前缀(如 `Environment:`、`Team:`、`CostCenter:`)
|
||||
- **必填标签**:Enforce Tag 策略要求所有资源必须附有特定标签
|
||||
- **自动化标签**:通过 AWS Config Rules 或 Lambda 自动补全缺失标签
|
||||
- **标签验证**:使用 Tag Editor 或第三方工具(如 ctp-topic-28-aws-tag-validation-tool)确保标签合规
|
||||
|
||||
## Relationship to Governance
|
||||
|
||||
Tagging 是 AWS 云治理的基石,支持:
|
||||
|
||||
- **成本归因**:按团队/项目/环境追踪云支出
|
||||
- **访问控制**:基于标签的 IAM 策略
|
||||
- **自动化操作**:Instance Scheduler、自动化备份等均依赖标签
|
||||
- **资源分组**:跨服务和账户的资源发现与分组
|
||||
|
||||
## Related Pages
|
||||
- [[AWS-Instance-Scheduler]] — 核心使用场景
|
||||
- [[ctp-topic-27-aws-instance-scheduler]] — 原始来源
|
||||
- [[ctp-topic-28-aws-tag-validation-tool]] — 标签验证工具
|
||||
- [[ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co]] — FinOps 标签策略
|
||||
Reference in New Issue
Block a user