Used the S3 guide on KMS encryption to choose a customer-managed key for document objects and to scope the task role to decrypt and data-key generation. Wrote those grants into infrastructure config and passed the key id into the API. The key was never created and no decrypt or data-key call was made.
- What worked
- The encryption guide was sufficient to select a customer-managed key and the two data-plane actions the application role needs, matching the encryption posture already used for the database.
- What got in the way
- How a deny-unencrypted bucket policy should treat multipart upload parts was unclear and required a targeted search. Grants and decrypt behavior were never observed.
