cloudfront: Support for Field-Level Encryption in CloudFront BehaviorOptions #30203
Labels
@aws-cdk/aws-cloudfront
Related to Amazon CloudFront
closed-for-staleness
This issue was automatically closed because it hadn't received any attention in a while.
effort/small
Small work item – less than a day of effort
feature-request
A feature should be added or improved.
p2
response-requested
Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Describe the feature
I am requesting support for enabling field-level encryption in CloudFront
BehaviorOptions
within the AWS CDK. Recently, a high vulnerability issue has been raised: "CloudFront distributions that utilize HTTP POST Methods should have field-level encryption enabled."However, currently, the AWS CDK does not support configuring field-level encryption directly in
BehaviorOptions
. This limitation requires the use of lower-level constructs (CfnDistribution
), which complicates the setup and deviates from the convenience provided by the high-levelDistribution
construct.Use Case
We need to secure sensitive data in HTTP POST requests by enabling field-level encryption in CloudFront distributions. Field-level encryption helps to protect specific data fields as they transit through CloudFront, ensuring compliance with security policies and protecting sensitive information.
Proposed Solution
Extend the
BehaviorOptions
in theaws-cloudfront
module to include a property for field-level encryption, such as:Other Information
Current Workaround
Currently, we have to define field-level encryption profiles and configurations using
CfnResource
and attach them to behaviors using the low-levelCfnDistribution
construct, which makes the code more complex and harder to maintain.Example
Here’s an example of the current workaround:
Request
Please consider adding support for field-level encryption in the BehaviorOptions for CloudFront distributions in AWS CDK. This enhancement will greatly simplify securing sensitive data in our applications.
Acknowledgements
CDK version used
2.141.0
Environment details (OS name and version, etc.)
OS: Ubuntu 22.04.4
Node.js: 18.18.2
The text was updated successfully, but these errors were encountered: