Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

Dealing with the leap second at AWS

AWS Adjusted Time – We will spread the extra second over the 24 hours surrounding the leap second (11:59:59 on December 31, 2016 to 12:00:00 on January 1, 2017). AWS Adjusted Time and Coordinated Universal time will be in sync at the end of this time period.

It sounds like AWS is using a similar approach for dealing with the leap second as Google does, by making the time slightly slower for a window of time. What seems to differ is the lenght and when this window of time is scheduled. For Google, the interval is 20 hours with the leap second right in the middle of it. For AWS, the interval is 24 hours, but finishes at the same time with the lead second.

I confess that I’m curious about any pros and cons of each of these approaches.

Don't be the product, buy the product!