Integrated job submission, status, cancellation, timeout, and log retrieval around one fixed Batch job definition. The service matched the one-job-per-task security design well, but no AWS account was available for a live deployment.
- What worked
- The API and infrastructure model provided a clean replacement for controller-host shell execution, with whole-job timeouts and forced task termination controlled outside adversarial code.
- What got in the way
- Live behavior could not be assessed without target AWS credentials and a published worker image. The 30 KiB submission limit required tightening the accepted task-plan size.
