# IAM policy example: read one CloudWatch Logs group, with a least privilege rewrite

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Allows a principal to find log streams and read events in one log group, /app/orders, and run queries over it. The original allows the Get and Describe wildcards on every log group. The rewrite names the group and five actions.

```json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "ReadLogs",
      "Effect": "Allow",
      "Action": [
        "logs:Get*",
        "logs:Describe*",
        "logs:FilterLogEvents",
        "logs:StartQuery"
      ],
      "Resource": "*"
    }
  ]
}
```

## What it allows

- Allows reading, searching and querying every log group in the account.

- Allows 39 actions (logs:Get*, logs:Describe*, logs:FilterLogEvents, logs:StartQuery) on every resource.

Checks:
- No flags.

Log data often holds tokens and personal data. The wildcards cover 18 and 19 actions across all groups.

## Least privilege rewrite

```json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "ReadOneGroup",
      "Effect": "Allow",
      "Action": [
        "logs:DescribeLogStreams",
        "logs:GetLogEvents",
        "logs:FilterLogEvents",
        "logs:StartQuery"
      ],
      "Resource": [
        "arn:aws:logs:us-east-1:111122223333:log-group:/app/orders",
        "arn:aws:logs:us-east-1:111122223333:log-group:/app/orders:*"
      ]
    },
    {
      "Sid": "QueryResults",
      "Effect": "Allow",
      "Action": [
        "logs:GetQueryResults",
        "logs:StopQuery"
      ],
      "Resource": "*"
    }
  ]
}
```

The rewrite names one log group and four actions. GetQueryResults and StopQuery keep a wildcard resource because they do not take a log group.

- Allows 4 actions (logs:DescribeLogStreams, logs:GetLogEvents, logs:FilterLogEvents, logs:StartQuery) on arn:aws:logs:us-east-1:111122223333:log-group:/app/orders, arn:aws:logs:us-east-1:111122223333:log-group:/app/orders:*.
- Allows 2 actions (logs:GetQueryResults, logs:StopQuery) on every resource.

Checks:
- No flags.

- [Paste it into the workbench](/)
- [Every CloudWatch Logs action and its access level](/actions/logs/)

## Related pages

- [IAM policy example: write to one log group](/examples/logs-application-write-logs/)
- [IAM policy example: read CloudTrail events](/examples/cloudtrail-read-recent-events/)
- [IAM policy example: send messages to one SQS queue](/examples/sqs-send-to-one-queue/)
- [All of them](/examples/)

## Sources

- Amazon CloudWatch Logs User Guide: managing access: https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/iam-access-control-overview-cwl.html (read 16 Nov 2026)
- AWS Service Authorization Reference, programmatic access (fetched 16 Nov 2026): https://docs.aws.amazon.com/service-authorization/latest/reference/service-reference.html (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://iampolicygenerator.com/examples/logs-read-one-log-group/

This site is not affiliated with Amazon Web Services. AWS service and product names are used only to describe AWS services.
