AWS AmazonCloudWatch: New CloudWatch Omni IAM managed policies and V2 integration policy
Summary
Documents new/updated AWS managed policies for CloudWatch Omni: CloudWatchOmniAWSIntegrationPolicyV2 (adds read access to logs, traces, and profiles in the account's default CloudWatch Dataset plus kms:Decrypt), CloudWatchOmniDevOpsAgentInvestigationServiceRolePolicy (aidevops task/topology actions scoped to the account's own agent spaces), and CloudWatchOmniSpaceAccessPolicy updates (agent asset CRUD, cloudwatch:PutRecords, role-template IAM permissions, tagging deny carve-out). Adds an Important note instructing replacement of the V1 policy and describing the broadened data-read scope.
Security assessment
This is IAM permission documentation: it introduces a policy granting read access to telemetry content (logs, traces, profiles) across all Regions with kms:Decrypt, and explicitly warns that access grants do not limit these permissions, plus documents new role-creation and tagging-deny carve-out permissions. It is security-relevant permission-boundary/least-privilege guidance, but it documents a capability change rather than remediating a specific vulnerability.
Evidence
+If your space operator role has `CloudWatchOmniAWSIntegrationPolicy`, replace it with `CloudWatchOmniAWSIntegrationPolicyV2`. `CloudWatchOmniAWSIntegrationPolicy` does not let CloudWatch Omni read the logs, traces, and profiles in your account's `default` CloudWatch Dataset. `CloudWatchOmniAWSIntegrationPolicyV2` includes every permission in `CloudWatchOmniAWSIntegrationPolicy`, so the role does not need both. The permissions that `CloudWatchOmniAWSIntegrationPolicyV2` adds read the content of the `default` Dataset in every Region of your account, and access grants do not limit them.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/omni-aws-managed-policies-for-cloudwatch-omni.md b/AmazonCloudWatch/latest/monitoring/omni-aws-managed-policies-for-cloudwatch-omni.md index 9814c41..8dbe796 100644 --- a//AmazonCloudWatch/latest/monitoring/omni-aws-managed-policies-for-cloudwatch-omni.md +++ b//AmazonCloudWatch/latest/monitoring/omni-aws-managed-policies-for-cloudwatch-omni.md @@ -22 +22,3 @@ Policy | What it grants -[CloudWatchOmniAWSIntegrationPolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/CloudWatchOmniAWSIntegrationPolicy.html) | Resource discovery for Context Graph: lets CloudWatch Omni discover resources and their relationships in an account. Optional on the space operator role — you choose it during space setup. In an organization Centralization rule, CloudWatch Omni also attaches it to the integration roles it provisions in each source account. +[CloudWatchOmniAWSIntegrationPolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/CloudWatchOmniAWSIntegrationPolicy.html) | Resource discovery for Context Graph: lets CloudWatch Omni discover resources and their relationships in an account. Optional on the space operator role — you choose it during space setup. In an organization Centralization rule, CloudWatch Omni also attaches it to the integration roles it provisions in each source account. On the space operator role, replace it with `CloudWatchOmniAWSIntegrationPolicyV2`, as the following note describes. +[CloudWatchOmniAWSIntegrationPolicyV2](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/CloudWatchOmniAWSIntegrationPolicyV2.html) | Everything in `CloudWatchOmniAWSIntegrationPolicy`, plus read access to the logs, traces, and profiles in your account's `default` CloudWatch Dataset. See [Permissions in CloudWatchOmniAWSIntegrationPolicyV2](./omni-iam-policies-to-use-cloudwatch-omni.html#omni-iam-policies-to-use-cloudwatch-omni-permissions-in-cloudwatchomniawsintegrationpolicyv2). In an organization Centralization rule, CloudWatch Omni attaches `CloudWatchOmniAWSIntegrationPolicy`, not this policy, to the integration roles in source accounts. +[CloudWatchOmniDevOpsAgentInvestigationServiceRolePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/CloudWatchOmniDevOpsAgentInvestigationServiceRolePolicy.html) | With this policy, you can have CloudWatch Omni run AWS DevOps Agent investigations for you. It can create and update tasks, read their progress and findings, and discover the topology of an agent space. It covers only agent spaces in your own account. CloudWatch Omni attaches it to the role that it creates when you connect the AWS DevOps Agent integration. @@ -24,0 +27,6 @@ Policy | What it grants +Important + +If your space operator role has `CloudWatchOmniAWSIntegrationPolicy`, replace it with `CloudWatchOmniAWSIntegrationPolicyV2`. `CloudWatchOmniAWSIntegrationPolicy` does not let CloudWatch Omni read the logs, traces, and profiles in your account's `default` CloudWatch Dataset. `CloudWatchOmniAWSIntegrationPolicyV2` includes every permission in `CloudWatchOmniAWSIntegrationPolicy`, so the role does not need both. The permissions that `CloudWatchOmniAWSIntegrationPolicyV2` adds read the content of the `default` Dataset in every Region of your account, and access grants do not limit them. + +To replace the policy, attach `CloudWatchOmniAWSIntegrationPolicyV2` to the role in IAM, and then detach `CloudWatchOmniAWSIntegrationPolicy`. Attach the new policy first so that resource discovery keeps working while you make the change. If your `default` Dataset is encrypted with a customer managed key, the key policy must also allow `kms:Decrypt` for the role. See [Sample key policy](./omni-data-encryption-in-cloudwatch-omni.html#omni-data-encryption-in-cloudwatch-omni-sample-key-policy). For the permissions that `CloudWatchOmniAWSIntegrationPolicyV2` adds, see [Permissions in CloudWatchOmniAWSIntegrationPolicyV2](./omni-iam-policies-to-use-cloudwatch-omni.html#omni-iam-policies-to-use-cloudwatch-omni-permissions-in-cloudwatchomniawsintegrationpolicyv2). + @@ -30,0 +39,2 @@ Change | Description | Date +[CloudWatchOmniSpaceAccessPolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/CloudWatchOmniSpaceAccessPolicy.html) — Updated policy | CloudWatch Omni added permissions to create and manage agent assets — `cloudwatch:CreateOmniAgentAsset`, `cloudwatch:GetOmniAgentAsset`, `cloudwatch:UpdateOmniAgentAsset`, `cloudwatch:ListOmniAgentAssets`, and `cloudwatch:DeleteOmniAgentAsset` — and `cloudwatch:PutRecords`, which CloudWatch uses to write GitHub change events to your account's `default` CloudWatch Dataset when you connect GitHub. Like the other space permissions, these require the `cloudwatch:HasAccessGrant` condition. The tagging deny now carves out the `omni-agent-asset/*` resource type, so a space session can tag its own agent assets. CloudWatch Omni also added IAM permissions to create two roles from CloudWatch-owned role templates: the partner integration role (`service-role/CloudWatchExternalAgentIntegration-*`) that it creates when a space admin connects a third-party investigation agent, and the AWS DevOps Agent investigation role (`service-role/CloudWatchOmniDevOpsAgentInvestigationRole-*`) that it creates when you connect the AWS DevOps Agent integration. | November 19, 2026 +[CloudWatchOmniDevOpsAgentInvestigationServiceRolePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/CloudWatchOmniDevOpsAgentInvestigationServiceRolePolicy.html) — New policy | CloudWatch Omni added a policy for running AWS DevOps Agent investigations for you. It grants `aidevops:CreateBacklogTask`, `aidevops:ListBacklogTasks`, `aidevops:GetBacklogTask`, `aidevops:UpdateBacklogTask`, `aidevops:ListJournalRecords`, `aidevops:ListExecutions`, and `aidevops:DiscoverTopology`, only on agent spaces in your own account. | November 19, 2026 @@ -31,0 +42 @@ Change | Description | Date +[CloudWatchOmniAWSIntegrationPolicyV2](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/CloudWatchOmniAWSIntegrationPolicyV2.html) — New policy | CloudWatch Omni added a policy that grants everything in `CloudWatchOmniAWSIntegrationPolicy`, plus read access to the logs, traces, and profiles in your account's `default` CloudWatch Dataset: the six telemetry query actions, the `cloudwatch:GetRecords` and `cloudwatch:GetProfileRecords` actions on the `default` Dataset, and `kms:Decrypt` through CloudWatch for the `default` Dataset, all in your own account. | November 16, 2026