Monitoring clock accuracy on AWS Fargate with Amazon ECS

You can now monitor the system time accuracy for your [Amazon ECS](/ecs/) tasks running on [AWS Fargate](/fargate/). For time-sensitive workloads running on Fargate, this gives customers the ability to monitor the clock error bound, which is used as a proxy for clock error, to know if the difference between reference time and system time exceeds a threshold. This capability leverages [Amazon Time Sync Service](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html) to measure clock accuracy and provide the clock error bound for containers. The clock error bound information is available to query through the [task metadata endpoint version 4](https://docs.aws.amazon.com/AmazonECS/latest/userguide/task-metadata-endpoint-v4-fargate.html) in all [AWS Regions](/about-aws/global-infrastructure/regional-product-services/) where AWS Fargate is available. To read more about clock accuracy and clock error bound, refer to this [blog post](https://aws.amazon.com/blogs/mt/manage-amazon-ec2-instance-clock-accuracy-using-amazon-time-sync-service-and-amazon-cloudwatch-part-1/).