AWS customer-cloud regions

The AWS path uses customer-reviewed Terraform or CloudFormation to create a private, scoped worker foundation.

Activation gated Terraform and CloudFormation validated

Packaged foundation

The current AWS packages define:

• A customer-specific external-ID trust boundary.
• A least-privilege worker instance profile.
• Private subnets across at least two Availability Zones.
• An egress-only security group with no inbound rules.
• Immutable launch-template versions.
• Encrypted root and XFS copy-on-write volumes.
• A fail-closed Auto Scaling lifecycle hook.
• A dedicated, versioned bootstrap secret per host attempt.
• Immutable runtime manifests with exact SHA-256 verification.

Security architecture

flowchart TB
  MIOSA["MIOSA control plane"] -->|AssumeRole with external ID| Role["Customer control role"]
  Role --> ASG["Owned Auto Scaling resources"]
  ASG --> Host["Private worker host"]
  Host -->|Scoped role| Artifacts["Approved artifact source"]
  Host -->|One dedicated secret| Secret["Bootstrap acceptance bundle"]
  Host -->|Outbound TLS and WireGuard| MIOSA
  Host --> Guests["Firecracker workloads"]
  Guests --> COW["Encrypted XFS COW storage"]

Revoking the cross-account role is the customer control-plane kill switch.

The worker role cannot administer EC2, Auto Scaling, IAM, or unrelated storage.

Hosts receive no public IP and accept no inbound security-group traffic.

Readiness is fail-closed

Terraform and CloudFormation completion do not make a worker schedulable.

The packaged fleet begins at zero capacity.

When activation is enabled, each launched host must remain behind an Auto Scaling lifecycle hook until MIOSA verifies:

1. The expected immutable image and runtime generation.
2. Encrypted root and copy-on-write device mappings.
3. Nested virtualization and /dev/kvm.
4. Snapshot restore support.
5. Outbound control-plane and WireGuard reachability.
6. A fresh authenticated host session.
7. One real guest boot smoke.
8. Scheduler capability advertisement.

Timeouts abandon the launch instead of admitting an ambiguous host.

Current maturity

The Terraform, CloudFormation, bootstrap, runtime-artifact, and control-plane contracts are implemented and validated in repository CI.

General production activation remains gated because the capacity packages intentionally create zero active hosts and live provider mutation requires a certified AWS/KVM canary.

Do not describe AWS BYOC as generally available

The current public contract is architecture and controlled onboarding preparation. Production placement must remain disabled until the acceptance gate is certified and enabled for the organization.

What customers will control

• AWS account and selected region.
• VPC, private subnets, routing, and endpoints.
• Customer IAM review and revocation.
• KMS and cloud storage choices.
• Provider quotas and provider billing.
• Terraform state or CloudFormation stack.
• Final placement enablement.

Bring Your Own Cloud architecture Return to the complete control-plane and customer-cloud model.