Scalability
Elastic Beanstalk auto-scaling absorbs traffic peaks.
The application needed to move onto AWS Elastic Beanstalk for API hosting, RDS for the database, S3 for frontend assets, and CloudFront as the CDN — across multiple availability zones, so a single zone going down would not take the application with it.
Deploy the application on Elastic Beanstalk, RDS, S3, and CloudFront, spread across two availability zones behind a load balancer.
API hosting
Runs the API with automated scaling, so deploys and capacity changes don't require manual server management.
Database
MySQL with automated backups and multi-AZ failover, so a database outage doesn't mean lost data.
Asset storage
Holds frontend assets — durable storage that scales without capacity planning.
CDN
Serves assets from edge locations close to each visitor, cutting load time.
Elastic Beanstalk auto-scaling absorbs traffic peaks.
RDS high availability with automated backups.
Serverless pieces keep idle cost down.
Elastic Beanstalk removes most day-to-day management.
The deployment now runs across two availability zones with automated backups and load balancing in place — a database or single-zone failure no longer takes the application down with it.
The audit is free and the findings are yours to keep. If an ongoing arrangement makes sense after that, the tiers are published.