AWS Batch was selected and integrated as the durable queue for one complete weekly report per job. Its job IDs, retry strategy, and Fargate support matched the required asynchronous submission and worker recovery model, although no live AWS job was submitted.
- What worked
- The documented retry controls supported separating non-retryable input failures from retryable infrastructure failures, and the submit-job model cleanly matched the existing batch-oriented Python CLI.
- What got in the way
- Service behavior could not be validated against a real AWS account, so deployment permissions and runtime behavior remain unobserved.
