Amazon Web Services (AWS) has released the first preview version of Amazon Linux 2027 (AL2027), the next generation of its Linux distribution built primarily for workloads running on AWS. The update builds on Amazon Linux 2023, but introduces deep changes: Linux kernel 7.1, SELinux in enforcing mode, DNF5, GCC 16.1, Python 3.14, systemd 260, and a new cryptographic stack based on AWS-LC. For now, AWS warns that this edition is intended for evaluation and testing, not production.
Amazon Linux 2027 in 20 seconds
- Amazon Linux 2027 has been available as a public preview since September 3, 2026.
- It debuts Linux kernel 7.1, and SELinux switches to enforcing by default.
- It updates major components such as GCC 16.1, glibc 2.44, Python 3.14, systemd 260, and DNF5.
- AWS plans to support AL2027 until 2032.
- For now, AWS advises against using this preview release in production.
Amazon Linux occupies a peculiar place among GNU/Linux distributions. It uses RPM packages and draws on components from Fedora, but AWS clarifies that AL2027 is not a derivative or remix of any specific Fedora release. The new distribution takes components from Fedora 44 and 45, plus software from other projects and its own in-house development. Its kernel, for instance, comes directly from the versions published on kernel.org and is selected independently of Fedora.
That also helps explain where it competes. Amazon Linux isn’t trying to replace Ubuntu, Debian, Rocky Linux, or AlmaLinux in every scenario. Its main appeal shows up when infrastructure is already concentrated on AWS and teams want an operating system built, maintained, and tested by that same provider.
What Actually Changes in Amazon Linux 2027
The jump from Amazon Linux 2023 is considerable. The preview release uses Linux kernel 7.1, compared with AL2023’s default 6.1, although that release also offers kernels 6.12 and 6.18. AWS plans to incorporate new mainline kernel branches roughly once a year over AL2027’s lifetime.
One of the changes most likely to affect existing applications is SELinux. Amazon Linux 2023 used it by default in permissive mode: it logged the operations the policy would have blocked, but didn’t actually prevent them from running.
AL2027 switches to SELinux enforcing by default. Mandatory access control policies are now actually enforced, so an application that relied on previously permitted behavior may need adjustments when migrating. AWS allows temporarily reverting to permissive mode, and even disabling SELinux entirely, though it recommends against doing so.
The overhaul also reaches practically the entire toolchain.
| Component | Amazon Linux 2023 | Amazon Linux 2027 Preview |
|---|---|---|
| Default kernel | 6.1 | 7.1 |
| SELinux | Permissive | Enforcing |
| GCC | 11.5 | 16.1 |
| glibc | 2.34 | 2.44 |
| binutils | 2.41 | 2.46 |
| LLVM/Clang | 15, 18, and 19 | 22 |
| systemd | 252 | 260 |
| RPM | 4.16 | 6.0 |
| Package manager | DNF 4.14 | DNF5 5.4 |
| Default Python | 3.9 | 3.14 |
| PCRE | PCRE1 + PCRE2 | PCRE2 only |
| zlib | 1.2.11 | zlib-ng 2.3 |
The jump from GCC 11 to GCC 16.1 deserves attention from anyone compiling their own software. AWS notes that applications already compiled for AL2023 should generally work on AL2027, but recompiling the code may surface new warnings or errors due to changes in the compiler and its defaults. GCC 16.1 uses C23 as its default C standard and C++20 for C++.
DNF5 introduces another possible incompatibility. The dnf and yum commands still exist, but both now run on DNF5. DNF4’s python3-dnf Python API is gone, and tools that depend on it directly will need to move to python3-libdnf5.
systemd support for old System V service scripts also disappears, while RPM 6.0 replaces RPM 4.16. These are changes substantial enough to justify AWS opening a testing phase several months before considering the platform finished.
Amazon Linux 2027 vs. Ubuntu, Debian, Rocky Linux, and AlmaLinux
Comparing distributions purely by kernel version can be misleading. An enterprise distribution may run a kernel that looks old while maintaining security fixes and features for years through backports.
The more useful comparison looks at what environment each distribution is designed for, how long its support runs, and how much independence it offers from the cloud provider.
| Distribution | 2026 reference version | Reference kernel | Packages | Typical MAC security | Approximate support | Main focus |
|---|---|---|---|---|---|---|
| Amazon Linux 2027 | Preview 2027.0 | 7.1 | RPM / DNF5 | SELinux enforcing | Until 2032 | AWS, EC2, containers, AI |
| Ubuntu Server | 26.04 LTS | 7.0 GA | DEB / APT | AppArmor | 5-year standard; extendable | Cloud, servers, Kubernetes |
| Debian | 13 Trixie | 6.12 LTS at release | DEB / APT | AppArmor available | Until 2030 with LTS | General-purpose server |
| Rocky Linux | 10 | 6.12 | RPM / DNF | SELinux | Security until 2035 | Enterprise, RHEL compatibility |
| AlmaLinux | 10.2 | 6.12 | RPM / DNF | SELinux | Security until 2035 | Enterprise, RHEL compatibility |
Kernel versions reflect each release’s reference branch and don’t by themselves amount to a comparison of security, performance, or compatibility.
Ubuntu 26.04 LTS is a particularly interesting counterpoint. Canonical maintains its GA 7.0 kernel until April 2031 under standard security maintenance, with commercial options that extend that period considerably. Ubuntu also offers a much broader package catalog and isn’t built around a single cloud provider.
Debian 13 Trixie represents a different philosophy. It was released on August 9, 2025, and is set to receive three years of full support plus another two years of Long Term Support (LTS), running through June 30, 2030. Besides amd64 and ARM64, it supports architectures such as RISC-V, POWER, and IBM System z.
Rocky Linux 10 and AlmaLinux 10 are aimed especially at organizations looking for the enterprise environment of the Red Hat Enterprise Linux (RHEL) family. Their advantage over Amazon Linux isn’t having the kernel with the highest version number, but a much longer support cycle and a focus on infrastructure that can run in in-house data centers and across multiple cloud providers.
Rocky Linux 10 has general support planned through May 31, 2030, and security updates through May 31, 2035. AlmaLinux sets equivalent dates for its 10.x branch.
Which Linux Fits Best, by Scenario
| Need | Especially interesting option | Reason |
|---|---|---|
| Servers mainly on AWS | Amazon Linux 2027 | AWS-specific integration and optimization |
| ARM EC2 with Graviton | Amazon Linux 2027 | ARM64 images maintained directly by AWS |
| AWS Trainium/Inferentia | Amazon Linux 2027 | Integration with AWS Neuron drivers |
| General-purpose server | Debian 13 | Stability, independence, and a broad repository |
| Cloud and multi-cloud Kubernetes | Ubuntu 26.04 LTS | Broad vendor and tooling support |
| Migration from RHEL | Rocky Linux / AlmaLinux | Compatibility with the RHEL enterprise environment |
| Very long security cycle | Rocky 10 / AlmaLinux 10 | Security planned through 2035 |
| Very recent software within AWS | Amazon Linux 2027 | Especially current kernel and toolchains |
| Maximum portability across providers | Debian / Ubuntu | Less conceptual dependence on AWS |
Amazon Linux 2027 also incorporates AWS-LC, the cryptographic library maintained by Amazon and originally derived from BoringSSL. AWS is using it to improve cryptographic performance and gain tighter control over how TLS and other security functions integrate with its infrastructure.
The distribution also adds post-quantum cryptography capabilities and hardens several elements of the package supply chain. This security hardening pairs with SELinux being active from first boot, a decision that brings the default configuration closer to what’s typical in enterprise distributions from the RHEL family.
For artificial intelligence and machine learning, AWS highlights access to accelerator drivers, including those for AWS Neuron, used with its Trainium and Inferentia chips. This is one of the areas where vertical integration can matter more than simply comparing the number of available packages.
A Modern Distribution, But Not Yet for Production
AL2027 images are available for x86-64 and ARM64, both as Amazon Machine Images (AMIs) for EC2 and as container images. AWS also offers standard and minimal AMIs. The latter trim installed packages down to the essentials and are aimed at teams that prefer to build smaller server images.
AWS also maintains versioned repositories. An AMI is initially tied to a specific repository version, which allows more deterministic control over which package set an infrastructure uses. Administrators can later move to newer repositories or deploy new instances from an updated AMI.
The company plans to publish quarterly minor releases during the standard support phase. When the next generation of Amazon Linux appears, AL2027 will move into maintenance and focus mainly on security updates and critical fixes. AWS currently sets AL2027’s end of support at 2032.
There is, however, a more immediate date that shouldn’t be confused with that cycle: the preview released on September 3, 2026 is supported through March 31, 2027. Final support terms for the stable edition’s packages will be published once the general release arrives.
That’s why AL2027 shouldn’t yet be read as an immediate replacement for Amazon Linux 2023. AWS explicitly states that the preview is meant for experimenting, checking compatibility, and reporting issues ahead of general availability.
It does offer a fairly clear picture of the chosen direction, though. Amazon is building a distribution with much newer components, stricter mandatory security, and tight integration with EC2, Graviton, and its AI accelerators.
For a company fully committed to AWS, that specialization can be an advantage. For hybrid or multi-cloud infrastructure, Ubuntu, Debian, Rocky Linux, and AlmaLinux still offer something Amazon Linux doesn’t try to make its main selling point: running virtually the same operating system regardless of where the server ends up running.
