# IAM policy example: administer KMS keys without using them, with a least privilege rewrite

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

Allows a key administrator to create, describe, tag and schedule deletion of keys, and to manage aliases, without the cryptographic actions that read data. The AWS key policy guidance splits administrators from users. The original adds kms:Decrypt, which gives access to protected data.

```json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "Admin",
      "Effect": "Allow",
      "Action": [
        "kms:Create*",
        "kms:Describe*",
        "kms:Enable*",
        "kms:List*",
        "kms:Put*",
        "kms:Update*",
        "kms:Revoke*",
        "kms:Disable*",
        "kms:Get*",
        "kms:Delete*",
        "kms:TagResource",
        "kms:UntagResource",
        "kms:ScheduleKeyDeletion",
        "kms:CancelKeyDeletion",
        "kms:Decrypt"
      ],
      "Resource": "*"
    }
  ]
}
```

## What it allows

- Allows key management actions on all keys and also decrypting data with any key.

- Allows 36 actions (kms:Create*, kms:Describe*, kms:Enable*, kms:List*, kms:Put*, kms:Update*, kms:Revoke*, kms:Disable*, kms:Get*, kms:Delete*, kms:TagResource, kms:UntagResource, kms:ScheduleKeyDeletion, kms:CancelKeyDeletion, kms:Decrypt) on every resource.

Checks:
- high: Allows 20 write or permissions-management actions (3 permissions management) on every resource ("Resource": "*"). (https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)

The administrator can decrypt data, so administration and data access are not separated. The wildcards cover 4, 1 and 4 actions.

## Least privilege rewrite

```json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "Admin",
      "Effect": "Allow",
      "Action": [
        "kms:Create*",
        "kms:Describe*",
        "kms:Enable*",
        "kms:List*",
        "kms:Put*",
        "kms:Update*",
        "kms:Revoke*",
        "kms:Disable*",
        "kms:Get*",
        "kms:Delete*",
        "kms:TagResource",
        "kms:UntagResource",
        "kms:ScheduleKeyDeletion",
        "kms:CancelKeyDeletion"
      ],
      "Resource": "*"
    }
  ]
}
```

The rewrite removes kms:Decrypt. The administrator manages keys but cannot decrypt data unless a separate statement grants it.

- Allows 35 actions (kms:Create*, kms:Describe*, kms:Enable*, kms:List*, kms:Put*, kms:Update*, kms:Revoke*, kms:Disable*, kms:Get*, kms:Delete*, kms:TagResource, kms:UntagResource, kms:ScheduleKeyDeletion, kms:CancelKeyDeletion) on every resource.

Checks:
- high: Allows 19 write or permissions-management actions (3 permissions management) on every resource ("Resource": "*"). (https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)

- [Paste it into the workbench](/)
- [Every KMS action and its access level](/actions/kms/)

## Related pages

- [IAM policy example: read one Secrets Manager secret](/examples/secretsmanager-read-one-secret/)
- [IAM policy example: read Secrets Manager secrets by tag](/examples/secretsmanager-read-secrets-by-tag/)
- [IAM policy example: read a Parameter Store path](/examples/ssm-read-parameter-path/)
- [All of them](/examples/)

## Sources

- AWS KMS Developer Guide: default key policy: https://docs.aws.amazon.com/kms/latest/developerguide/key-policy-default.html (read 16 Nov 2026)
- AWS KMS Developer Guide: key policies: https://docs.aws.amazon.com/kms/latest/developerguide/key-policy-overview.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/kms-key-administrator-without-use/

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