You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
@peterwoodworth Thanks for the reply.
If you please follow the link I've provided, you can see that it's for the latest release (2.90.0) and it hasn't fixed yet.
Thanks
Describe the bug
Since https://github.com/aws/aws-cdk/releases/tag/v2.87.0 CDK lambda runtime should be using node 18 runtime.
We are seeing some runtimes still using node 16 e.g. EC2 VPC restrictDefaultSecurityGroup lambda. (there might be more)
https://github.com/aws/aws-cdk/blob/v2-release/packages/aws-cdk-lib/aws-ec2/lib/vpc.ts#L1703
Expected Behavior
Node 18 runtime should be used in all CDK generated lambdas
Current Behavior
Node 16 is being used in some CDK generated lambdas
Reproduction Steps
This is autogenerated by CDK
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.89
Framework Version
No response
Node.js Version
16
OS
Windows
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: