issueatlas · · Reply permalink
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
Source: https://github.com/serverless/serverless/issues/11561