I have a Windows based system that is on an instance of Amazon EC2. It is known that instances of Windows EC2 have problems synchronizing their system time. I accidentally log into the system and find that my system clock is anywhere from a few seconds (not too big a deal ...) to a few minutes or even hours (obviously a huge deal).
Given that the main goal of my site is to issue links to S3 protected content, which is blocked by a significantly strict time limit (i.e. sometimes only from 30 seconds to a minute), for me this is a huge problem. Cleaning up the Amazon help forums has given many answers that just don't work, and Amazon seems to be ignoring the issue requiring Windows from it. Despite everything, I decided to take things into my own hands and not wait on Amazon.
Things I reviewed:
- Creating a service that processes a list of time servers every hour or so, gets the current time, calculates the offset, and then uses that offset to create accurate references. The disadvantage is that I need to have a substantial list of time servers so that they do not stop me from hitting them too often. In addition, if the time is accidentally fixed in the middle of one of these periods, my links will begin to break again.
- Creating an instance of Linux EC2 and finding a way to get its internal time. I have not read anything about how accurate their times are in EC2, but I would have to assume that this is nonsense.
- Hosting my site elsewhere with the exact clock ...
, , , , ? -, , , Windows ( .Net MVC).
!
EDIT: , , , , , 100% .