Aws PHP SDK S3 RequestTimeTooSkewed Error

Question

Up until last night, I was able to upload files to S3 using the AWS PHP SDK without any problem. Since this morning (clock's changed because of the Daylight Saving) I've been getting RequestTimeTooSkewed error.

I compared AWS' and my server's time and they are identical (apart from AWS being on GMT and my server is on UTC)

wget https://email.us-east-1.amazonaws.com/date --no-check-certificate --server-response
--2015-03-29 11:23:06--  https://email.us-east-1.amazonaws.com/date
Resolving email.us-east-1.amazonaws.com (email.us-east-1.amazonaws.com)... 207.171.162.129
Connecting to email.us-east-1.amazonaws.com (email.us-east-1.amazonaws.com)|207.171.162.129|:443... connected.
HTTP request sent, awaiting response...
  HTTP/1.1 404 Not Found
  x-amzn-RequestId: 981a9ae9-d5fd-11e4-8f83-65a61f41c957
  Content-Length: 29
  Date: Sun, 29 Mar 2015 10:23:08 GMT
2015-03-29 11:23:07 ERROR 404: Not Found.

And on my server

date -u
Sun Mar 29 11:23:08 UTC 2015

Am I missing something here? Is my server being UTC a problem?

Michael - sqlbot Michael - sqlbot · Accepted Answer · 2015-03-29T14:17:40

Your time and AWS time are not identical.

For all practical purposes, UTC and GMT are exactly the same time zone.

Google current time utc and current time gmt. Not only should you find that they are the same... you should also find that, for reasons not clear, your system clock is one hour ahead...which is wrong by any standard, since neither UTC nor GMT observes DST.

Your server time in GMT/UTC should not change when switching from/to summer time... so the question is, why did it change? I notice you used date -u... if you've actually set your server time to some other time zone, you could be experiencing some kind of error from the double conversion (which is one reason the server clock should not be set to local time).

Aws PHP SDK S3 RequestTimeTooSkewed Error

2 Answers