Essential services cannot wait
Evaluate change, patching, backup, and recovery decisions against the service consequences of degraded availability.
INDUSTRIES / WATER
Supported cloud images for workloads around treatment, distribution, monitoring, reporting, asset management, and remote operating sites.
OPERATING CONTEXT
Cloud workloads may sit around treatment and distribution operations rather than inside direct control. Their security still depends on clear ownership, supportable platforms, controlled access, practical recovery, and decisions that smaller or distributed teams can sustain.
Evaluate change, patching, backup, and recovery decisions against the service consequences of degraded availability.
Treat connectivity, privileged access, monitoring coverage, and local recovery constraints as part of the image decision.
Prefer baselines that can be selected, rebuilt, tested, documented, and supported without relying on one-off configuration.
IMAGE SELECTION
Choose the image around the actual water-sector workload, responsible team, OS support horizon, architecture, and validation plan.
Use the named profile and product scope—not the page headline—as the description of image-level hardening.
Confirm application support, release lifecycle, package behavior, and the team's ability to maintain the platform.
Choose x86_64 or arm64 against workload compatibility, tooling, performance, and support requirements.
Test identity, networking, applications, monitoring, recovery, exceptions, and operating procedures before production use.
RELEVANT FRAMEWORKS
Each framework page keeps the image boundary explicit and leads back to the same product catalog.
NEXT STEP