IAM policies to use CloudWatch Omni

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.

This page enumerates what each policy grants and why, discloses the permissions that read metadata across your whole account, and lists the permissions you must add separately. For how CloudWatch Omni works with IAM in general (resource types, condition keys, and the roles setup creates), see Identity and access management for CloudWatch Omni.

Topics

Permissions in CloudWatchOmniModelInferencePolicy

This policy grants model inference and nothing else. It is attached only to spaces that use the prompt playground or run evaluations that invoke a model. A space that only views telemetry does not receive it, and a space can create and view its evaluation configuration without it. Only running a model requires it.

Every action except bedrock-mantle:CallWithBearerToken is restricted to your own account by an aws:ResourceAccount condition, so a space can invoke only the models, inference profiles, and projects in the account it belongs to. CallWithBearerToken has no resource type in the IAM action model, so it cannot be scoped to a resource or narrowed by a condition. The same action appears with the same unscoped resource in the AWS managed policy BedrockAgentCoreFullAccess, which uses it for the same purpose.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AgentCoreEvaluationBedrockInvoke",
            "Effect": "Allow",
            "Action": [
                "bedrock:InvokeModel",
                "bedrock:InvokeModelWithResponseStream"
            ],
            "Resource": [
                "arn:aws:bedrock:*::foundation-model/*",
                "arn:aws:bedrock:*:*:inference-profile/*"
            ],
            "Condition": {
                "StringEquals": {
                    "aws:ResourceAccount": "${aws:PrincipalAccount}"
                }
            }
        },
        {
            "Sid": "AgentCoreEvaluationBedrockMantleInference",
            "Effect": "Allow",
            "Action": "bedrock-mantle:CreateInference",
            "Resource": "arn:aws:bedrock-mantle:*:*:project/*",
            "Condition": {
                "StringEquals": {
                    "aws:ResourceAccount": "${aws:PrincipalAccount}"
                }
            }
        },
        {
            "Sid": "AgentCoreEvaluationBedrockMantleCallWithBearerToken",
            "Effect": "Allow",
            "Action": "bedrock-mantle:CallWithBearerToken",
            "Resource": "*"
        }
    ]
}

Permissions in CloudWatchOmniSpaceAccessPolicy

This is the base policy, always attached. It grants the space experience and the management side of evaluation. The table groups its permissions by what they are for, and gives the condition that limits each group.

Permissions that read across your whole account

Four permission groups grant permissions that the underlying API cannot restrict to a subset of resources, so they enumerate metadata across your entire account:

None of them permits a change, and none reads the contents of anything. Apart from creating the AWS Config service-linked role, this policy grants no permission to create, modify, or delete an IAM role, user, or policy, and reading a secret value is a separate permission limited to secrets in your own account whose name begins with cw-omni- and that carry the cw-omni tag.

For the complete policy document, see CloudWatchOmniSpaceAccessPolicy in the AWS Managed Policy Reference.

Permissions you provide yourself

The managed policies cover using a space. They do not cover creating one, and they do not cover telemetry ingestion.