69 AWS listings · 8 Linux families · x86_64 + ARM64Open the live index ↗

INDUSTRIES

A clearer Linux starting point for sector-specific workloads.

Every sector carries different obligations, dependencies, and failure modes. Choose the operating context first, then move into the catalog with that context intact.

01

Government & public sector

Give public-sector cloud teams a named, testable Linux artifact when missions demand repeatable configuration, traceable change, and clear responsibility boundaries.

Explore sector
02

Financial services

Standardize the Linux layer beneath regulated financial workloads while keeping resilience, data protection, evidence, and risk ownership with the teams that operate the service.

Explore sector
03

Industrial & manufacturing

Create a consistent Linux foundation for industrial cloud workloads where uptime, supplier integration, and the boundary between enterprise and operational systems require deliberate testing.

Explore sector
04

Healthcare & life sciences

Strengthen the operating-system starting point beneath health and research workloads while keeping privacy, clinical safety, data governance, and application controls in their proper scope.

Explore sector
05

Energy & utilities

Standardize cloud Linux for energy and utility workloads without obscuring the separate responsibilities surrounding critical infrastructure, operational technology, resilience, and field operations.

Explore sector
06

Technology & SaaS

Move repeatable operating-system security into the platform layer so product teams can start from a known image without giving up delivery speed or workload-specific ownership.

Explore sector
COMMON DECISION

Standardize the image without flattening the workload.

A hardened image can reduce configuration variation across teams while still allowing each regulated, critical, or customer-facing environment to validate its own application behavior and security responsibilities.

The right image is the one that fits the supported operating system, version, architecture, deployment model, and program context—not simply the strictest-looking option.

Start with the workload. Finish with an exact build.

Use the catalog to select the Linux distribution, release, architecture, and product line that fits the service.