I'm currently facing issues with 'DescribeEc2Snapshots' operations failing, likely due to clock skew problems. To address this, I've added chrony to the installation script that runs at boot for our EC2 instances. Here's what I included in the script:
```bash
sudo apt-get install -y chrony
echo "server 169.254.169.123 prefer iburst minpoll 4 maxpoll 4" | $sudo_cmd tee /etc/chrony.conf
sudo systemctl stop ntpd 2>/dev/null || true
sudo systemctl disable ntpd 2>/dev/null || true
sudo systemctl enable chronyd
sudo systemctl start chronyd
```
Despite these efforts, I'm still encountering clock skew errors. Has anyone experienced this and can offer insights on further troubleshooting options?
2 Answers
Hmm, clock skew issues might indicate a problem with TLS rather than your operating system setup. Can you provide more context? What specific components are failing? Knowing the exact commands and APIs you’re using, along with where they're being run from, can help pinpoint the issue.
It sounds like you're seeing some clock sync issues, but first, can you share more details about the actual errors you're getting? Setting up monitoring for your clock sync state could help identify the variance. Just remember, virtual machines often behave differently than physical hardware, so NTP isn't always perfect. Usually, AWS API calls shouldn't fail due to clock drift unless things are really out of whack.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures