Cloud Foundation Build

The problem an AWS landing zone solves

Common situation: the company started in one account, grew quickly, and now every team negotiates security from scratch while much of the setup is still clicked in by hand. Root cause: no account-vending or guardrail baseline means security is per-team tribal effort and drift is unbounded; hand-built consoles can't be reviewed, reproduced, or audited.

What you own when we leave

• A Terraform/IaC monorepo (or modules) for your org/account structure — multi-account on AWS, multi-cloud where in scope — with an account-vending/baseline pattern your team applies to create new accounts.
• A guardrail set (Service Control Policies on AWS, equivalent org policies on other clouds) enforcing your non-negotiables by default.
• Centralized identity wiring (SSO/IdP federation, baseline roles, least-privilege patterns).
• Baseline network and connectivity scaffolding (VPC/segmentation patterns, shared services).
• Centralized logging, audit, and guardrail-violation visibility, as code.
• An ADR log capturing the structure decisions, and runbooks for vending accounts, changing guardrails, and break-glass.

Not a reference architecture diagram you then pay someone else to implement. The foundation is running, in your accounts, defined in your repo.

How we approach it

1. 01

   Discovery

   We read your accounts, configs, and constraints directly (scoped read-only access or exported state), map the real current state, and agree on a written scope and success criteria before any code is written.

2. 02

   Architecture Decision Records

   We write down the key decisions — what we’re doing, the options we rejected, and why — as ADRs in your repo, so the reasoning survives long after we’re gone and you can challenge it before we build.

3. 03

   Implementation

   We build the solution as reviewable Terraform/IaC in small, tested pull requests against your CI, so you watch it land incrementally and nothing arrives as a black box.

4. 04

   Handover

   We walk your team through the repo, the threat model, and the runbooks live, confirm you can apply/destroy/extend it yourselves, and then we leave. You own everything — there is no phase 5 where you still need us.

Engagement shape

A fixed-scope build over a defined cloud footprint and account model, delivered as reviewable Terraform PRs and ended with a live handover. Scope is set by your cloud count, account model, and guardrail strictness, all agreed in writing first.

An illustrative example of the format

# guardrails/scp.tf — org-wide non-negotiables, attached at the root
resource "aws_organizations_policy" "baseline" {
  name = "baseline-guardrails"
  type = "SERVICE_CONTROL_POLICY"
  content = jsonencode({
    Version = "2012-10-17"
    Statement = [
      {
        Sid    = "ProtectAuditTrail"
        Effect = "Deny"
        Action = [
          "cloudtrail:StopLogging",
          "cloudtrail:DeleteTrail",
          "cloudtrail:UpdateTrail",
        ]
        Resource = "*"
      },
      {
        Sid      = "DenyLeavingOrg"
        Effect   = "Deny"
        Action   = "organizations:LeaveOrganization"
        Resource = "*"
      },
    ]
  })
}

resource "aws_organizations_policy_attachment" "baseline_root" {
  policy_id = aws_organizations_policy.baseline.id
  target_id = aws_organizations_organization.this.roots[0].id
}