CDK does not add existing Cloudfront as trigger to Lambd@Edge?

[jatinmehrotra]

Describe the bug

I am using CDK v1,
Whenever i am trying to update my Lambda@edge function, the Lambda@edge stack is created with function, lambda role but it does not add EXISTING Cloudfront distribution.

Expected Behavior

Ideally when i update my lambda code, the new lambda@edge stack should automatically have trigger as existing cloudfront distribution.

Current Behavior

After i update lambda code, CDK creates new lambda@edge stack which has iam role, but does not have cloudfront as trigger.

Reproduction Steps

Lambda@edge code

const uriRedirector = new cloudfront.experimental.EdgeFunction(
      this,
      'UriRedirector',
      {
        code: lambda.Code.fromAsset('dist/events/object-cache/uri-redirector'),
        runtime: lambda.Runtime.NODEJS_14_X,
        handler: 'index.handle',
      }
    )

Cloudfront code

this.distribution = new cloudfront.Distribution(this, 'Distribution', {
      defaultBehavior: {
        origin: s3Origin,
        edgeLambdas: [
          {
            functionVersion: uriRedirector.currentVersion,
            eventType: cloudfront.LambdaEdgeEventType.ORIGIN_REQUEST,
          },
        ],
        originRequestPolicy: defaultBehaviourOriginRequestPolicy,
        viewerProtocolPolicy: cloudfront.ViewerProtocolPolicy.HTTPS_ONLY,
        allowedMethods: cloudfront.AllowedMethods.ALLOW_ALL,
      },
      
      ....

Possible Solution

Is it due to cdk v1?

Additional Information/Context

No response

CDK CLI Version

1.153

Framework Version

No response

Node.js Version

14.17.6

OS

macOS

Language

Typescript

Language Version

4.4.3

Other information

No response

[jatinmehrotra]

Update :-
Update :- I tried replicating code into another environment and looks like it works as it should,
However in above mentioned environment where issue is happening, it always create new lambda@edge stack on updating lambda code instead it should create. a new version on the exsiting lambda@edge stack with cloudfront as trigger.

i do have code which was used while change cloudfront API's , could this be a problem

const cfnDistribution = this.distribution.node
      .defaultChild as cloudfront.CfnDistribution
    cfnDistribution.overrideLogicalId(props.oldDistributionLogicalId)

[khushail]

@jatinmehrotra , the CDK V1 is deprecated and we no longer provide updates on this.

AWS CDK v1 will enter Maintenance Mode after June 1, 2022. After this date, v1 releases will contain new and updated resource level “L1” constructs, critical bug fixes, and security updates only. We will not publish new features or minor bug fixes to v1. See the [AWS SDKs and Tools maintenance policy](https://docs.aws.amazon.com/sdkref/latest/guide/maint-policy.html) for more detail on what this means.

Maintenance mode has a duration of 12 months. On June 1, 2023, CDK v1 will reach end-of-support. After this date, the AWS CDK v1 will no longer receive updates or releases. Previously published releases will continue to be available via public package managers and the code will remain on GitHub. Use of a CDK version which has reached end-of-support is done at your own discretion. We recommend you upgrade to the new major version.

Migration guide - https://docs.aws.amazon.com/cdk/v2/guide/migrating-v2.html

I am closing this issue as its related to V1. Please feel free to reopen if you face the similar issue in CDK V2.

[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.