---
格式版本: 2
标题: "Amazon CloudWatch log Centralization now supports log group tag propagation"
原文链接: "https://aws.amazon.com/cn/about-aws/whats-new/2026/08/amazon-cloudwatch-centralization-tag-propogation/"
发布日期: "2026-08-19"
发布时间校准状态: "found"
发布时间需复核: "否"
发布时间来源: "llm:local:original_script_field"
发布时间证据: "postDateTime: 2026-08-19T21:06:00Z"
发布时间校准原因: "候选日期来自页面脚本中的postDateTime字段，符合文章发布时间标注，且无其他冲突候选。"
发布时间校准置信度: "1"
发布时间候选数量: 1
发布时间严格候选数量: 0
发布时间原页读取状态: "source template page reused from URL open"
发布时间未找到原因: ""
发布时间校准时间: "2026-08-20T10:37:31+08:00"
发布时间仲裁状态: "confirmed"
发布时间仲裁尝试次数: 1
发布时间仲裁耗时毫秒: 51304
发现时间: "2026-08-20T10:31:30+08:00"
入库时间: "2026-08-20T02:38:24.442Z"
来源平台: "固定入口"
搜索渠道: "fixed_url"
搜索词: "https://aws.amazon.com/new"
匹配关键词:
  []
相关厂家:
  - "AWS"
相关专家:
  []
内容类型: "网页"
抓取工具: "Free Fetch + Defuddle"
清洗工具: "Defuddle Markdown + Defuddle/Readability 正文提取"
原始附件:
  []
AI优质: "否"
AI打分: 5
AI分档: "非优质"
AI质检状态: "不通过"
AI打分理由: "内容为AWS CloudWatch日志集中化功能更新，涉及日志标签传播，与超节点/AI Rack/机柜级AI基础设施完全无关，无技术架构或商业部署信号。"
AI质检模型: "ali-deepseek-v4-flash"
AI质检时间: "2026-08-20T10:39:03+08:00"
AI主题相关性: 0
AI来源权威性: 5
AI新颖性: 0
AI技术细节: 0
AI商业部署信号: 0
AI完整性: 5
AI摘要: "Amazon CloudWatch Centralization 现在可将源账户日志组的标签复制到目标日志组，并按规则设置保持同步，使成本、所有权和合规标签在集中后的日志中继续生效。"
AI摘要模型: "ali-deepseek-v4-flash"
AI摘要时间: "2026-09-07T03:16:55.010Z"
采集批次: "2026年8月20日10点15分53秒"
采集批次ID: "20260820-101553-437"
去重键: "https://aws.amazon.com/cn/about-aws/whats-new/2026/08/amazon-cloudwatch-centralization-tag-propogation"
---

Amazon CloudWatch Centralization now copies log group tags from source accounts to the destination log groups created by centralization rules. CloudWatch Centralization aggregates log data from multiple accounts and Regions into one destination account. With tag propagation, the cost, ownership, and compliance tags you maintain at the source now apply to the copied log groups.

With today's launch, CloudWatch copies the tags of each source log group to its destination log group and keeps them in sync based on the tag propogation behaviour selected as part of the centralization rule setup. For example, a platform team can preserve Application and CostCenter tags on centralized log groups, then use those tags to scope access with IAM conditions and report centralized log spend by team in AWS Cost Explorer.

Tag propagation is available in all AWS Regions where CloudWatch Centralization is available. For a list of Regions, see the [AWS Regions table](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/).

To get started, turn on tag propagation for a centralization rule in the Amazon CloudWatch console, or by using the AWS CLI or AWS SDKs. To learn more about centralizing logs while preserving their tags, see [Log Centralization User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatchLogs_Centralization.html). For Centralization pricing, see [Amazon CloudWatch pricing](https://aws.amazon.com/cloudwatch/pricing/).