Cloud Infrastructure
Accounts, networking, and IAM on AWS, Azure, and GCP, written in Terraform or Pulumi.
Who this is for
- Teams on AWS, Azure, or GCP whose accounts were created by hand
- Groups writing Terraform without a standard for the next account
- An account that also has to reach a private data center
The next account matches the last good one
Account structure, IAM, and networking, so a new account does not start as a one-off. Terraform or Pulumi, in the repo your team already reviews.
What that account gets on day one
The network, the identity rules, and where logs are allowed to go. The account is ready for the cluster you already run, or the one you are about to build.
A private data center on the other side
When a workload has to stay in a private data center, the network rules in the account define what can reach it, and what cannot.
Capabilities
- Account structure, networking, and IAM
- Terraform and Pulumi
- The boundary between a cloud account and a private data center
Example: Amazon ECS migration
Common questions
Do you build multi-cloud for its own sake?
No. We work in the cloud you run. A second cloud is only in scope when a workload or a customer constraint requires it.
Is the cloud bill part of this?
It can be. Cost tags can go on from the first account. Quotas and per-team dashboards come later, once each team owns its spend.
How do engagements start?
A 30-minute call. We look at the accounts you have and whether the work is a landing zone, a review, or ongoing work.