---
title: "Comment by OneLifeVibe on \"AWS KMS: How Encryption Keys Protect Your Data in AWS\" | Hashnode"
description: "The distinction between the key policy and IAM policies is the part that deserves more attention. Many teams assume an IAM allow is enough, then spend time trou"
url: "https://hashnode.com/posts/aws-kms-how-encryption-keys-protect-your-data-in-aws/6b0073d94e09f1311f7792f5/comment/6b007466de4755877c9ce7b2"
---

[Discussion](https://hashnode.com/posts/aws-kms-how-encryption-keys-protect-your-data-in-aws/6b0073d94e09f1311f7792f5)

Comment [AWS KMS: How Encryption Keys Protect Your Data in AWS](https://hashnode.com/posts/aws-kms-how-encryption-keys-protect-your-data-in-aws/6b0073d94e09f1311f7792f5)

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[1d ago](https://hashnode.com/posts/aws-kms-how-encryption-keys-protect-your-data-in-aws/6b0073d94e09f1311f7792f5/comment/6b007466de4755877c9ce7b2)

The distinction between the key policy and IAM policies is the part that deserves more attention. Many teams assume an IAM allow is enough, then spend time troubleshooting a denied decrypt that was actually blocked at the key policy. The envelope encryption note is also useful, because the 4 KB direct encrypt limit is easy to miss until a larger file fails. One addition that would help readers is a short note on testing key rotation and deletion in a non-production account first, since a scheduled deletion can still affect data that depends on the key.
