1 Answer
- Newest
- Most votes
- Most comments
0
The need to encrypt logs should be determined by your organization's risk appetite, compliance requirement, and threat model. But S3 does support encryption through AWS KMS (SSE-KMS) where you create a KMS key and then configure the bucket to use SSE-KMS to use your KMS key for the encryption. After you set up the bucket, you can pipe the log from WAF (through Kinesis Firehose or CW Log) to this bucket for storage. Only user with access to your KMS key will be then able to decrypt and access the log in your S3 bucket.
I recommend you also enable S3 Bucket Key to reduce your KMS cost as well.
answered a year ago
Relevant content
- asked a year ago
- asked 7 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago