Amplify version 13.0.0 GLIBC not found

[bob-lee]

Amplify CLI Version

13.0.0

Question

Our project (App ID: d3e09syp3jtf2a) has been using AWS Amplify console for CI/CD for years.

Yesterday we experienced a series of failures to deploy and found "Backend Build" phase failed with below error:

# Patching NPM package '@aws-amplify/cli' from 10.5.2 to 13.0.0...
/root/.amplify/bin/amplify: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /root/.amplify/bin/amplify)

Today I clicked Redeploy button on failed Deployment and it just worked ok with previous version:

# Patching NPM package '@aws-amplify/cli' from 10.5.2 to 12.14.4...

I believe we have no control on which version of CLI to use, some kind explanation will be appreciated.

[ykethan]

Hey @bob-lee, thank you for reaching out and apologizes on the issue caused by this. The version 13.0.0 was immediately rolled back to 12.14.4 as latest.

As part of the latest new release we are expecting to use Node.js v22 as the default version which would require newer GLIBC. From the error message provided it appears your build settings currently use Amazon Linux 2 which does not provide newer GLIBC as part of the build image. I would suggest updating your build setting to use the latest default image Amazon Linux 2023 which does provide newer GLIBC.

If you would like to set a specific version of Amplify CLI like 12.14.4, you can use the _LIVE_UPDATES environment variable in Amplify console. Refer to the Amplify console environment variables documentation providing this information: https://docs.aws.amazon.com/amplify/latest/userguide/environment-variables.html
Alternatively, you can also install a specific version of Amplify CLI as part of your build specification amplify.yml file in the backend phase. For example:

backend:
 phases:
  build:
   commands:
    - npm i -g @aws-amplify/cli@12.14.4

Refer to the Amplify console build specification documentation: https://docs.aws.amazon.com/amplify/latest/userguide/edit-build-settings.html

Do let us know if you have any other questions or concerns. We're here to help ensure a smooth experience as you continue developing with AWS Amplify.

[bob-lee]

Thanks for clarification and extra info @ykethan , we have practical reason to stick to old versions such as node@18, vue@2.7, etc. plus this cli@12.14.4. Following your advice:

• changed Build image to Amazone Linux 2023
• took amplify.yml approach and deploy went smooth using specified version.

[INFO]: ## Starting Backend Build
# Starting phase: build
# Executing command: npm i -g @aws-amplify/cli@12.14.4

[github-actions]

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.

[warrenmcquinn]

Just experienced this issue today - setting Live package updates value to 12.14.4 instead of latest resolved the issue for me on Amazon Linux 2.

[ykethan]

Update:
If your Amplify application uses a backend from a different Amplify application or configured to automatically generate the Amplify config files at build time.
https://docs.aws.amazon.com/amplify/latest/userguide/amplify-config-autogeneration.html

The GLIBC message may not appear with the build logs as following causing the aws-exports.js or amplifyconfiguration.json to not generate as during build the amplify commands are run internally.

similar to the pevious comment, I would suggest updating your build setting to use the latest default image Amazon Linux 2023 which does provide newer GLIBC.
If you would like to set a specific version of Amplify CLI like 12.14.4, you can use the _LIVE_UPDATES environment variable.