Skip to main content
  1. Blog
  2. Article

David Beamonte
18 November 2026

Automating bare metal infrastructure in FIPS-regulated environments with MAAS


Organizations operating sensitive infrastructure, particularly in the government, defense, and financial services sectors, often face strict security and compliance requirements. These requirements extend beyond applications and operating systems (OSs) to the tools responsible for provisioning and managing the underlying physical infrastructure.

The Federal Information Processing Standard (FIPS) 140-3 defines security requirements for cryptographic modules used to protect sensitive information. Supporting FIPS requirements across the infrastructure stack is therefore an important consideration for organizations operating in regulated environments.

With the release of MAAS v3.7.4, Canonical introduces long-awaited FIPS mode support for the bare metal management control plane. This allows organizations to apply stricter cryptographic and security controls to their infrastructure, while maintaining automated provisioning and lifecycle management of physical servers.

What FIPS mode brings to MAAS

Canonical MAAS (Metal as a Service) is an open source platform that brings cloud-like automation to bare metal infrastructure. It provides a centralized control plane to discover, test, provision, configure, and manage physical servers throughout their lifecycle. Through its APIs and integration with infrastructure-as-code tools, MAAS enables organizations to manage large fleets of servers with consistent, repeatable operations. You can learn more about how MAAS helps organizations manage their data centers in our whitepaper.

As the control plane for physical infrastructure, MAAS communicates with server management controllers, manages remote power operations, and provisions OSs. These functions involve network connections, authentication, and cryptographic mechanisms that must also meet the organization’s security requirements.

When FIPS mode is enabled, MAAS automatically applies stricter security controls. These include restricting Transport Layer Security (TLS) and Secure Shell Protocol (SSH) connections to approved cryptographic algorithms, validating key types and sizes, requiring trusted SSH host keys, and rejecting power management configurations that rely on insecure protocols. For example, Intelligent Platform Management Interface (IPMI) connections must use cipher suite 17, and unsupported power drivers are rejected.

MAAS also makes security hardening mandatory when FIPS mode is active. Administrators can identify configuration problems through validation errors and security notifications, while the MAAS API provides users with visibility into the FIPS and hardening status of each controller.

By integrating these controls into MAAS, infrastructure teams can enforce security requirements more consistently, without relying entirely on manual checks or custom validation scripts.

Getting started with FIPS mode in MAAS

MAAS supports FIPS mode on its controllers and can also deploy Ubuntu machines with FIPS-enabled kernels. These are separate capabilities, and the configuration process depends on whether you are setting up a new environment, adapting an existing deployment, or provisioning managed machines.

Enabling FIPS mode on MAAS controllers

For new deployments, we recommend starting with an Ubuntu host already running in FIPS mode. Using an Ubuntu Pro subscription, administrators can enable the fips-updates service and reboot the host before deploying MAAS.

MAAS detects FIPS mode at startup and automatically activates the corresponding security controls. Administrators can then validate the configuration and verify the FIPS status through the MAAS API. In deployments with multiple controllers, FIPS mode must be enabled consistently across all of them.

Detailed instructions are available in the guide to enabling FIPS mode on a MAAS controller.

Adopting FIPS mode on existing deployments

For environments with FIPS requirements, it is best to begin with a new MAAS deployment with FIPS mode enabled from the outset. Enabling FIPS mode on an existing deployment can introduce complex dependencies between components, potentially leading to compatibility issues, unexpected conflicts, and unsupported configurations. For this reason, enabling FIPS mode on existing deployments should only be considered as a last resort, when a fresh deployment is not feasible. If adopting FIPS mode on an existing deployment, it is critical to carefully plan and test deployments before transitioning.

Existing MAAS installations require additional preparation before enabling FIPS mode. Administrators must review their power management configurations, ensure compatible IPMI cipher suites, register trusted SSH host keys, and validate existing cryptographic keys and certificates. Supporting services such as PostgreSQL also need to be reviewed.

This preparation is particularly important, because MAAS does not automatically revalidate previously stored cryptographic material. As a result, converting an existing populated deployment to FIPS mode is not a supported path to achieving FIPS compliance.

The migration guide explains the required preparation and considerations for existing environments.

Deploying machines with FIPS-enabled kernels

Separately from controller FIPS mode, MAAS can provision Ubuntu machines with FIPS-enabled kernels using MAAS’s standard deployment workflow and cloud-init.

After deploying Ubuntu, cloud-init activates Ubuntu Pro, installs the FIPS kernel, and reboots the machine. This makes it possible to incorporate FIPS kernel installation into existing bare metal provisioning workflows.

For prerequisites and configuration details, check the MAAS guide to deploying FIPS kernels. The documented procedure covers Ubuntu LTS deployment and requires an Ubuntu Pro subscription and network access to obtain the necessary packages.

Improve the security of your infrastructure operations with MAAS

With FIPS mode support in MAAS 3.7.4, organizations have more control over the cryptographic policies used to manage their physical infrastructure. Security restrictions can be enforced as part of normal MAAS operations, reducing the need to maintain separate processes for security validation and infrastructure provisioning.

If you are planning to deploy MAAS in an environment with FIPS requirements, start by reviewing the MAAS security documentation to understand the prerequisites, supported configurations, and limitations.

You can also contact Canonical experts to discuss your infrastructure security and compliance requirements.


Related posts

MAAS installation: bare metal provisioning is easier than ever

MAAS brings cloud-like automation to physical servers. It helps teams discover, commission, deploy, and repurpose machines from a central control plane, turning bare metal into...

Managing Ubuntu on bare metal at scale

Modern infrastructure teams are expected to deliver cloud-like speed, consistency, and reliability, even when their workloads run on physical servers. Bare metal remains...

Ubuntu Server: a platform made for enterprise scale

A platform is an environment that allows software to run smoothly across the infrastructure, runtime, and application layers. The key word there is “smoothly”: a good platform...

VMware hypervisor deployment using MAAS

Most modern datacenters are inherently heterogeneous. VMware environments coexist with container platforms, databases, and other bare-metal workloads, often on the same...