Cloud Engineering

Context

A national Tier-1 logistics operator managing freight, warehousing, and last-mile delivery across a fleet-tracking and order management ecosystem, running a fragmented mix of on-premises data centres and two independently procured cloud environments following a prior corporate merger.

The Problem Statement

The merged environment had created duplicated infrastructure, inconsistent security baselines between the two cloud estates, and spiralling infrastructure costs from over-provisioned, always-on compute supporting seasonal freight volume spikes. Engineering teams lacked a single infrastructure-as-code standard, resulting in slow, error-prone environment builds and an inability to scale reliably during peak trading periods.

Approach

AIIDA ran a current-state architecture and cost-baseline assessment across both cloud estates, then designed a target-state multi-cloud architecture that preserved the operational strengths of each platform (compute-heavy workloads on one provider, data and analytics workloads on the other) rather than forcing an artificial single-cloud consolidation.

Technical Execution

A unified landing zone was built across AWS and Azure using Infrastructure-as-Code (Terraform), with standardised network segmentation, centralised identity federation, and consistent tagging for cost allocation by business unit. Auto-scaling groups and containerised workloads (Kubernetes) were introduced to handle seasonal freight volume spikes elastically, replacing static, always-on infrastructure. A FinOps practice was embedded with real-time cost dashboards and automated anomaly alerts.

Methodology

Migration was delivered in sequenced waves by business criticality, using an Agile squad model with dedicated migration, security, and FinOps workstreams, followed by a hypercare stabilisation phase at each wave boundary before proceeding to the next.