A health-department Java API needs a load-balanced, elastic web environment without the team wiring a custom Auto Scaling group and load balancer from scratch. Which service fits?

A health-department Java API that needs a load-balanced, elastic web environment without hand-wiring a custom Auto Scaling group and load balancer from scratch is a classic fit for AWS Elastic Beanstalk. Beanstalk can provision a load-balanced environment that includes capacity provisioning and scaling so the team deploys the application rather than assembling every listener, target group, and ASG policy manually. That managed elastic web compute path is the correct Task 3.2 selection when operational simplicity for a standard web tier is the requirement. Amazon Macie as the application runtime and autoscaler fails because Macie discovers and classifies sensitive data in AWS; it is not an application platform that runs or autoscales a Java API. AWS Backup plans to horizontally scale Java threads fail conceptually: Backup protects data with backup plans and vaults; it does not scale application compute or threads. Amazon VPC Peering as a substitute application platform fails because peering connects networks between VPCs; it does not host, load-balance, or elastically scale a health-department API. Exam caveat: Beanstalk reduces assembly work but you still choose instance types, environment configuration, and deployment policies; teams that need full infrastructure-as-code control may prefer explicit ALB plus ASG designs once requirements outgrow the platform abstraction. Operational check: create a load-balanced Beanstalk environment for the Java API, deploy a health check endpoint, generate load to confirm instances scale, and verify the environment’s load balancer distributes traffic before production cutover.