North America's largest home inspection company came to Armakuni for emergency infrastructure migration from shared AWS account, platform stabilization, DevOps foundation, and ongoing engineering POD support.
The challenge
Armakuni won the engagement within two days of contact, displacing a previous AWS partner who had stalled on the same brief. The client selected Armakuni for its Do-With delivery model and DevOps depth. A PoC SOW established the migration approach, a delivery SOW executed the full migration, and the relationship has expanded into an ongoing Flexible Engineering POD retainer.
Scale: Infrastructure supporting a Django-based application, ~600 GB PostgreSQL database, RabbitMQ, Redis, and S3 across EC2 instances; serving franchise inspection operations across North America.
What we built
Armakuni delivered emergency infrastructure migration from shared AWS account, platform stabilization, DevOps foundation, and ongoing engineering POD support. The engagement ran as three SOWs: PoC SOW (migration feasibility, ~3-4 weeks), Flexible Engineering POD Delivery SOW (full migration execution, effective 29 October 2025), Flexible Engineering POD January 2026 SOW (ongoing retainer, 80 hrs/month plus on-call support). AWS funded the work at $7,200.
The outcomes
6 measurable outcomes shipped across the engagement. The ones that moved the business the most:
Full infrastructure independence achieved within the eight-to-ten-week migration window. meaning P2P owns every layer of its production stack, controls its own security posture, and is no longer dependent on a third-party account for the platform that runs its business.
Data integrity validated at greater than 99.9% fidelity on the PostgreSQL migration. with checksum validation stored as auditable CSV reports giving P2P and its stakeholders documented proof that no data was lost or corrupted during the transition.
Cutover completed within a two-hour window with failback validated. meaning the migration approach eliminated the scenario P2P feared most: a cutover that could not be reversed if something went wrong on the other side.
Terraform-managed infrastructure in place for the first time in the environment's history. replacing hand-configured EC2, ALB, WAF, and security group settings with version-controlled code that can be audited, reproduced, and modified without fear of invisible configuration drift.
EC2-to-ECS migration path identified and planned, giving P2P a clear route to structural cost reduction once the platform is stable, with container-based compute. replacing individual EC2 instance management.
Ongoing POD engagement providing 80 hours per month of multi-discipline engineering capacity, covering the full stack from application development. and QA to CloudOps and data engineering, giving P2P the ability to accelerate product development without the overhead of individual recruitment.
Built on AWS
The production environment runs on 13 first-party AWS services. Delivered under our AWS DevOps Consulting Competency, Migration and Modernization Consulting Competency competencies.
What's next
EC2-to-ECS migration to reduce infrastructure cost. Continued POD engagement supporting product development and platform enhancement. Potential buildout of formal CI/CD pipeline.