Ensure that your Amazon Simple Queue Service (SQS) queues are protecting the contents of their messages with Server-Side Encryption (SSE). Amazon SQS service uses a KMS Customer Master Key (CMK) to generate data keys required for the encryption/decryption process of the SQS messages. There is no additional charge for using SQS Server-Side Encryption, however, there is a charge for using Amazon KMS.
This rule can help you with the following compliance standards:
- PCI
- HIPAA
- GDPR
- APRA
- MAS
- NIST4
For further details on compliance standards supported by Conformity, see here.
This rule can help you work with the AWS Well-Architected Framework.
This rule resolution is part of the Conformity Security & Compliance tool for AWS.
When you are using Amazon SQS queues to send and receive messages that contain sensitive data, it is highly recommended to implement data encryption in order to make the contents of these messages unavailable to unauthorized or anonymous users. The encryption and decryption is handled transparently by SQS Server-Side Encryption (SSE) and does not require any additional action from you or your application.
Audit
To determine if Server-Side Encryption (SSE) is enabled for your Amazon SQS queues, perform the following actions:
Remediation / Resolution
To enable Server-Side Encryption (SSE) for your existing Amazon SQS queues, perform the following actions:
References
- AWS Documentation
- Amazon SQS FAQs
- Encryption at rest
- Configuring server-side encryption (SSE) for a queue (console)
- AWS Command Line Interface (CLI) Documentation
- sqs
- list-queues
- get-queue-attributes
- set-queue-attributes
- CloudFormation Documentation
- Amazon Simple Queue Service resource type reference
- Terraform Documentation
- AWS Provider