Request is missing Authentication Token after upgrading Serverless Framework to 3.25.0

TL;DR

For "Request is missing Authentication Token": upgrade to v3.25.1, which contains the fix. 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.

Request is missing Authentication Token

Steps

1. 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.
2. 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.

When to use

You are seeing this: The error came from the AWS SDK layer, not from the framework config. Use this skill when you run into "Request is missing Authentication Token after upgrading Serverless Framework to 3.25.0".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 3.25.0, v3.25.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

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