A county assessor runs nightly parcel GIS batch jobs that need managed provisioning of compute for containerized or AMI-based workers. Which service best fits this large-scale batch pattern?

Nightly parcel GIS batch jobs need queued work, provisioned workers, and teardown without the assessor babysitting an ad-hoc EC2 farm. AWS Batch with managed compute environments provisions the underlying compute for containerized or AMI-based jobs, runs the queue, and fits large-scale batch patterns under Task 3.2. That managed batch orchestration is why AWS Batch is the correct service for the county assessor’s nightly GIS crunch. Amazon Cognito user pools fail as a scheduler for parcel workers because Cognito provides authentication and user directory features, not batch job queues or compute provisioning. AWS Certificate Manager fails conceptually because ACM issues and manages TLS certificates; it does not orchestrate job queues or GIS workers. Amazon CloudWatch Alarms alone fail as the job scheduler and executor because alarms can signal conditions but do not replace a batch compute service that submits, runs, and scales GIS jobs. Exam caveat: Batch still requires container images or AMIs, IAM roles, VPC networking for data access, and retry/DLQ strategy for failed parcel jobs; managed compute does not eliminate data dependency design. Operational check: define a Batch job queue and managed compute environment, submit a representative GIS job, confirm workers reach parcel data stores, and monitor success/failure metrics before promoting the nightly schedule.