A new deploy with same code would not work

Help
1

Hi, need help, my last deployment to in 2025/09 works fine, but when I try to deploy again today, I get the following error for any api request:

Unhandled Rejection: UnrecognizedClientException: The security token included in the request is invalid at throwDefaultError (/var/task/node\_modules/@smithy/smithy-client/dist-cjs/index.js:839:20) at /var/task/node\_modules/@smithy/smithy-client/dist-cjs/index.js:848:5 at de\_CommandError (/var/task/node\_modules/@aws-sdk/client-dynamodb/dist-cjs/index.js:2230:14) at process.processTicksAndRejections (node:internal/process/task\_queues:105:5) at async /var/task/node\_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20 at async /var/task/node\_modules/@smithy/core/dist-cjs/index.js:165:18 at async /var/task/node\_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38 at async /var/task/node\_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:34:22 at async main (/var/task/node\_modules/dynamoose/dist/aws/ddb/internal.js:6:20) at async createTable (/var/task/node\_modules/dynamoose/dist/Table/utilities.js:84:5)

anything you can think of? I have not changed anything in my code, just some edit in ignored files: https://github.com/electerm/electerm-cloud/commit/5994564b0e8c84691234a0f8431b330575b0fc70

see prev section

the settings, envs not change compare to old deploy of 2025/09

project url: https://vercel.com/zxdong262s-projects/electerm-cloud

5

The error you’re seeing is an AWS authentication issue: “The security token included in the request is invalid” which suggests your AWS credentials have expired or become invalid.

Even though you haven’t changed your environment variables, AWS credentials (especially temporary ones) can expire over time.

Can you check that?

6

Thank you so much for the quick reply, Pauline,

I checked the envs, not changed since 2024, the old deploy still use same credential, and I have one set of active credential only, if the old deploy works, it means the credential still works,

Also I checked in aws IAM, confirmed the credential works, actively used 6 hours ago(when revert back to old deploy, I tested)

Am I missing something?

Do you have the perimission to check request log, like request id: xrw7c-1769524569530-a30683337041, I do not have permission to check External APIs detail to aws.

7

I tried deploy again, it is working now, not sure what is happening, anyway, seems resolved

8

Hmm - interesting! Glad it’s resolved. If it comes up again, let us know.

1 Like