Cannot upgrade UserPoolClientLambda from Nodejs14.x via the Amplify CI pipeline, therefore cannot deploy any code about amplify-cli HOT 9 CLOSED

Hey @dragosiordachioaia, thank you for reaching out. Does the CI pipeline also use the latest/updated Amplify CLI version?
As the UserPoolClientLambda is a inline function present in the auth CloudFormation templates, when running amplify push Amplify builds and updates the NodeJs version on the Lambda function.

YAML CloudFormation

It appears this is an un-migrated auth resource, you can update the resource by running amplify update auth which should prompt you to migrate the the auth resource.

from amplify-cli.

I've run amplify update auth and it didn't prompt me to upgrade the resource. I did this a few months ago, so that's not too surprising.

Yes, the CLI in the pipeline is on the latest version (see screenshot below)

from amplify-cli.

Hey @dragosiordachioaia, thank you for confirming. Could you download and un-zip the #current-cloud-backend.zip from the AWS S3 deployment bucket. In the CloudFormation templates under auth/<name>/build and the awscloudformation/build do you observe a userpoolclient lambda with a NodeJs runtime as 14?

Could you try pulling the project into a new directory outside your existing project directory. In the CloudFormation templates under backend/auth/<name>/build and the backend/awscloudformation/build do you observe a userpoolclient lambda?

from amplify-cli.

@ykethan I've checked all of that, no Lambda uses Node 14, only 18 and 20.

from amplify-cli.

@dragosiordachioaia could you provide us the App ID and failed build?
additionally, if you switch the image to Amazon Linux:2 image does this throw a similar error message?

from amplify-cli.

app ID is d18apgfog4c8xo. One example of a failed build (before I disabled the back-end build altogether just to get the front-end to deploy) is 1740 (I hope this is the right identifier, it seems to be an auto-incrementing build number). As for switching to Amazon Linux: 2, I tried it just now (while using Node 16 for the build, since building the front-end with Node 18 seems to run out of memory no matter what I try, but that's a problem to solve later) and this is the error I get. I am however installing Node 16 just above this and it does say it's installed, so I don't understand why this would not work:

                                    npm ERR! command failed
                                    npm ERR! command sh -c -- node scripts/warn-maintenance-mode.js
                                    npm ERR! sh: node: command not found
                                    npm ERR! A complete log of this run can be found in:
                                    npm ERR!     /root/.npm/_logs/2024-03-11T20_41_20_388Z-debug-0.log
2024-03-11T20:41:57.270Z [ERROR]: !!! Build failed
2024-03-11T20:41:57.271Z [ERROR]: !!! Error: Command failed with exit code 127
2024-03-11T20:41:57.271Z [INFO]: # Starting environment caching...
2024-03-11T20:41:57.271Z [INFO]: # Uploading environment cache artifact...
2024-03-11T20:41:57.340Z [INFO]: # Uploaded environment cache artifact
2024-03-11T20:41:57.340Z [INFO]: # Environment caching completed
2024-03-11T20:41:57.341Z [INFO]: # A new default build image based on Amazon Linux 2023 is now generally available. The image includes newer versions of Node.js, Python, and Ruby that you can use to build your app. To use the new image, select "Amazon Linux:2023" in the "Build settings" section for your app in the Amplify console.
Terminating logging...```

from amplify-cli.

from amplify-cli.

@dragosiordachioaia thank you for the confirmation. Glad to hear you were able to mitigate the issue.

from amplify-cli.

⚠️COMMENT VISIBILITY WARNING⚠️

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.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

from amplify-cli.