GovCloud Mission Platform on EKS with NIST 800-53 as Code Skip to content
← Back to Blog

How a Defense Organization Modernized a GovCloud Mission Platform with AWS EKS, CDK & NIST 800-53 as Code

GovCloud mission platform architecture on AWS EKS with NIST 800-53 policy-as-code pipeline

By Michael Walker, CEO, Horus Technology

Horus Technology rebuilt a U.S. defense organization’s mission simulation platform on AWS GovCloud as infrastructure-as-code. We replaced laptop-driven deployments with a reproducible Amazon EKS, AWS CDK, and GitLab OIDC pipeline that enforces NIST 800-53 controls as code.

Overview

Challenge Run a regulated, IL-5 / CUI mission simulation platform on AWS GovCloud without the fragile, non-reproducible delivery model the program had outgrown.
Solution Partner with Horus Technology to rebuild the environment in AWS CDK, deployed to Amazon EKS through a GitLab CI pipeline federated with OIDC and gated by NIST 800-53 policy-as-code.
Outcome A platform that can be destroyed and rebuilt identically, ships with no long-lived AWS credentials, and enforces NIST 800-53 controls as code in the pipeline.

Who is the customer behind this platform?

The customer is a U.S. defense and public-sector organization that operates a mission simulation platform. Because the workload handles Controlled Unclassified Information (CUI) under an IL-5 mission profile, it runs exclusively on AWS GovCloud (US) and must satisfy a NIST 800-53 control set. (This is an anonymized public case study; the customer’s identity is withheld for security reasons.)

What was wrong with the platform’s delivery model?

The platform worked, but the way it was delivered did not scale to a regulated production posture. Services were deployed by hand from developer workstations using manual helm upgrade commands, and continuous-integration jobs authenticated to AWS with long-lived static access keys. There was no infrastructure-as-code and no single reproducible path to stand the environment back up.

For a CUI / IL-5 mission, that delivery model carried real risk. Static CI credentials are a standing attack surface. And without a reproducible build, a disruption or an accidental teardown had no documented recovery path, which threatened mission availability.

If left unaddressed, the program faced compounding risk:

  • Accreditation risk: a failed or delayed Authority to Operate and recurring audit findings.
  • Availability risk: mission downtime with no documented, reproducible rebuild path.
  • Security risk: standing credential and supply-chain exposure that a defense accreditation simply will not accept.

The program needed its infrastructure and its security controls to become code.

How did Horus Technology rebuild the platform on GovCloud?

Horus Technology re-platformed the environment as code on AWS GovCloud and wrapped it in a federated, policy-gated delivery pipeline. The environment is defined in AWS CDK, and the GitLab CI pipeline runs cdk deploy to provision it and helm upgrade to roll the workload out to Amazon EKS. Nobody runs Helm by hand.

1. Reproducible infrastructure with AWS CDK and Amazon EKS

  • AWS CDK + Helm: AWS CDK defines the environment, and the GitLab CI pipeline deploys the Helm-packaged workload to EKS, so the same stack can be destroyed and rebuilt identically from source.
  • Amazon EKS (Kubernetes 1.29): the mission services run in private subnets across multiple Availability Zones in AWS GovCloud (us-gov-west-1), with EKS control-plane logging fully enabled.
  • Amazon RDS and Amazon S3: the data tier for the platform runs on managed AWS services.
  • Amazon ECR: container images are stored in Amazon ECR.

2. Federated identity and encryption

  • IAM OIDC federation (GitLab): GitLab CI is federated with AWS through OIDC, so there are no long-lived AWS access keys in the pipeline.
  • AWS KMS: AWS KMS envelope encryption protects Kubernetes secrets.

3. Compliance as code

The policy gate is what separates this from an ordinary IaC rollout. NIST 800-53 controls are enforced as code in the GitLab CI pipeline (policy-as-code), so a change that does not meet them fails the build before it deploys. Compliance is checked as part of normal delivery rather than assembled by hand at audit time.

What did the engagement change?

The engagement replaced the fragile, non-reproducible delivery model with a pipeline where the infrastructure is defined as code and the controls are enforced at build time. The mission platform has been in production on AWS GovCloud since May 2026.

Key Results

  • Reproducibility: the same stack can be destroyed and rebuilt identically from AWS CDK.
  • Security posture: no long-lived AWS access keys, with GitLab CI federated through OIDC.
  • Compliance as code: NIST 800-53 controls, including audit logging, transport protection, and key management, are enforced as code in the pipeline.
  • Controlled deployment: deployments reach EKS through the GitLab CI pipeline, not from developer workstations.

Before and after, side by side:

Before After
Manual helm upgrade from laptops Pipeline-run cdk deploy and helm upgrade
Static AWS access keys in CI GitLab OIDC federation, no long-lived keys
No infrastructure-as-code Environment defined in AWS CDK

About the Partner

Horus Technology is a San Diego-based AWS and AI consulting firm founded by former AWS engineers. We help organizations design, build, and operate secure, well-architected cloud platforms, with specialization in AWS DevOps and infrastructure-as-code, regulated and GovCloud workloads, generative AI, and intelligent document processing. Our team delivers production systems that meet rigorous compliance bars while staying reproducible, observable, and cost-governed.

Highlights

Industry Defense / Public Sector
Solution GovCloud DevOps modernization: infrastructure-as-code, federated CI/CD, and compliance as code
AWS services Amazon EKS, Amazon RDS, Amazon S3, AWS CDK, Amazon ECR, AWS KMS, IAM OIDC federation
Delivery Horus Technology

See also: AWS Consulting Services | Generative AI Services | AWS Migration Case Study

Get started

Tell us what you're trying to solve.

AWS architecture, a GenAI pilot, document processing, a migration off another cloud — tell us where you're stuck and we'll tell you if we can help. We build in your own AWS account, so what's yours stays yours.