Skip to main content

S2 — Fresh AWS Self-Service

Your DevOps team provisions a fresh AWS environment using our reference Terraform snippets, then installs the OpenBox Helm chart. You own the deployment end-to-end.

When to pick S2​

  • You have a DevOps / SRE team with EKS + Terraform experience
  • You want full control over infra decisions (region, VPC, tagging, security posture)
  • You already run other workloads on AWS and want OpenBox to slot into your standards

Prerequisites​

Before starting, verify:

  • AWS account with billing enabled
  • IAM user or role with PowerUserAccess (for initial terraform apply)
  • terraform ≥ 1.5
  • aws CLI configured (aws sts get-caller-identity succeeds)
  • kubectl ≥ 1.27
  • helm ≥ 3.12
  • S3 bucket for Terraform remote state (or DIY step 01 will create one)
  • Domain you control (for ingress TLS) — optional if using plain HTTP for dev

Estimated time​

60–90 min end-to-end on first run (fastest is 30 min if you're familiar with EKS provisioning).

Overview of the 4-step flow​

  1. AWS account setup → — enable services, prepare backend (Terraform state OR CloudFormation admin)
  2. Provision infrastructure — pick ONE:
  3. Helm install → — deploy OpenBox chart wired to IaC outputs
  4. Post-install validation → — smoke tests + first login

Hit a snag? See Troubleshooting →.

Do not mix IaC tools

Terraform and CloudFormation both create the same underlying AWS resources. Do not run one after the other in the same account/region — you'll get two-writer conflicts and drift. Pick one, stick with it.

Cost estimate​

Steady-state small prod: ~$2,000/mo (self-hosted Temporal) or ~$1,740/mo (Temporal Cloud). Full breakdown in System requirements.

What's out of scope​

Openbox does not prescribe your region strategy, edge protection (CloudFront/WAF), admin access (Verified Access/VPN), observability stack (Datadog/Prometheus/etc), DR tier, or compliance program. See AWS integration surface — What this page does NOT cover.