Amazon Linux 2027 makes migration rehearsal urgent

What happened: the next platform baseline is testable

AWS says Amazon Linux 2027 builds on AL2023 and will follow the same versioned-repository model, with support planned through 2032. The documentation describes quarterly minor releases during standard support, followed by a maintenance phase focused on security updates and critical fixes. Each release couples an image with a repository version, so teams can deliberately select a known package set instead of silently consuming an unspecified latest state.

The preview includes refreshed system components and language runtimes, plus an Amazon ECR Public container image. It also supports UEFI Secure Boot on compatible EC2 instances, although Secure Boot is not enabled by default on standard images. These changes affect more than an AMI identifier: package availability, runtime versions, image pipelines, boot settings and operational tooling all belong in the compatibility test.

Why it matters: preview gaps expose hidden assumptions

AWS's known-issues page says the initial preview has no NVIDIA drivers, no on-premises Hyper-V, KVM or VMware images, and no working Systems Manager Patch Manager operations. AWS advises manual DNF updates for now. Those limitations are valuable evidence for teams that depend on GPU workloads, hybrid images or centrally managed patch compliance: a successful application start does not prove the operating model is ready.

The platform's deterministic upgrade design also requires an explicit procedure. A newly installed system is locked to its installed release, and an ordinary DNF upgrade does not automatically move it to a newer repository version. That can improve repeatability, but only if image automation, vulnerability response and fleet reporting record which release each workload is expected to run.

The practical implication: build a migration evidence pack

Create a disposable AL2027 environment from infrastructure code and deploy a representative service with production data removed. Record every required package and repository, then run build, startup, health, performance and rollback checks. Test the exact instance families and container paths you use; include boot-mode and Secure Boot behaviour where those controls matter.

Exercise the operational path as carefully as the application. Confirm logging, metrics, endpoint protection, vulnerability scanning, backup, recovery and patch reporting. Where Patch Manager or another dependency is unavailable, document the gap rather than inventing a permanent workaround for a preview. Keep AL2023 production images and rollback procedures unchanged while the evidence develops.

Turn failures into dated migration decisions: dependency to replace, control awaiting vendor support, or workload that should remain on its current platform. Re-run the pack when AWS publishes a new preview release. The goal is not to be first on AL2027; it is to reach general availability with fewer unknowns and a migration plan that can be explained, tested and reversed.