Amazon Linux 2023

Error: Unable to find a match: <package>

Error: Unable to find a match: <package>

What it means

A package that existed on Amazon Linux 2 isn't in the Amazon Linux 2023 repositories under that name.

Why it happens

AL2023's repositories differ from AL2's. A package may have been renamed, made version-namespaced (python3.11, nginx1.24, postgresql15), moved to SPAL (Supplementary Packages for Amazon Linux), left to EPEL, or dropped. Scripts that `dnf install <old-name>` (or `yum install`, which now routes to dnf) fail with 'Unable to find a match'.

How to fix it

  1. Find the real name: `dnf search <keyword>` and `dnf provides '*/<binary>'`.
  2. Use the version-namespaced package where AL2023 splits versions, e.g. `dnf install -y python3.11` / `nginx1.24` / `postgresql15`.
  3. If it lived behind amazon-linux-extras on AL2, it's now a default dnf package, version-namespaced, or in SPAL — enable SPAL instead of the old extras topic.
  4. Do not add a repository built for another distribution. Check SPAL, which is built for AL2023 but has separate support limitations; if the package is absent, vendor or build it deliberately.
  5. Check support status/dates with the `dnf-plugin-support-info` plugin before standardizing on a package.

Related deadline: Amazon Linux 2 EOL2026-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/package-management.html

Inspect the $299 report sample and availability →