AWS Signature Version 4 Credential Scope Issue

Question

Hi, I am receiving the following error message from AWS Signature V4 
```
"Date in Credential scope does not match YYYYMMDD from ISO-8601 version of date from HTTP: '20221227' != '20211227', from '20211227T060649Z'."
```
My application had been working perfectly for the last 6 months and then all of a sudden stopped on 2021-12-26. The troubleshooting page [HERE](https://docs.aws.amazon.com/general/latest/gr/signature-v4-troubleshooting.html) does discuss this issue, but the dates in my error message appear to match and no other changes had been made. Has anyone else experienced, or is experiencing this?

AWS-User · Accepted Answer

Quoting from the post

> "Date in Credential scope does not match YYYYMMDD from ISO-8601 version of date from HTTP: '20221227' != '20211227', from '20211227T060649Z'."

and

> ..., but the dates in my error message appear to match and no other changes had been made.

It appears there is a date mismatch.

The year does not seem to be matching:  202**2**1227

Would recommending checking again to confirm if there is any application bug related to year handling and then reaching out to AWS support if the issue persists.

jsonc · Answer

Interesting.  AWS checks for this first checks for  x-amz-date header or query parameter, and then if that's not there for a date header.

Is the time stamp in UTC and in the following ISO 8601 format: YYYYMMDD'T'HHMMSS'Z' without milliseconds?

I haven't seen anything yet, but would be curious if something changed as well.

AWS Signature Version 4 Credential Scope Issue

Relevant content