Waymark & Cairn

Cloud solutions and infrastructure

Cloud infrastructure built to run, recover and scale

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

  • Is our cloud foundation secure and consistent?
  • What happens when a zone or region fails?
  • Why is our cloud bill rising?

The landing zone every workload starts from

A landing zone is a repeatable, governed foundation. New workloads inherit its identity, network and controls instead of rebuilding them.

Organization and governance

Management hierarchy, accounts or subscriptions, policy and budgets.

Identity and access

Single sign-on, role design, privileged access, secrets and key management.

Network

Hub-and-spoke or virtual WAN, private connectivity, DNS, ingress and egress control.

Workload environments

Separate production and non-production, standard templates and deployment pipelines.

Shared services

Logging, monitoring, backup, security tooling and artifact registries.

Cloud capabilities

Cloud design

Reference architectures and well-architected reviews for new and existing workloads.

Migration

Assessment, wave planning and cutover using rehost, replatform, refactor, retain or retire.

Infrastructure as code

Terraform or native templates in version control, with pipelines that plan, review and apply.

Containers and Kubernetes

Managed clusters, ingress, service networking, image pipelines and cluster upgrades.

Observability and SRE

Metrics, logs and traces, service-level objectives, alert routing and incident runbooks.

Disaster recovery

Backup, replication and failover designed to recovery targets, with scheduled tests.

Cost management

Tagging, budgets, rightsizing and commitments, with spend reported by team and product.

Hybrid and multi-cloud

Connectivity, identity and operations that span data centers and more than one provider.

Resilience matched to what each workload is worth

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.

Tier
Typical pattern
Design aim
Tier 1 · Critical
Active-active across zones or regions
RTO in minutes, RPO close to zero
Tier 2 · Important
Warm standby in a second region
RTO in hours, RPO in minutes
Tier 3 · Standard
Backup and restore, rebuilt from code
RTO within a day, RPO within hours

Aims are starting points. Final targets are agreed per workload and confirmed in recovery tests.

Build or rescue a cloud estate

Tell me what runs where today and what must never go down.

Book a discovery call