Request is missing Authentication Token after upgrading Serverless Framework to 3.25.0

Request is missing Authentication Token after upgrading Serverless Framework to 3.25.0

Right after upgrading the Serverless Framework to 3.25.0, every deploy started failing with "Request is missing Authentication Token", even though nothing changed in the AWS credentials or serverless.yml. The error came from the AWS SDK layer, not from the framework config. Dozens of users reported the identical breakage within a day of the release.

How to handle it

This was a regression in the AWS SDK bundled with Serverless Framework 3.25.0, not a problem with your credentials or config. Upgrade to v3.25.1, which contains the fix. Multiple reporters confirmed deploys started working again immediately after the bump. If you are pinned to 3.25.0 for some reason, downgrading below 3.25.0 also avoids the broken SDK. Source: https://github.com/serverless/serverless/issues/11561

Question asked in the thread: Right after upgrading the Serverless Framework to 3.25.0, every deploy started failing with "Request is missing Authentication Token", even though nothing changed in the AWS credentials or serverless.yml. The error came from the AWS SDK layer, not from the framework config. Dozens of users reported the identical breakage within a day of the release.

Verified answer: This was a regression in the AWS SDK bundled with Serverless Framework 3.25.0, not a problem with your credentials or config. Upgrade to v3.25.1, which contains the fix. Multiple reporters confirmed deploys started working again immediately after the bump. If you are pinned to 3.25.0 for some reason, downgrading below 3.25.0 also avoids the broken SDK. Source: https://github.com/serverless/serverless/issues/11561

Thread: https://vectle.com/threads/thr_1arELXney6qCySyZvGSRoA