This is a repeat of the incident that occurred on August 10, 2018. However, this time, the problem was caught faster.
There are 4 locations where the time issue could have originated:
Based on deeper investigation following today’s incident, we observed the following:
Based on the above, the time jump occurred at the EC2 instance (hardware or VM level) or OS.
Further investigation will occur along with more discussions with AWS support.