Cloud solutions and infrastructure
I design and operate cloud estates on AWS, Microsoft Azure and Google Cloud, from a single landing zone to hybrid and multi-cloud environments that must not go down.
Questions this answers
A landing zone is a repeatable, governed foundation. New workloads inherit its identity, network and controls instead of rebuilding them.
Management hierarchy, accounts or subscriptions, policy and budgets.
Single sign-on, role design, privileged access, secrets and key management.
Hub-and-spoke or virtual WAN, private connectivity, DNS, ingress and egress control.
Separate production and non-production, standard templates and deployment pipelines.
Logging, monitoring, backup, security tooling and artifact registries.
Reference architectures and well-architected reviews for new and existing workloads.
Assessment, wave planning and cutover using rehost, replatform, refactor, retain or retire.
Terraform or native templates in version control, with pipelines that plan, review and apply.
Managed clusters, ingress, service networking, image pipelines and cluster upgrades.
Metrics, logs and traces, service-level objectives, alert routing and incident runbooks.
Backup, replication and failover designed to recovery targets, with scheduled tests.
Tagging, budgets, rightsizing and commitments, with spend reported by team and product.
Connectivity, identity and operations that span data centers and more than one provider.
Not every system needs multi-region failover. I set recovery time objective (RTO) and recovery point objective (RPO) with the business, then design to them and test.
Aims are starting points. Final targets are agreed per workload and confirmed in recovery tests.
Tell me what runs where today and what must never go down.