Skip to content
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

Cannot update Nodejs runtime version of UserPoolClientLambda function #13726

Closed
2 tasks done
eagren20 opened this issue Apr 18, 2024 · 5 comments
Closed
2 tasks done

Cannot update Nodejs runtime version of UserPoolClientLambda function #13726

eagren20 opened this issue Apr 18, 2024 · 5 comments
Labels
auth Issues tied to the auth category of the CLI pending-triage Issue is pending triage

Comments

@eagren20
Copy link

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

v16.13.2

Amplify CLI Version

12.11.1

What operating system are you using?

Windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

Manually changed runtime versions of custom lambda functions to 18

Describe the bug

I cannot complete an amplify push because the Nodejs runtime version of the function UserPoolClientLambda is 14, which is no longer supported. As this is an auto generated function there doesn't appear to be a way to manually update the runtime version in the cloudformation files. I am using the latest version of the CLI.

Resource creation Initiated
Resource handler returned message: "The runtime parameter of nodejs14.x is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs20.x) while creating or updating functions.
The following resource(s) failed to create: [UserPoolClientLambda].

Expected behavior

Successful amplify push

Reproduction steps

This project was created several years ago when nodejs runtime 14 was still used so there is no reliable way to recreate it

Project Identifier

353214476f258ac72d41a4057d9c5ae7

Log output

# Put your logs below this line
CREATE_IN_PROGRESS                           [***]ntLambda                                                         AWS::Lambda::Function        Thu Apr 18 2024 16:30:12 GMT-0400 (Eastern Daylight Time) Resource creation Initiated                                                                                                                                                                                                                                                                                                                                                                                        
CREATE_FAILED                                [***]ntLambda                                                         AWS::Lambda::Function        Thu Apr 18 2024 16:30:12 GMT-0400 (Eastern Daylight Time) Resource handler returned message: "The runtime parameter of nodejs14.x is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs20.x) while creating or updating functions. (Service: Lambda, Status Code: 400, Request ID: cb62ec8b-d194-42cc-83f2-ed4458b4e266)" (RequestToken: e4e2a69b-0b9a-cb78-a81c-cf504d660abd, HandlerErrorCode: InvalidRequest)
UPDATE_ROLLBACK_IN_PROGRESS                  [***]ify-[***]ectyield-[***]ev-[***]245-[***]yieldff68962f-[***]LZTDZ AWS::CloudFormation::Stack   Thu Apr 18 2024 16:30:12 GMT-0400 (Eastern Daylight Time) The following resource(s) failed to create: [UserPoolClientLambda].                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          

Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@eagren20 eagren20 added the pending-triage Issue is pending triage label Apr 18, 2024
@ykethan
Copy link
Member

ykethan commented Apr 19, 2024

Hey @eagren20, Could you run amplify update auth to update the UserPoolClientLambda runtime, then run amplify build and the check the CloudFormation template to ensure the runtime has been updates. If you do not observe the updated runtime, on the update auth flow reselect your existing options which should regenerate the template.

@ykethan ykethan added auth Issues tied to the auth category of the CLI pending-response Issue is pending response from the issue author labels Apr 19, 2024
@eagren20
Copy link
Author

amplify update auth resolved it, thank you!

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Apr 19, 2024
@ykethan
Copy link
Member

ykethan commented Apr 19, 2024

Glad to hear that @eagren20. Closing the issue, feel free in reaching out to us if you have any issues.

@ykethan ykethan closed this as completed Apr 19, 2024
Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

@malcomm
Copy link

malcomm commented Oct 9, 2024

In my particular case I had to upgrade the amplify CLI to: 12.13.0. Also had to adjust the amplify build settings to nodejs version 18 (I previously had 16).

@ykethan - is there a list of supported nodejs versions supported by Amplify Console for building?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auth Issues tied to the auth category of the CLI pending-triage Issue is pending triage
Projects
None yet
Development

No branches or pull requests

3 participants