How do I fix "Failed to start ntpd.service: Unit ntpd.service not found."?

Use chrony instead: `sudo dnf install -y chrony && sudo systemctl enable --now chronyd`. Migrate any custom `/etc/ntp.conf` settings to `/etc/chrony.conf`. Update cloud-init / Ansible / Packer steps that referenced ntpd. Verify with `chronyc sources`. Source: https://docs.aws.amazon.com/linux/al2023/ug/compare-with-al2.html

Amazon Linux 2023

Failed to start ntpd.service: Unit ntpd.service not found.

Failed to start ntpd.service: Unit ntpd.service not found.

What it means

Amazon Linux 2023 uses chrony for time sync; the ntpd service no longer exists.

Why it happens

Amazon Linux 2 used ntpd; AL2023 standardizes on chrony (chronyd). user-data or config management that enables/starts ntpd fails on AL2023.

How to fix it

Use chrony instead: `sudo dnf install -y chrony && sudo systemctl enable --now chronyd`.
Migrate any custom `/etc/ntp.conf` settings to `/etc/chrony.conf`.
Update cloud-init / Ansible / Packer steps that referenced ntpd.
Verify with `chronyc sources`.

Related deadline: Amazon Linux 2 EOL — 2026-06-30.

Check configured patterns in your project

The free EOLkits scanner processes files in your browser and flags selected related patterns in supported IaC and dependency files. File names and contents are not uploaded; bounded aggregate file and finding counts may be sent. It is not a complete source or AWS-account scan.

Prefer a 10-second check? Paste your config into the free AWS EOL checker. Pasted input is not uploaded; bounded first-party usage events may be sent.

Primary source: https://docs.aws.amazon.com/linux/al2023/ug/compare-with-al2.html

Inspect the $299 report sample and availability →