Design AWS Service Architecture

I’m revamping my stack and need a clear, production-ready architecture on AWS. The core of the design must revolve around EC2, S3, and Lambda, with EC2 instances configured for auto-scaling, load balancing, and reliable backup-and-recovery. I want every decision—from instance sizing and Auto Scaling Groups to S3 bucket policies and Lambda triggers—captured in a diagram and accompanying documentation so I can hand it straight to my DevOps team. Here’s how I picture the engagement working: • Architecture blueprint: a high-level diagram (Visio, Lucidchart, or Draw.io) that shows VPC layout, subnets, security groups, Auto Scaling Groups, Elastic Load Balancer, backup flow, S3 storage tiers, and Lambda integrations. • Implementation notes: brief, step-by-step guidance or Terraform/CloudFormation snippets that reflect the diagram. • Operations playbook: concise instructions covering scaling thresholds, backup scheduling, recovery testing, and Lambda deployment. I’ll be available to clarify requirements and review iterations quickly, but I expect you to drive best-practice decisions around security, cost optimisation, and fault tolerance. Once these three deliverables are complete and reviewed, the project is done.