Architecture
Choose AWS services and deployment patterns around the workload’s real availability, scalability and security requirements.
AWS Case Study · EV Mobility / Fleet Technology
Cross-region disaster recovery for a 24/7 EV platform.
DriveTerra operates an EV battery-swapping platform serving riders and fleet operators across the UAE. Because real-time station availability directly supports deliveries and fleet SLAs, the platform needed a tested recovery path outside the primary UAE Region.
The challenge
What had to change.
The platform runs five microservices on Amazon EKS with PostgreSQL and IoT-related data. A regional disruption could halt rider operations, so DriveTerra needed a geographically separated DR target with pre-positioned artifacts, backups, infrastructure definitions and DNS failover procedures.
Our solution
How Ghaim approached it.
Ghaim designed and operated a backup-and-restore DR architecture from me-central-1 (UAE) to ap-south-1 (Mumbai) and executed the recovery during the March 2026 incident.
- Ran Amazon EKS across two Availability Zones with autoscaling and least-privilege service identities.
- Used RDS PostgreSQL Multi-AZ in the primary Region and cross-region backup copies for recovery.
- Replicated S3 data and ECR container images to the DR Region.
- Defined the DR network and cluster environment with CloudFormation and CDK.
- Used Route 53 health checks and pre-staged DNS failover.
- After the incident, increased backup frequency and pre-warmed the DR EKS node group to improve future recovery time.
4 hoursIncident recovery execution
< 1 hourImproved RPO after hardening
15m 20sSubsequent DR drill RTO
AWS services used
What this demonstrates
AWS architecture tied to operating outcomes.
Each case study reflects the same Ghaim approach: secure foundations, automation, resilience, cost awareness and a clear operating model after deployment.
Automation
Use Infrastructure as Code and CI/CD to reduce manual operational risk and make changes repeatable.
Operations
Design monitoring, recovery and ongoing optimization into the platform instead of adding them after go-live.
Related expertise
Explore the capabilities behind this work.
Your AWS workload
Need the same level of architecture and execution?
Tell us your current environment, constraints and target outcome. We will map the right AWS approach.