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.
Open the workbench ยท All examples
{
"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.
What it allows
Allow 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.
Action or pattern Actions Access levels kms:Create*4 Write 3, Permissions management 1 kms:Describe*2 Read 2 kms:Enable*2 Write 2 kms:List*7 List 7 kms:Put*1 Permissions management 1 kms:Update*4 Write 4 kms:Revoke*1 Permissions management 1 kms:Disable*2 Write 2 kms:Get*5 Read 5 kms:Delete*3 Write 3 kms:TagResource1 Tagging 1 kms:UntagResource1 Tagging 1 kms:ScheduleKeyDeletion1 Write 1 kms:CancelKeyDeletion1 Write 1 kms:Decrypt1 Write 1
Checks
- High Allows 20 write or permissions-management actions (3 permissions management) on every resource ("Resource": "*"). AWS documentation for this check
The administrator can decrypt data, so administration and data access are not separated. The wildcards cover 4, 1 and 4 actions.
Least privilege rewrite
{
"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.
What it allows
Allow 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.
Action or pattern Actions Access levels kms:Create*4 Write 3, Permissions management 1 kms:Describe*2 Read 2 kms:Enable*2 Write 2 kms:List*7 List 7 kms:Put*1 Permissions management 1 kms:Update*4 Write 4 kms:Revoke*1 Permissions management 1 kms:Disable*2 Write 2 kms:Get*5 Read 5 kms:Delete*3 Write 3 kms:TagResource1 Tagging 1 kms:UntagResource1 Tagging 1 kms:ScheduleKeyDeletion1 Write 1 kms:CancelKeyDeletion1 Write 1
Checks
- High Allows 19 write or permissions-management actions (3 permissions management) on every resource ("Resource": "*"). AWS documentation for this check
Related pages
Sources
- AWS KMS Developer Guide: default key policy, read 16 Nov 2026
- AWS KMS Developer Guide: key policies, read 16 Nov 2026
- AWS Service Authorization Reference, programmatic access (fetched 16 Nov 2026), read 16 Nov 2026
Last reviewed 16 Nov 2026.