11 · FIPS 140 mode¶
Outcome: you see exactly what one switch, --var fips_mode=true, changes in an environment, what it refuses, and how to inspect its evidence: an AWS FIPS environment rendered offline, the refusals that keep a configuration honest, the platform catalog's FIPS tiers, and (with an Ubuntu Pro token) a FIPS lab on VMware whose kernel, sshd and keys can be checked by cs scan fips. Offline configuration checks do not establish runtime assurance.
Verified with --dry-run (Terraform render + validate); run for real with cloud credentials
tests/scenarios/11-fips-140-mode.sh renders the AWS and VMware FIPS environments, checks every refusal below and runs cs scan fips offline (the configuration, key and declared endpoint checks pass, while missing runtime evidence makes the overall result INCOMPLETE / exit 3). The live host checks of step 6 are not part of that verification: they need an Ubuntu Pro token, and the script runs them on VMware only with CLOUDSEED_LIVE=1 and UBUNTU_PRO_TOKEN set.
| Time | Cost | Level | Needs |
|---|---|---|---|
| ~15 min offline, ~45 min with the VMware lab | $0 offline; AWS as in 02 plus a VPN host | Advanced | For the live lab: an Ubuntu Pro token (free for personal use) |
What you'll build¶
%%{init: {"flowchart": {"nodeSpacing": 30, "rankSpacing": 38, "padding": 12}}}%%
flowchart LR
sw["--var fips_mode=true<br/>(chosen at creation)"] --> aws & hosts & k8s & plat
aws["AWS<br/>FIPS endpoints for the provider and the S3 backend<br/>us-east-1/2, us-west-1/2, GovCloud only"]
hosts["Hosts<br/>kernel fips=1, FIPS crypto policy<br/>sshd: AES-GCM/CTR, SHA-2, ECDH P-curves<br/>RSA-4096 SSH key"]
k8s["Kubernetes<br/>EKS: Bottlerocket FIPS AMIs · AKS: fips_enabled pools<br/>GKE: COS · VMware: RKE2 only"]
plat["Platform catalog<br/>compatible · tls-restricted · crypto-restricted · refused"]
aws & hosts & k8s & plat --> verify["cs scan fips<br/>PASS / FAIL / INCOMPLETE / N/A"]Before you start¶
- Nothing for steps 1 to 5: they run offline.
- For step 6: VMware Fusion Pro / Workstation Pro as in 01 and an Ubuntu Pro token, because the FIPS-validated modules for Ubuntu come with Ubuntu Pro.
Step 1: Read what FIPS mode does¶
Step 2: Render an AWS FIPS environment¶
cs setup aws -y --env fips --region us-east-1 --allow-ip 203.0.113.7 --var fips_mode=true --var enable_kubernetes=true --var enable_vpn=true --dry-run
Expected output (abbreviated)
▲ FIPS mode: the FIPS-validated modules for the VPN host (Ubuntu) come with Ubuntu Pro, and UBUNTU_PRO_TOKEN
is not set. export UBUNTU_PRO_TOKEN=... or store it with: cloudseed creds set UBUNTU_PRO_TOKEN
● FIPS mode: FIPS images/endpoints, kernel fips=1 on every host, FIPS-only SSH/TLS algorithms, RSA-4096 SSH
keys. Platform items are checked for FIPS capability at install time; verify with: cs scan fips
● Generating an RSA-4096 SSH key pair (FIPS mode) at ~/.cloudseed/envs/aws-fips/ssh/id_rsa
...
│ fips_mode true │
...
✔ Dry run complete. Rendered root(s): ~/.cloudseed/envs/aws-fips/stack, ~/.cloudseed/envs/aws-fips/bootstrap
A dry run or --plan-only only warns about the missing token; a setup that applies (you answer yes in a terminal, or pass --auto-approve) stops before creating anything.
Step 3: See what FIPS mode refuses¶
cs setup aws -y --env fips-eu --region eu-west-1 --allow-ip 203.0.113.7 --var fips_mode=true --dry-run
cs setup vmware -y --env fipslab --var fips_mode=true --var enable_kubernetes=true --var kubernetes_distro=kubeadm --dry-run
cs setup gcp -y --env fipsts --project-id my-gcp-project --allow-ip 203.0.113.7 --var fips_mode=true --var enable_vpn=true --var vpn_type=tailscale --dry-run
Expected output: each one stops, nothing is saved
✖ FIPS mode is on, but this configuration cannot be FIPS-compliant:
- region eu-west-1: AWS has FIPS 140 endpoints for everything this stack uses only in us-east-1,
us-east-2, us-west-1, us-west-2, us-gov-east-1, us-gov-west-1; pick one of those with --region.
✖ FIPS mode is on, but this configuration cannot be FIPS-compliant:
- kubernetes_distro=kubeadm: upstream kubeadm binaries are not FIPS builds; use kubernetes_distro=rke2
(FIPS-validated Go crypto).
✖ FIPS mode is on, but this configuration cannot be FIPS-compliant:
- vpn_type=tailscale: WireGuard (ChaCha20-Poly1305) is not a FIPS-approved cipher; use vpn_type=openvpn
(AES-GCM, TLS 1.2+).
FIPS mode is chosen at creation (the SSH key type depends on it) and cannot be toggled on an existing environment.
Step 4: Inspect offline evidence¶
Expected output
╭─ FIPS 140 verification · aws-fips ────────────────────────────────────────────╮
│ ✔ config fips_mode enabled for the environment fips_mode=true │
│ ✔ ssh environment SSH key is FIPS-approved (RSA-4096; ECDSA only on │
│ GCP/VMware) ssh-rsa (4096 bits) │
│ ✔ cloud AWS provider uses FIPS endpoints provider.aws.use_fips_endpoint │
│ │
│ ? hosts host runtime not checked no deployed host evidence │
│ ? k8s cluster not checked no reachable cluster evidence │
│ INCOMPLETE - 3 passed, 0 failed, 2 unknown │
╰────────────────────────────────────────────────────────────────────────────────╯
Expect exit 3 here: the dry run has created configuration, not running hosts or a cluster. Keep those unknowns visible. With no failed checks, a runtime gap remains INCOMPLETE; any definite failed check makes the result FAIL.
On a deployed environment the same command also checks reachable hosts (kernel fips_enabled, sshd and OpenSSL algorithms), the node images, the RKE2 build, the TLS policy on the shared Gateway and the FIPS capability of every installed platform item.
Step 5: The platform catalog in a FIPS environment¶
Items come in four tiers: compatible (installed), tls-restricted (Envoy Gateway, ingress-nginx: installed with TLS 1.2+ and FIPS cipher suites, flagged by cs scan fips), crypto-restricted (cert-manager, sealed-secrets, Velero, CloudNativePG: installed because the platform needs them, and flagged) and the rest (application stacks with their own crypto, like the ai group: skipped unless --force).
Step 6: A FIPS lab on VMware (live)¶
cs creds set UBUNTU_PRO_TOKEN
cs setup vmware -y --env fipslab --var fips_mode=true --dry-run
cs setup vmware --env fipslab --var fips_mode=true
cs ssh vmware --env fipslab -- cat /proc/sys/crypto/fips_enabled
cs scan fips vmware --env fipslab
creds set UBUNTU_PRO_TOKEN asks for the token with hidden input. Every VM attaches Ubuntu Pro, enables fips-updates and reboots into the FIPS kernel, so the SSH check prints 1. Add --var enable_kubernetes=true for an RKE2 cluster in FIPS mode.
Use an agent, MCP or the UI¶
Follow the same numbered steps and verification/cleanup conditions through your chosen interface. Start with the interface setup and coverage guide; replace account/project/subscription and SSH placeholders before any live request.
Agent prompt: “Follow the FIPS walkthrough for aws-fips. Preview the exact target changes and paid image requirements, explain unsupported combinations, then verify the resulting host/node evidence after approved deployment. Do not call an unverified deployment certified.”
MCP starter: cloudseed_setup with:
{
"cloud": "aws",
"env": "fips",
"region": "us-east-1",
"allow_ip": "203.0.113.7/32",
"vars": {
"fips_mode": true,
"enable_kubernetes": true,
"enable_vpn": true
},
"dry_run": true
}
Use the matching tool for each remaining step in this page; the command-to-tool map lists the tool family. Keep aws-fips selected. Preview first; add confirm:true only to the specific change you have authorized. Host bootstrap, provider login and interactive applications retain their documented human steps.
UI: Create → AWS: select fips and set fips_mode plus the Kubernetes/VPN options from the chosen branch of this page. Preview and inspect cost before apply. Use Resilience → Scans → fips and host checks for verification; enter paid subscription credentials only through Credentials or provider login.
Verify it worked¶
scan fipsends with INCOMPLETE / exit 3 for this offline preview. A FIPS-enabled environment can return PASS, FAIL or INCOMPLETE based on the collected checks; enablement alone is not a pass. A non-FIPS environment returns N/A. Read unknowns, coverage limits and remediation in the full JSON/Markdown report.- On the live lab:
/proc/sys/crypto/fips_enabledis1andsshd -Tlists only FIPS-approved ciphers and MACs.
Clean up¶
cs destroy aws -y --env fips --purge --auto-approve
cs destroy vmware -y --env fipslab --purge --auto-approve
cs creds unset UBUNTU_PRO_TOKEN
What just happened¶
- One variable fans out to every layer: provider endpoints, images, kernel settings, the Ansible
fipsrole, SSH key type, sshd and OpenVPN cipher lists, the Kubernetes distro, the Gateway's TLS policy and the catalog tiers. - Setup refuses combinations that can never be compliant instead of silently building something that is not.
- Learn more: Security and FIPS · Credentials · Explain index
Next steps¶
- 10 · Compliance scans:
cs scan stigincludes FIPS checks too. - 12 · Private access with a VPN: OpenVPN is the FIPS-compatible choice.
- 02 · AWS landing zone: apply the FIPS environment for real.