AWS AmazonCloudWatch: Document new CloudWatchOmniAWSIntegrationPolicyV2 managed policy permissions
Summary
Adds a section describing the new CloudWatchOmniAWSIntegrationPolicyV2 managed policy: its telemetry query and GetRecords/GetProfileRecords read permissions on the account's default CloudWatch Dataset, its kms:Decrypt scope, the fact that it lacks the cloudwatch:HasAccessGrant condition, and the iam:CreateRole/PutRolePolicy/AttachRolePolicy/GetRoleTemplateVersion restrictions for partner and DevOps Agent integration roles. Also updates the policy overview table and navigation list.
Security assessment
The added text is IAM documentation: it enumerates permissions of a new managed policy, including sensitive data-read permissions (GetRecords/GetProfileRecords) that are explicitly noted as not gated by the cloudwatch:HasAccessGrant condition, plus iam:CreateRole/AttachRolePolicy/PassRole-style grants constrained by aws:ResourceAccount, aws:CalledVia, and iam:RoleTemplateARN conditions. This is security-relevant access-control documentation and a hardening note, but it documents a new feature rather than remediating a specific vulnerability or incident.
Evidence
`CloudWatchOmniAWSIntegrationPolicyV2` holds every permission in [CloudWatchOmniAWSIntegrationPolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/CloudWatchOmniAWSIntegrationPolicy.html), plus read access to the logs, traces, and profiles in your account's `default` CloudWatch Dataset. The read covers everything stored in the `default` Dataset, in every Region of your account, such as the logs and traces that your Dataset integration forwards. These permissions read content, not only metadata. Unlike the telemetry permissions in `CloudWatchOmniSpaceAccessPolicy`, they have no `cloudwatch:HasAccessGrant` condition, so access grants do not limit them.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/omni-iam-policies-to-use-cloudwatch-omni.md b/AmazonCloudWatch/latest/monitoring/omni-iam-policies-to-use-cloudwatch-omni.md index 49bb356..3f14cb7 100644 --- a//AmazonCloudWatch/latest/monitoring/omni-iam-policies-to-use-cloudwatch-omni.md +++ b//AmazonCloudWatch/latest/monitoring/omni-iam-policies-to-use-cloudwatch-omni.md @@ -7 +7 @@ -Permissions in CloudWatchOmniModelInferencePolicyPermissions in CloudWatchOmniSpaceAccessPolicyPermissions that read across your whole accountPermissions you provide yourself +Permissions in CloudWatchOmniModelInferencePolicyPermissions in CloudWatchOmniSpaceAccessPolicyPermissions that read across your whole accountPermissions in CloudWatchOmniAWSIntegrationPolicyV2Permissions you provide yourself @@ -11 +11 @@ Permissions in CloudWatchOmniModelInferencePolicyPermissions in CloudWatchOmniSp -The space operator role carries `CloudWatchOmniSpaceAccessPolicy` as its base policy, with `CloudWatchOmniModelInferencePolicy` and `CloudWatchOmniAWSIntegrationPolicy` as optional additions chosen during setup. Between them they cover using a space: querying telemetry, managing alerts and dashboards, and creating and running evaluations. None covers creating a space or a domain, so setup needs permissions you grant yourself. CloudWatch Omni provides further managed policies for other roles, including `CloudWatchOmniDomainAccessPolicy` for organization domain administration. For the complete set, see [AWS managed policies for CloudWatch Omni](./omni-aws-managed-policies-for-cloudwatch-omni.html). +The space operator role carries `CloudWatchOmniSpaceAccessPolicy` as its base policy, with `CloudWatchOmniModelInferencePolicy` and `CloudWatchOmniAWSIntegrationPolicy` as optional additions chosen during setup. Between them they cover using a space: querying telemetry, managing alerts and dashboards, and creating and running evaluations. None covers creating a space or a domain, so setup needs permissions you grant yourself. On the space operator role, replace `CloudWatchOmniAWSIntegrationPolicy` with `CloudWatchOmniAWSIntegrationPolicyV2`. See [The policies](./omni-aws-managed-policies-for-cloudwatch-omni.html#omni-aws-managed-policies-for-cloudwatch-omni-the-policies). CloudWatch Omni provides further managed policies for other roles, including `CloudWatchOmniDomainAccessPolicy` for organization domain administration. For the complete set, see [AWS managed policies for CloudWatch Omni](./omni-aws-managed-policies-for-cloudwatch-omni.html). @@ -22,0 +23,2 @@ This page enumerates what each policy grants and why, discloses the permissions + * Permissions in CloudWatchOmniAWSIntegrationPolicyV2 + @@ -87 +89 @@ Permission group | What it covers | How it is limited -The space experience, in the `cloudwatch` namespace | Space and access-grant management, telemetry query sessions, temporary credentials for reading space data, the context graph, alerts, dashboards, access profiles, views, user preferences, threads, integrations, intelligence configuration, and tagging. | Every action requires the condition `cloudwatch:HasAccessGrant` to be `true`, so a principal with no grant in the space cannot use any of them. +The space experience, in the `cloudwatch` namespace | Space and access-grant management, telemetry query sessions, temporary credentials for reading space data, the context graph, alerts, dashboards, access profiles, views, user preferences, threads, agent assets, integrations, intelligence configuration, writing GitHub change events to your account's `default` CloudWatch Dataset, and tagging. | Every action requires the condition `cloudwatch:HasAccessGrant` to be `true`, so a principal with no grant in the space cannot use any of them. @@ -91,0 +94,2 @@ Passing a role for online evaluations | `iam:PassRole` for the evaluation execut +Creating the partner integration role | `iam:CreateRole`, `iam:PutRolePolicy`, and `iam:GetRoleTemplateVersion`, so CloudWatch Omni can create the IAM role in your account that a partner investigation agent uses to read your CloudWatch data within your access grants, when a space admin connects a third-party agent. | Restricted to roles named `service-role/CloudWatchExternalAgentIntegration-*` in your own account (`aws:ResourceAccount` equals `${aws:PrincipalAccount}`), only when the call arrives through CloudWatch (`aws:CalledVia` is `cloudwatch.amazonaws.com`), and only for roles created from the CloudWatch-owned role template `CloudWatchExternalAgentIntegrationRoleTemplate` (`iam:RoleTemplateARN`). `iam:GetRoleTemplateVersion` is limited to that template. +Creating the AWS DevOps Agent investigation role | `iam:CreateRole`, `iam:AttachRolePolicy`, and `iam:GetRoleTemplateVersion`, so CloudWatch Omni can create the investigation role in your account and attach its policy when you connect the AWS DevOps Agent integration. | Restricted to roles named `service-role/CloudWatchOmniDevOpsAgentInvestigationRole-*` in your own account, only when the call arrives through CloudWatch (`aws:CalledVia` is `cloudwatch.amazonaws.com`), and only for roles created from the CloudWatch-owned template `CloudWatchOmniDevOpsAgentInvestigationAccessRoleTemplate` (`iam:RoleTemplateARN`). `iam:AttachRolePolicy` is further limited by `iam:PolicyARN` to the single AWS managed policy `CloudWatchOmniDevOpsAgentInvestigationServiceRolePolicy`. @@ -125,0 +130,17 @@ For the complete policy document, see [CloudWatchOmniSpaceAccessPolicy](https:// +## Permissions in CloudWatchOmniAWSIntegrationPolicyV2 + +`CloudWatchOmniAWSIntegrationPolicyV2` holds every permission in [CloudWatchOmniAWSIntegrationPolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/CloudWatchOmniAWSIntegrationPolicy.html), plus read access to the logs, traces, and profiles in your account's `default` CloudWatch Dataset. The read covers everything stored in the `default` Dataset, in every Region of your account, such as the logs and traces that your Dataset integration forwards. These permissions read content, not only metadata. Unlike the telemetry permissions in `CloudWatchOmniSpaceAccessPolicy`, they have no `cloudwatch:HasAccessGrant` condition, so access grants do not limit them. + +`CloudWatchOmniAWSIntegrationPolicyV2` grants the following permissions in addition to those in `CloudWatchOmniAWSIntegrationPolicy`: + + * `cloudwatch:StartTelemetryQuerySession`, `cloudwatch:StartTelemetryQuery`, `cloudwatch:GetTelemetryQueryResults`, `cloudwatch:StopTelemetryQuery`, `cloudwatch:StopTelemetryQuerySession`, and `cloudwatch:ListTelemetryQuerySessions` run telemetry queries, only in your own account. + + * `cloudwatch:GetRecords` and `cloudwatch:GetProfileRecords` read the logs, traces, and profiles in your own account's `default` Dataset. + + * `kms:Decrypt` works only through CloudWatch, only on keys in your account, and only for the encryption context of the `default` Dataset. CloudWatch Omni needs it only when the `default` Dataset is encrypted with a customer managed key. In that case, the key policy must also allow `kms:Decrypt` for the IAM role that has this policy attached, either by naming the role or by allowing IAM policies in your account to use the key. See [Sample key policy](./omni-data-encryption-in-cloudwatch-omni.html#omni-data-encryption-in-cloudwatch-omni-sample-key-policy). + + + + +For the complete policy document, see [CloudWatchOmniAWSIntegrationPolicyV2](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/CloudWatchOmniAWSIntegrationPolicyV2.html) in the _AWS Managed Policy Reference_. +