<story><title>Keeping Time with Amazon Time Sync Service</title><url>https://aws.amazon.com/blogs/aws/keeping-time-with-amazon-time-sync-service/</url></story><parent_chain></parent_chain><comment><author>NelsonMinar</author><text>Details worth highlighting.. They recommend chrony over ntpd, which makes particular sense given that chrony is designed to work well on virtual machine. They are doing leap second smearing like Google does internally. They don&amp;#x27;t say anything about what sort of accuracy you can expect but if the clock source is truly local it could be very good.&lt;p&gt;It&amp;#x27;s kinda neat they&amp;#x27;re using a link local address.</text></comment>
<story><title>Keeping Time with Amazon Time Sync Service</title><url>https://aws.amazon.com/blogs/aws/keeping-time-with-amazon-time-sync-service/</url></story><parent_chain></parent_chain><comment><author>CaliforniaKarl</author><text>Argh!  I wish the NTP servers were usable from outside of AWS.&lt;p&gt;Outside of North America and Europe, there aren&amp;#x27;t as many public NTP servers as there should be.  For example, according to &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;www.pool.ntp.org&amp;#x2F;zone&amp;#x2F;south-america&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.pool.ntp.org&amp;#x2F;zone&amp;#x2F;south-america&lt;/a&gt;, South America has less than 50 NTP servers.&lt;p&gt;It would be awesome if the large, widely-distributed providers (not just AWS with CloudFront, but also Akami, Cloudflare, etc.) provided public, Stratum-1 NTP servers at their POPs.</text></comment>