Hospitality & FinTech
Automated Tip Management Platform
Tip Sheet
Read case study
All Case Studies
Finance & SaaS
AWS Cloud Architecture Optimization
InstaBooks
Timeline
1.5 mo
Team
1
Launch
Q1 2022
Overview
The Challenge
InstaBooks operates a multi-site WordPress bookkeeping application serving users across multiple geographic regions. The existing AWS infrastructure was provisioned manually, lacked auto-scaling, and suffered from inconsistent performance during traffic spikes. Static assets were served directly from EC2 instances, creating unnecessary load and latency.
The platform needed geographic redirection -- users in Australia should hit Australian servers, users in the US should hit US-based infrastructure -- but this had been implemented at the application layer rather than the network edge, adding complexity and latency to every request.
The brief was focused: bring in a single senior architect for a rapid engagement to audit the current infrastructure, design a production-grade architecture, and implement the changes. No team ramp-up, no multi-month timeline. Just clean, surgical infrastructure work.
Solution
What We Built
The architecture was redesigned around AWS best practices for high-availability WordPress deployments. EC2 instances were placed behind an Elastic Load Balancer with Auto Scaling groups configured for CPU and memory thresholds, ensuring the platform scales horizontally under load and contracts during quiet periods.
The database layer was migrated to Amazon RDS for MySQL with Multi-AZ deployment for automatic failover. Static assets and media uploads were offloaded to S3, served globally through CloudFront's edge network. EFS provides shared filesystem access across all EC2 instances for WordPress core files and plugins.
Route53 with geolocation routing policies replaced the application-level geographic redirection, directing users to the nearest regional deployment at the DNS layer. CloudWatch dashboards and alarms provide operational visibility, with automated alerts for cost anomalies, performance degradation, and scaling events.
Tech Stack
WordPressAWS EC2AutoscalingELBRDS/MySQLCloudFrontS3EFSCloudWatchRoute53
Key Results
Measurable outcomes
01
Auto-Scaling Infrastructure
EC2 instances scale automatically based on demand. No more manual intervention during traffic spikes or over-provisioning during quiet periods.
02
Edge-Level Geo Routing
Route53 geolocation policies direct users to their nearest regional deployment at the DNS layer, eliminating application-level redirects.
03
Global CDN Delivery
Static assets and media served through CloudFront edge locations worldwide, dramatically reducing page load times for all users.
04
Database High Availability
RDS Multi-AZ deployment with automatic failover ensures the database remains available even during infrastructure failures.
05
Cost Optimization
Right-sized instances with auto-scaling reduced monthly infrastructure costs while improving performance and reliability.
06
Operational Visibility
CloudWatch dashboards and automated alerts provide real-time insight into infrastructure health, costs, and performance.