A developer packaged a small application (requires minimal CPU and memory) as a container image. The app fetches data from an external API, processes it, and writes results to S3. The application must run once every hour in an existing Amazon ECS cluster. Which option minimizes infrastructure management overhead?

Creating an ECS task definition with the AWS Fargate launch type minimizes infrastructure management overhead because Fargate is a serverless compute engine for containers. You don't need to provision, patch, or scale servers; AWS manages the underlying EC2 instances. For an hourly, small application, this is ideal as you pay only for the compute resources consumed during execution. Adding a capacity provider or managed node groups still requires managing EC2 instances, increasing overhead. Launching a standalone EC2 instance for a small, hourly task is inefficient and requires significant manual management.