aws-cloudfront: Support cloudfront-js-2.0 runtime

[jmortlock]

Describe the feature

Cloudfront functions support either "cloudfront-js-1.0" or "cloudfront-js-2.0" runtimes

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/functions-javascript-runtime-features.html

Use Case

AWS provide example functions here: https://github.com/aws-samples/amazon-cloudfront-functions

Not all of them are cloudfront-js-1.0 v1 compatible; specifically I was using the URL rewrites and redirect example.

Proposed Solution

Add a new enum property to allow the user to choose which runtime is used.

Other Information

Available in cloudformation: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-function-functionconfig.html

Currently Hardcoded in CDK: https://github.com/aws/aws-cdk/blob/85cc0c686049ca40a0bc09589830a909e911fbdf/packages/aws-cdk-lib/aws-cloudfront/lib/function.ts#L168C19-L168C36

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.111.0

Environment details (OS name and version, etc.)

Linux

[go-to-k]

The PR has already been submitted👍

#28099

[pahud]

Awesome! Can't wait to see the 2.0 runtime support in CDK.

[prerakhere]

Great. Can't wait!

[mridehalgh]

Before we have L2 support, you should be able to enable this feature like this:

const cfFunction = new aws_cloudfront.Function(this, 'Function', {
      ...
    });

(cfFunction.node.defaultChild as aws_cloudfront.CfnFunction).addPropertyOverride("FunctionConfig.Runtime", "cloudfront-js-2.0")

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.