Skip to main content

EC2 Time Sync & Chrony Configuration Diagnostics

Data strictly extracted from official AWS troubleshooting documentation. Click the symptom below to get the targeted CLI remediation commands.

🚨 Step 1: What specific error symptom are you experiencing?

Please click the most accurate description:


Quick Reference Table

#ScenarioKey Error SignalPrimary Fix
1Smeared vs Unsmeared Time Server Conflictserver 169.254.169.123 mixed with non-smeared sourcessystemctl restart systemd-timesyncd.service
2Mixed IPv4/IPv6 NTP Endpoint Conflictserver fd00:ec2::123 used alongside IPv4 entryUse only one entry in chrony.conf — IPv4 or IPv6, not both
3Chrony Time Sources Unreachable^? source state flag in chronyc sources -vN/A