How to fix a S3 RequestTimeTooSkewed bug

3 July 2017
3 Jul 2017
1 min read

While uploading a recent blog post to the cloud, I came across a strange S3 error:

ERROR: S3 error: 403 (RequestTimeTooSkewed): The difference between the request time and the current time is too large.

I’ve never encountered this error before. At first I thought my S3 instance had a weird time bug. After doing some debugging,1 I saw that the time on my machine was off by several days. After logging into system preferences and updating the time, everything was back to normal.

  1. Googling [return]

Want to know more?

I spend a ton of time thinking on how to work smarter, not harder. If you'd like to be the first to know what I'm thinking about, sign up to the list below.

Time Tracking

Apple Moves into AR