Recommended read-only permissions
Copyable IAM policies and an IAM Identity Center permission set for day-to-day, read-only use.
CloudConsole does exactly what your credentials allow, no more. For checking alarms, logs, costs and resources, give it a read-only role. Keep write access for a separate role you switch to when you need it, or make the account read-only in the app.
Option 1: AWS managed ReadOnlyAccess (simplest)
Attach the AWS managed policy ReadOnlyAccess (arn:aws:iam::aws:policy/ReadOnlyAccess). It covers every screen in the app, including the ~110 services read through Cloud Control. Be aware that it also allows reading data, such as objects in S3 buckets and items in DynamoDB tables.
Option 2: the CloudConsole read-only policy (tightest)
This lists the read calls the app's own screens make, and nothing else. The second statement is for reading data (S3 object previews and DynamoDB items); leave it out if you don't want that. Objects encrypted with a customer managed KMS key also need kms:Decrypt on that key (see Preview S3 objects).
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "CloudConsoleRead",
"Effect": "Allow",
"Action": [
"ec2:DescribeRegions",
"ec2:DescribeInstances",
"ec2:DescribeInstanceAttribute",
"ec2:DescribeVolumes",
"ec2:DescribeSnapshots",
"ec2:DescribeAddresses",
"ec2:DescribeImages",
"ec2:DescribeNatGateways",
"elasticloadbalancing:DescribeLoadBalancers",
"elasticloadbalancing:DescribeTargetGroups",
"elasticloadbalancing:DescribeTargetHealth",
"autoscaling:DescribeAutoScalingGroups",
"autoscaling:DescribeInstanceRefreshes",
"autoscaling:DescribeScalingActivities",
"lambda:ListFunctions",
"lambda:GetFunction",
"lambda:GetFunctionConfiguration",
"lambda:ListVersionsByFunction",
"lambda:ListAliases",
"s3:ListAllMyBuckets",
"s3:GetBucketLocation",
"s3:ListBucket",
"s3:GetBucketVersioning",
"s3:GetBucketPublicAccessBlock",
"s3:GetEncryptionConfiguration",
"s3:GetBucketRequestPayment",
"rds:DescribeDBInstances",
"rds:DescribeOrderableDBInstanceOptions",
"ecs:ListClusters",
"ecs:DescribeClusters",
"ecs:ListServices",
"ecs:DescribeServices",
"ecs:ListTasks",
"ecs:DescribeTasks",
"ecs:ListTaskDefinitions",
"ecs:DescribeTaskDefinition",
"cloudwatch:DescribeAlarms",
"cloudwatch:DescribeAlarmHistory",
"cloudwatch:GetMetricData",
"logs:DescribeLogGroups",
"logs:DescribeLogStreams",
"logs:FilterLogEvents",
"logs:GetLogEvents",
"logs:GetLogRecord",
"logs:DescribeQueryDefinitions",
"logs:StartQuery",
"logs:GetQueryResults",
"logs:StopQuery",
"ce:GetCostAndUsage",
"ce:GetCostForecast",
"codepipeline:ListPipelines",
"codepipeline:GetPipeline",
"codepipeline:GetPipelineState",
"codepipeline:ListPipelineExecutions",
"cloudformation:ListStacks",
"cloudformation:DescribeStacks",
"cloudformation:DescribeStackEvents",
"cloudformation:ListStackResources",
"cloudtrail:LookupEvents",
"sqs:ListQueues",
"sqs:GetQueueAttributes",
"sqs:ListDeadLetterSourceQueues",
"sqs:ListMessageMoveTasks",
"states:ListStateMachines",
"states:DescribeStateMachine",
"states:ListExecutions",
"states:DescribeExecution",
"states:GetExecutionHistory",
"events:ListEventBuses",
"events:ListRules",
"events:DescribeRule",
"events:ListTargetsByRule",
"dynamodb:ListTables",
"dynamodb:DescribeTable",
"dynamodb:DescribeContinuousBackups",
"dynamodb:DescribeTimeToLive",
"iam:GetAccountSummary",
"iam:ListUsers",
"iam:GetUser",
"iam:ListUserTags",
"iam:GetLoginProfile",
"iam:ListAccessKeys",
"iam:GetAccessKeyLastUsed",
"iam:ListMFADevices",
"iam:ListGroupsForUser",
"iam:ListAttachedUserPolicies",
"iam:ListUserPolicies",
"iam:ListRoles",
"iam:GetRole",
"iam:ListAttachedRolePolicies",
"iam:ListRolePolicies",
"iam:ListPolicies",
"iam:GetPolicy",
"iam:GetPolicyVersion",
"secretsmanager:ListSecrets",
"secretsmanager:DescribeSecret",
"route53:ListHostedZones",
"route53:GetHostedZone",
"route53:ListResourceRecordSets",
"route53:ListHealthChecks",
"route53:GetHealthCheckStatus",
"cloudfront:ListDistributions",
"cloudfront:GetDistribution",
"cloudfront:ListInvalidations",
"cloudfront:GetInvalidation",
"apigateway:GET",
"health:DescribeEvents",
"health:DescribeEventDetails",
"health:DescribeAffectedEntities",
"acm:ListCertificates",
"acm:DescribeCertificate",
"ssm:DescribeParameters",
"ssm:DescribeInstanceInformation",
"ssm:ListCommands",
"ssm:ListCommandInvocations",
"ssm:GetCommandInvocation",
"codebuild:ListProjects",
"codebuild:BatchGetProjects",
"codebuild:ListBuildsForProject",
"codebuild:ListBuilds",
"codebuild:BatchGetBuilds",
"cloudformation:ListResources",
"cloudformation:GetResource",
"cloudformation:DescribeType",
"tag:GetResources",
"sns:ListTopics",
"ec2:DescribeVpcs",
"ec2:DescribeSubnets",
"ec2:DescribeNetworkInterfaces",
"ec2:DescribeVpcPeeringConnections",
"ec2:DescribeTransitGatewayVpcAttachments",
"scheduler:ListSchedules",
"scheduler:GetSchedule",
"servicequotas:ListServiceQuotas",
"servicequotas:GetServiceQuota",
"s3:GetBucketPolicyStatus",
"s3:GetLifecycleConfiguration",
"s3:GetBucketLogging",
"s3:GetAccountPublicAccessBlock",
"pricing:GetProducts",
"cloudformation:GetTemplate",
"cloudformation:DescribeStackResources",
"ec2:DescribeLaunchTemplates",
"ec2:DescribeLaunchTemplateVersions",
"autoscaling:DescribePolicies",
"autoscaling:DescribeScheduledActions",
"budgets:ViewBudget",
"logs:ListTagsLogGroup",
"logs:ListTagsForResource"
],
"Resource": "*"
},
{
"Sid": "CloudConsoleReadData",
"Effect": "Allow",
"Action": [
"s3:GetObject",
"dynamodb:Scan",
"dynamodb:Query",
"ssm:GetParameter",
"ssm:GetParametersByPath",
"ssm:GetParameterHistory"
],
"Resource": "*"
}
]
}
This policy doesn't cover the read-only services browsed through Cloud Control (Elastic Beanstalk, KMS, SNS and so on): each of those also needs that service's own List* and Describe* or Get* permissions. See Supported services.
Option 3: ViewOnlyAccess plus extras
The AWS managed job-function policy ViewOnlyAccess lists resources but deliberately doesn't let you read log events, query logs or read costs. Attach it together with this statement:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "CloudConsoleExtras",
"Effect": "Allow",
"Action": [
"logs:FilterLogEvents",
"logs:GetLogEvents",
"logs:GetLogRecord",
"logs:DescribeQueryDefinitions",
"logs:StartQuery",
"logs:GetQueryResults",
"logs:StopQuery",
"cloudwatch:GetMetricData",
"cloudwatch:DescribeAlarmHistory",
"ce:GetCostAndUsage",
"ce:GetCostForecast",
"cloudtrail:LookupEvents",
"cloudformation:ListResources",
"cloudformation:GetResource",
"cloudformation:DescribeType",
"tag:GetResources",
"sns:ListTopics",
"health:DescribeEvents",
"health:DescribeEventDetails",
"health:DescribeAffectedEntities",
"scheduler:ListSchedules",
"scheduler:GetSchedule",
"servicequotas:ListServiceQuotas",
"servicequotas:GetServiceQuota",
"s3:GetBucketPublicAccessBlock",
"s3:GetBucketPolicyStatus",
"s3:GetBucketVersioning",
"s3:GetEncryptionConfiguration",
"s3:GetLifecycleConfiguration",
"s3:GetBucketLogging",
"s3:GetAccountPublicAccessBlock",
"iam:GetAccessKeyLastUsed",
"pricing:GetProducts",
"ssm:DescribeParameters",
"ssm:GetParameter",
"ssm:GetParametersByPath",
"ssm:GetParameterHistory",
"ssm:DescribeInstanceInformation",
"ssm:ListCommands",
"ssm:ListCommandInvocations",
"ssm:GetCommandInvocation",
"codebuild:BatchGetProjects",
"codebuild:BatchGetBuilds"
],
"Resource": "*"
}
]
}
As an IAM Identity Center permission set
In the IAM Identity Center console, create a permission set. Either choose the predefined ReadOnlyAccess, or create a custom permission set and paste Option 2 as its inline policy. Then assign it to your users or groups for each account. With the CLI:
# 1. Create the permission set (use your Identity Center instance ARN)
aws sso-admin create-permission-set \
--instance-arn arn:aws:sso:::instance/ssoins-1234567890abcdef \
--name CloudConsoleReadOnly \
--session-duration PT8H
# 2a. Either attach the AWS managed ReadOnlyAccess policy...
aws sso-admin attach-managed-policy-to-permission-set \
--instance-arn arn:aws:sso:::instance/ssoins-1234567890abcdef \
--permission-set-arn arn:aws:sso:::permissionSet/ssoins-1234567890abcdef/ps-1234567890abcdef \
--managed-policy-arn arn:aws:iam::aws:policy/ReadOnlyAccess
# 2b. ...or use the CloudConsole read-only policy above as an inline policy
aws sso-admin put-inline-policy-to-permission-set \
--instance-arn arn:aws:sso:::instance/ssoins-1234567890abcdef \
--permission-set-arn arn:aws:sso:::permissionSet/ssoins-1234567890abcdef/ps-1234567890abcdef \
--inline-policy file://cloudconsole-readonly.json
# 3. Give a group access to an account with it
aws sso-admin create-account-assignment \
--instance-arn arn:aws:sso:::instance/ssoins-1234567890abcdef \
--target-id 123456789012 --target-type AWS_ACCOUNT \
--permission-set-arn arn:aws:sso:::permissionSet/ssoins-1234567890abcdef/ps-1234567890abcdef \
--principal-type GROUP --principal-id 1234567890-abcd1234-5678-90ab-cdef-1234567890ab
For an IAM user with access keys
aws iam create-policy --policy-name CloudConsoleReadOnly \
--policy-document file://cloudconsole-readonly.json
aws iam attach-user-policy --user-name cloudconsole \
--policy-arn arn:aws:iam::123456789012:policy/CloudConsoleReadOnly
Things that cost money even when read-only
- Cost Explorer: AWS charges $0.01 for each request. See Costs for how often the app calls it. Leave out
ce:*if you'd rather not pay for it. - Logs Insights: billed by AWS per GB of logs scanned. Leave out
logs:StartQueryto prevent it.
To make changes from the app as well, see Permissions for changes.
Questions
Does CloudConsole need admin access?
No. A read-only role is enough for everything except changes, and even changes need only the specific actions listed in the permissions for changes article.
Why does it need cloudformation:ListResources?
About 110 services are read through AWS Cloud Control, whose list and get calls are authorised as cloudformation:ListResources and cloudformation:GetResource, plus the service's own read permissions.
Can I see which permissions are missing?
Yes. Account → Safety → Access check makes one read call per service and shows which are allowed or denied.
Email [email protected] with what you tried and any message the app showed. Don’t send access keys or secrets. We reply within two working days.