MIGRATION ISSUE: InvalidSignatureException after upgrade NodeJS 20 to 22 in AWS lambda

[ThangBui2703]

Pre-Migration Checklist

• I've read the Migration Guide.
• I've reviewed the upgrading notes and major version differences mentioned in UPGRADING.md.
• I've checked AWS Forums and StackOverflow for similar migration issues.

Which JavaScript Runtime is this issue in?

Node.js (includes AWS Lambda)

AWS Lambda Usage

• Yes, my application is running on AWS Lambda.
• No, my application is not running on AWS Lambda.

Describe the Migration Issue

I upgrade my NodeJS runtime in lambda from 20 to 22 and got error {
"errorType": "Runtime.UnhandledPromiseRejection",
"errorMessage": "InvalidSignatureException: Signature expired: 20251103T110018Z is now earlier than 20251103T110817Z (20251103T112317Z - 15 min.)",
"trace": [
"Runtime.UnhandledPromiseRejection: InvalidSignatureException: Signature expired: 20251103T110018Z is now earlier than 20251103T110817Z (20251103T112317Z - 15 min.)",
" at process. (file:///var/runtime/index.mjs:1448:17)",
" at process.emit (node:events:518:28)",
" at emitUnhandledRejection (node:internal/process/promises:252:13)",
" at throwUnhandledRejectionsMode (node:internal/process/promises:388:19)",
" at processPromiseRejections (node:internal/process/promises:475:17)",
" at process.processTicksAndRejections (node:internal/process/task_queues:106:32)"
]
}

Code Comparison

No response

Observed Differences/Errors

{
"errorType": "Runtime.UnhandledPromiseRejection",
"errorMessage": "InvalidSignatureException: Signature expired: 20251103T110018Z is now earlier than 20251103T110817Z (20251103T112317Z - 15 min.)",
"trace": [
"Runtime.UnhandledPromiseRejection: InvalidSignatureException: Signature expired: 20251103T110018Z is now earlier than 20251103T110817Z (20251103T112317Z - 15 min.)",
" at process. (file:///var/runtime/index.mjs:1448:17)",
" at process.emit (node:events:518:28)",
" at emitUnhandledRejection (node:internal/process/promises:252:13)",
" at throwUnhandledRejectionsMode (node:internal/process/promises:388:19)",
" at processPromiseRejections (node:internal/process/promises:475:17)",
" at process.processTicksAndRejections (node:internal/process/task_queues:106:32)"
]
}

Additional Context

I am calling a lambda from another lambda via axios, then got 502 error. I go to check cloud watch and got error InvalidSignatureException: Signature expired: 20251103T110018Z is now earlier than 20251103T110817Z (20251103T112317Z - 15 min.). But if i recall after get the error it will work as expected and do not error

[aBurmeseDev]

Hi @ThangBui2703 - thanks for stopping by.

We've have similar issues open before and please refer to these comments with suggestions to troubleshoot this behavior:

• InvalidSignatureException: Signature expired: 20240820T230143Z is now earlier than 20240820T230302Z (20240820T230802Z - 5 min.) #6400 (comment)
• "InvalidSignatureException: The request signature we calculated does not match the signature you provided" when calling a command with credentials from the SDK, but the same command and credentials work when called from the CLI #5811 (comment)

If issue persists and need further assistance, please share your code snippet without any sensitive info.

[github-actions]

This issue has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing.