Platform foundation

Your teams ship from day one, on AWS and GitHub set up as code

Fixed price · 4 to 7 weeks

Scoped and priced up front in a statement of work.

Book a free 30-minute introductionContact for outside-IR35 contract availability · UK-based, remote-first

Somewhere safe for your teams to ship from on day one, where nobody waits on a ticket for an account, access or a repo. It's the AWS and GitHub structure I run for Sudoblark and have set up for clients, delivered as code to a fixed scope, whether you're starting fresh or bringing an existing setup under code.

Who it's for

  • You're about to build or launch a product, and your engineers need somewhere safe to ship from on day one.

  • Your developers wait on tickets for an account, access or a new repo, and your platform team spends its time on requests instead of the platform.

  • You're starting on AWS for anything more than a proof of concept, and want your environments kept apart from day one.

  • Your AWS accounts or GitHub organisation grew by hand, and need bringing under code without disruption.

  • You want access, guardrails and repo standards to change by reviewed pull request, and keep holding after I leave.

  • Your code lives on GitHub, and your pipelines run on GitHub Actions. Other CI/CD platforms can be supported at additional cost, agreed in the statement of work.

What's included

  • Environments that can't break each other: A separate AWS account for each environment, so a mistake in development can't reach production. Each account's name and root email come from a single entry.

  • Rules no account can break: Every account follows them, including accounts created later: approved regions only, no leaving the organisation, and the production audit trail protected.

  • One sign-in for everyone, with short sessions: People sign in once, from your own directory if you have one, and you can see in one place who can do what, and where.

  • Deployments with no keys to leak: Pipelines deploy to every account without long-lived keys, and a new repo or account can deploy with nothing new to set up.

  • Every repo set up to your standards: Your GitHub organisation, repositories, branch protection and teams held as code, with people listed there or synced from your directory. It scales from one organisation to an enterprise.

  • Every change reviewed, access included: The organisation and everyone's access change by reviewed pull request, like any other code, so the standards hold after I leave.

  • A platform your team runs after I leave: A walkthrough of adding an account, a person and a repo by pull request, and an onboarding guide for every developer.

What I need from you

  • A root email for every account: As distribution lists or plus addresses on your own domain.

  • An AWS management account: One you own and pay for, created on your admin alias with root MFA registered, and a temporary administrator session in it for the first apply.

  • A GitHub organisation: One you own and pay for, with me added as an owner.

  • A GitHub plan that covers the rules you need: Team at least for rulesets on private repos, and Enterprise for commit message and tag rules.

  • An identity admin, if you run Entra ID: To connect it to Identity Centre and GitHub, following the guides I hand over.

  • The owner of each existing AWS account: To accept the organisation's invitation, so the account can come under code.

How it works

PhaseIndicative timingWhat is delivered
Discover and decideWeeks 1 to 2Account names and root emails, the region, the identity source and the GitHub plan, agreed up front. Hand-offs started with your identity admin and the owner of each existing account.
Build the AWS organisationWeeks 2 to 3The organisation created from your management account and handed to code. CI bootstrapped with a hub role and a spoke in each account, so every plan and apply runs in CI. Default VPCs removed and budget alerts added in every account.
Bring GitHub under codeWeeks 3 to 5The GitHub App Terraform signs in as, then your organisation and repositories in Terraform, importing whatever already exists.
Hand overWeeks 6 to 7A walkthrough of adding an account, a person and a repo by pull request, an onboarding guide for every developer, and admin handed to someone on your team.

Timings are indicative. They depend on the number of accounts, how much already exists to import, and whether an identity provider is connected. Hand-offs can extend them, since an identity team works to its own availability and Entra ID needs a tenant-wide approval.

Operational costs

The foundation costs under $1 a month to run on AWS. AWS Organizations and IAM Identity Centre carry no charge, so the only cost is the storage for its Terraform state. Your GitHub plan is licensed per user, and grows with your team.

What you're left with

The code in your repositories, running in your accounts and documented, with your team able to change it by pull request.

“Ben played a pivotal role in setting infrastructure as code standards and deployment processes, allowing my team of engineers to focus on application code and in turn create their own supporting infrastructure. This helped speed up delivery and also led to smooth deployments to a production environment.”
— Data Architect

What's not included

  • What runs in the accounts: Workloads, and the application code and pipelines that deploy them.

  • A fuller landing zone: A Security OU for log archive and security tooling, or an Infrastructure OU for networks and shared services, added once compliance or four or more VPCs call for one.

  • DNS: Such as a zone per account, delegated from production's apex.

  • Narrowing CI's access: CI's roles start as administrator in each account, and narrow once the services you use have settled.

  • Connecting your identity provider: Your identity team does it, from the guides I hand over.

  • AWS and GitHub charges: These stay with you.

Need what runs in the accounts built too? That's contract delivery.

© 2026 Sudoblark Ltd. | Registered in England and Wales | Company number 14712154 | VAT number GB 438 1548 82 | Registered office: 1 Cedar Office Park, Cobham Road, Wimborne, BH21 7SB