This website uses cookies to ensure you get the best experience.
Learn more.
A high-volume S3 ingestion workload uses SSE-KMS and produces many objects. The team wants to reduce applicable KMS request costs without removing KMS-backed encryption. Which feature should it evaluate?
Published
- Disable encryption and leave the KMS key ARN in an object tag.
- S3 Bucket Keys for the supported SSE-KMS configuration, with a review of key-policy and encryption-context implications.
- Use only an S3 lifecycle storage-class transition and assume that it enables Bucket Keys for every existing object.
- Increase the KMS request quota and assume that a higher quota reduces the price of each request.
Comments — 0
Sign in to comment