Drift was detected during the scheduled drift detection run.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! Node 20 has reached end-of-life on 2026-04-30 and is not supported. !!
!! Please upgrade to a supported node version as soon as possible. !!
!! !!
!! This software is currently running on node v20.20.2. !!
!! As of the current release of this software, supported node releases are: !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Bundling asset CdkAppStack-stage/DemoApiService/Function/Code/Stage...
...2428cb7f5eb45e32e56dd2e4531511fb933ea2303772ee011b3c8c5f/index.js 5.6kb
...cb7f5eb45e32e56dd2e4531511fb933ea2303772ee011b3c8c5f/index.js.map 16.1kb
⚡ Done in 3ms
[Warning at /CdkAppStack-stage/DemoApiService] If you are relying on AWS SDK v2 to be present in the Lambda environment already, please explicitly configure a NodeJS runtime of Node 16 or lower. [ack: @aws-cdk/aws-lambda-nodejs:sdkV2NotInRuntime]
[Warning at /CdkAppStack-stage/DemoApiService/RestAPI/DeploymentStage.prod/Resource] AwsSolutions-APIG3: The REST API stage is not associated with AWS WAFv2 web ACL.
Stack CdkAppStack-stage (platform-product-stage)
NOTICES (What's this? https://github.com/aws/aws-cdk/wiki/CLI-Notices)
34892 CDK CLI will collect telemetry data on command usage starting at version 2.1100.0 (unless opted out)
Overview: We do not collect customer content and we anonymize the
telemetry we do collect. See the attached issue for more
information on what data is collected, why, and how to
opt-out. Telemetry will NOT be collected for any CDK CLI
version prior to version 2.1100.0 - regardless of
opt-in/out. You can also preview the telemetry we will start
collecting by logging it to a local file, by adding
`--unstable=telemetry --telemetry-file=my/local/file` to any
`cdk` command.
Affected versions: cli: >=2.0.0 <2.1100.0
More information at: https://github.com/aws/aws-cdk/issues/34892
30717 (lambda-nodejs): breaking change in esbuild causes import module error
Overview: ESBuild released a breaking change on version 0.22.0 that
changed the default bundling behavior. `lambda-nodejs`'s
`NodeJsFunction` now to fails to synthesize with the error
message `Runtime.ImportModuleError: Cannot find module
'module'`. This issue exists on all CDK versions up to and
including `2.147.2`. The workaround is either pin the
esbuild version to ~0.21 or add `--packages=bundle` to
`bundling.esbuildArgs` property (this option only works for
esbuild version >= `0.22.0`).
Affected versions: aws-cdk-lib.aws_lambda_nodejs.: >=2.0.0 <= 2.147.2
More information at: https://github.com/aws/aws-cdk/issues/30717
32775 (cli): CLI versions and CDK library versions have diverged
Overview: Starting in CDK 2.179.0, CLI versions will no longer be in
lockstep with CDK library versions. CLI versions will now be
released as 2.1000.0 and continue with 2.1001.0, etc.
Affected versions: cli: >=2.0.0 <=2.1005.0
More information at: https://github.com/aws/aws-cdk/issues/32775
If you don’t want to see a notice anymore, use "cdk acknowledge <id>". For example, "cdk acknowledge 34892".
Unable to resolve AWS account to use. It must be either configured when you define your CDK Stack, or through the environment
Drift Detected in stage
Drift was detected during the scheduled drift detection run.
Action Required: Review the changes and determine if they are expected or if remediation is needed.