-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
custom-resource-apigw-cw-role lambda gets created through serverless framework and how can I change it's runtime #12307
Comments
It's hard-coded in lib/plugins/aws/custom-resources/index.js - I guess that should be updated to nodejs18.x or nodejs20.x |
Yes, making that change is working well, but the next version should address this problem. |
Hi Any updates on this one -- the AWS cutoff for node 16 is fast approaching. |
@bradwood this is going to be fixed in the v4 beta coming out within the next week. |
Got another bunch of emails from AWS about this yesterday. @Mmarzex ? Is this going upgrade going to happen? Or do I need we need to solve this another way? Maybe just do a 3.x.y patch release, just to fix the runtime? And decouple it from all the v4 stuff? Just a thought. |
I am also interested in this |
Same here. Also a bunch of AWS emails. |
Seeing how little time we have remaining (June 12), we have to look into alternatives already. Maybe managing the custom resources ourselves through other IaC is an option? |
@JaroVDH we are kinda at this point too - if we can't get rid of this lambda by the cut-off we're going to have to do some kinda hand-rolled alternative. I'm really not keen to go there, as unpicking what it does it likely to be PITA. But we are also up against it now. It's a pity that this issue has not had more focus from the Serverless team. :-/ |
@bradwood I think you can actually get rid of this lambda function. If you set |
This removes access logging for the API Gateway, which for many API's is a security requirement. |
any update on this? |
@Mmarzex can you please let us know where we are with this? |
FYI, June 12 won't end up killing any services with custom resources just yet.
I will still be pushing to remove these custom resources from our deploys before the June deadline, but it's good to know that at least we won't be stuck because of it. |
@JaroVDH thanks for this update. What about the idea of just releasing the runtime change as a 3.x.y release? Surely this is just a small change. Doing this takes all the pressure off waiting for v4 and keeps us all happy. |
Sorry for the confusion, I'm not affiliated with Serverless Framework; I'm just another impacted user :) |
My bad -- apologies. So I wonder if anyone who is part of the Serverless team is going to bother responding into this... It feels like we are just yelling into the abyss here... 😢 |
Are you certain it's a bug?
Is the issue caused by a plugin?
Are you using the latest v3 release?
Is there an existing issue for this?
Issue description
I got a notification from AWS like Fwd: [Action Required]. AWS Lambda ends support for Node.js 16.
When I hit the CLI command provided, I got to know that some custom-resource-apigw-cw-role lambda gets created, and it has the node 16.x runtime that gave me a warning.
How could I change the AWS-managed function runtime?
Service configuration (serverless.yml) content
N/A
Command name and used flags
sls deploy
Command output
Environment information
The text was updated successfully, but these errors were encountered: