AWS Self Hosted runner fails with Node error

[tbulding]

Describe the bug

When authenticating with a Self Hosted runner that runs on AWS, the action fails with the following error...

Run aws-actions/configure-aws-credentials@v4
/opt/actions-runner/externals/node20/bin/node: /lib64/libm.so.6: version GLIBC_2.27' not found (required by /opt/actions-runner/externals/node20/bin/node) /opt/actions-runner/externals/node20/bin/node: /lib64/libc.so.6: version GLIBC_2.28' not found (required by /opt/actions-runner/externals/node20/bin/node)

Expected Behavior

Run aws-actions/configure-aws-credentials@v3
Proceeding with IAM user credentials

Current Behavior

Run aws-actions/configure-aws-credentials@v4
/opt/actions-runner/externals/node20/bin/node: /lib64/libm.so.6: version GLIBC_2.27' not found (required by /opt/actions-runner/externals/node20/bin/node) /opt/actions-runner/externals/node20/bin/node: /lib64/libc.so.6: version GLIBC_2.28' not found (required by /opt/actions-runner/externals/node20/bin/node)

Reproduction Steps

  - name: Step 2 - Configure AWS Credentials
    if: ${{ always() }} #  This ensures that your workflow runs successfully
    uses: aws-actions/configure-aws-credentials@v4
    with:
      aws-region: ${{ env.AWS_REGION }}

Possible Solution

I was able to execute the authentication simply by going down to version 3
- name: Step 2 - Configure AWS Credentials
if: ${{ always() }} # This ensures that your workflow runs successfully
uses: aws-actions/configure-aws-credentials@v3
with:
aws-region: ${{ env.AWS_REGION }}

Additional Information/Context

No response

[yasminetalby]

Hello @tbulding ,

Thank you very much for your submission.

As you can see in the changelog, the difference between configure-aws-credentials v3 and v4 is that we have upgraded runtime to node20 from node16.

What OS and glibc version are you using?

Node16 and Node20 don't have the same requirements which is why you might experience this error by upgrading from v3 to v4.

I have linked the Building.md file for node16 and node20 respectively above so you can check if you are meeting all requirement.

Let me know if this helps you resolve your issue or if you have any further questions or inquiries!

Best regards,

Yasmine

[kellertk]

I suspect you're running this on EL7 (CentOS, RHEL, etc.). Although the GitHub runner documentation says that CentOS 7 is supported, I'm not sure this is true for recent versions of the GitHub runner.

Does this still happen if you use version 2.285 of the runner? This was the first release to support Node 16.

[tbulding]

Hello, thank you for the prompt replies. The build is using ec2 instances on al2, This is a new deployment using the latest runner code.

[dmirica-gpsw]

I encountered this even when using latest docker image from amazon for aws cli (amazon/aws-cli:2.15.11); I would have thought that this way would be compatible.
(indeed v3 works)

[jbelkins]

I get these same error messages if I try to set up AWS credentials when running:

• v4 of this action,
• on a Github runner (2.311.0),
• with a Amazon Linux 2-based Docker image (swift:5.9-amazonlinux2)

      - uses: aws-actions/configure-aws-credentials@v4
        with:
          role-to-assume: <...>
          aws-region: us-west-2

The same credential setup action is successful if I replace the Docker image with one based on Ubuntu (Focal or Jammy, both work.)

Seems like there is definitely some issue between v4 of this action and AL2.

[526f73656e0a]

Same issue is happening for us. However we are using the default GitHub runners with the aws-cli:2.15.44 container. The workaround: configure-aws-credentials@v3 does not fix it for us though.

[egrieveillum]

I am also experiencing this issue with v3. Downgrading to v2 and v1 does not work either.

[cagartner-id]

Same issue

[ivivanov]

/__e/node20/bin/node: /lib64/libm.so.6: version GLIBC_2.27' not found (required by /__e/node20/bin/node)`
We are using the github hosted runners.
Tried all kind of combinations between the ubuntu-20.04, ubuntu-22.04, ubuntu-24.04 and the aws-actions/configure-aws-credentials@v1,2,3,4
Nothing seems to work for me. Will update later if I find a workaround...

[timbrunette]

Was able to get a workaround following this comment: dawidd6/action-download-artifact#262 (comment)

Details here:
https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

[ivivanov]

The workaround which @timbrunette mentioned worked for me as well.
On the jobs which are using configure-aws-credentials action I set

runs-on: ubuntu-20.04
uses: aws-actions/configure-aws-credentials@v1-node16

and

env:
  ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true