A delivery company will migrate a third-party route-planning app to AWS. The vendor supplies a supported Docker image from a public registry. The image can scale to many containers and each delivery-area section runs its own set of containers with a custom configuration to process only that section's orders. The company needs to allocate resources cost-effectively based on running container count and minimize operational overhead. Which solution meets these requirements with the least operational burden?

The correct answer is to create an Amazon ECS cluster on AWS Fargate and use the AWS CLI run-task command with enableECSManagedTags set to true, along with --tags to assign a custom tag. This solution leverages AWS Fargate for serverless container execution, minimizing operational overhead by eliminating the need to manage EC2 instances. ECS is a good fit for Docker images and provides cost-effective scaling. enableECSManagedTags automatically propagates tags to underlying resources, simplifying cost allocation. The --tags option allows for custom tagging per delivery-area section, which is crucial for cost-effective resource allocation based on specific configurations. Incorrect options: EKS on EC2 involves managing EC2 instances, increasing operational overhead. Tagging pods directly via EKS CLI --tags is not a standard or effective method for cost allocation across underlying AWS resources. EKS on Fargate reduces operational overhead, but the EKS CLI --tags option for pods does not propagate tags to Fargate tasks for cost allocation. ECS on EC2 requires managing EC2 instances, increasing operational overhead. While --tags can be used, the underlying infrastructure management negates the "least operational burden" requirement compared to Fargate.