I would like to use AWS’s Server Side Encryption (SSE) with the AWS Key Management Service (KMS) to encrypt data at rest in S3. (See this AWS blog post detailing SSE-KMS.)
However, I also have the requirement that I use Cloudfront Presigned URLs.
How can I set up a Cloudfront distribution to use a key in AWS KMS to decrypt and use S3 objects encrypted at rest?
(This Boto3 issue seems to be from someone looking for the same answers as me, but with no results).
This was previously not possible because CloudFront didn’t support it and because (as I mentioned in comments on John’s answer — which was on the right track) there was no way to roll-your-own solution with Lambda@Edge because the
X-Amz-Cf-Id request header –generated on the back side of CloudFront and visible only to S3, not to the trigger invocation — would invalidate any signature you tried to add to the request inside a Lambda@Edge trigger, because signing of all
X-Amz-* headers is mandatory.
X-Amz-Cf-Id header value is now exposed to a Lambda@Edge trigger function in the event structure — not with the other request headers, but as a simple string attribute — at
With that value in hand, you can use the execution role credentials and the built-in SDK in the Lambda@Edge environment to generate a signature and and add the necessary headers (including an
Authorization header with the derived credential identifier and freshly-generated signature) to the request.
This setup does not use an Origin Access Identifier (OAI) because the Lambda@Edge trigger’s IAM Execution Role is used instead of an OAI to persuade S3 that the request is authorized.
Achraf Souk has published an official AWS blog post explaining the solution from start to finish.