Cloud Architecture & Modernization
Landing zones, network and identity design, resilience and governance for Azure and AWS, built to be repeated.
The problem
Most cloud estates grew one project at a time. Accounts follow no pattern, networking was decided per workload, identity is a mix of what each team knew, and nobody can say what would happen if a region went away. New work inherits the complexity and adds to it.
What you receive
- Target architecture with the decisions and their trade-offs written down
- Landing-zone design and, where wanted, the Terraform to build it
- Resilience assessment with tested recovery objectives
- A sequenced roadmap the team can execute without us
Capabilities
- Cloud architecture reviews with prioritised findings
- Azure and AWS landing zones: subscription/account structure, policy, identity, networking
- Hybrid and private connectivity (ExpressRoute, Direct Connect, VPN, private endpoints)
- Identity architecture: Entra ID, IAM, workload identity, privileged access
- Environment segmentation and regional design
- High availability and disaster recovery that has actually been rehearsed
- Cloud governance: policy as code, tagging, cost allocation, guardrails
- Legacy modernization paths: what to keep, what to replatform, what to retire
Example engagement
Landing zone for a company consolidating three acquired Azure tenants
Reviewed the inherited estates, designed a management-group and subscription hierarchy with shared networking and identity, built it in Terraform with policy guardrails, and migrated workloads in waves with the client's platform team doing the later waves themselves.
Representative of the work; client details are not published.
Technologies
- Azure
- AWS
- Entra ID
- AWS IAM
- Azure Policy
- AWS Organizations
- Terraform
- Private Link
- ExpressRoute
- Direct Connect
Related solutions
Reduce cloud spend
Find what drives the bill across architecture, Kubernetes, storage, databases, builds and observability, then change it.
Migrate to cloud
Migration architecture, landing zones, networking, IAM, deployment patterns and a phased workload migration.
Adopt Infrastructure as Code
Move manually provisioned infrastructure into governed, testable Terraform workflows.
Multi-region and high-availability architecture
Improve availability across cloud regions and failure domains, with recovery you have rehearsed.
How we think about it
Migration · Cloud architecture · 7 min
Migration by disposition, not by lift
A cloud migration that treats every workload the same ends up moving the problems with the servers. How to classify an estate into dispositions, plan the waves, and keep the business running while the ground moves.
Cloud architecture · Security · 7 min
Landing zones before the first workload
The account structure, identity, network and guardrails that every later decision rests on. What a landing zone has to settle, what it can leave open, and the order that avoids rebuilding it in year two.
Terraform · Cloud architecture · 9 min
Adopting Terraform on a brownfield estate without breaking production
Importing an existing cloud estate into Terraform is a sequencing problem. The order that keeps production safe, and the mistakes that make people give up halfway.
Before you write to us
The questions we get asked first.
Answered the way we would on a call. The consulting FAQ covers how engagements work in general.
- Do we need a landing zone before anything else?
- Usually yes, and it is smaller than it sounds: the account or subscription boundaries, federated identity, the address plan and the guardrails. Those four are hard to change later; most other decisions can wait for the workloads.
- We already have an estate. Is this a rebuild?
- Rarely. An architecture review usually finds that the boundaries are missing rather than wrong, and the fix is drawing them, applying the guardrails to what exists, and moving workloads across one at a time, with the business running throughout.
- What access do you need?
- Read access to the cloud accounts or subscriptions, the network and identity configuration, and the infrastructure code, and a few hours of the team's time. Nothing is run under your production credentials from outside your own tooling, and write access only arrives with an implementation phase, through your pipeline and your review.
- What happens after the engagement?
- Everything is written down and handed over: the decisions, the code, the runbooks and the reasons. Your team runs it. Where a standing arrangement makes sense, a retainer or a few architect days a month keeps the context without keeping us on the payroll.