Skip to content
IAM Policy Generator

IAM policy example: read one Secrets Manager secret, with a least privilege rewrite

Allows a role to read the value of one secret and see its details. The secret ARN ends with a random six-character suffix, so the policy uses a wildcard on the suffix. The AWS documentation shows this pattern. The original allows secretsmanager:* on all secrets.

Open the workbench ยท All examples

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "Secrets",
      "Effect": "Allow",
      "Action": "secretsmanager:*",
      "Resource": "*"
    }
  ]
}

What it allows

  • Allows every Secrets Manager action on every secret.

What it allows

  1. Allow 27 actions (secretsmanager:*) on every resource.

    Action or patternActionsAccess levels
    secretsmanager:*27List 1, Read 7, Write 14, Permissions management 3, Tagging 2

Checks

The action secretsmanager:* covers 27 actions, including reading, replacing and deleting all secrets.

Least privilege rewrite

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "ReadOneSecret",
      "Effect": "Allow",
      "Action": [
        "secretsmanager:GetSecretValue",
        "secretsmanager:DescribeSecret"
      ],
      "Resource": "arn:aws:secretsmanager:us-east-1:111122223333:secret:prod/orders/db-??????"
    }
  ]
}

The rewrite names one secret and two read actions. The six question marks match the random suffix. Writing and deleting secrets are removed.

What it allows

  1. Allow 2 actions (secretsmanager:GetSecretValue, secretsmanager:DescribeSecret) on arn:aws:secretsmanager:us-east-1:111122223333:secret:prod/orders/db-??????.

    Action or patternActionsAccess levels
    secretsmanager:GetSecretValue1Read 1
    secretsmanager:DescribeSecret1Read 1

Checks

No flags from the six checks.

Sources

  1. AWS Secrets Manager User Guide: permissions policy examples, read 16 Nov 2026
  2. AWS Service Authorization Reference, programmatic access (fetched 16 Nov 2026), read 16 Nov 2026

Last reviewed 16 Nov 2026.