A large city already runs a multi-team Kubernetes platform with mature cluster operations skills and wants that model for newly migrated container workloads. Which hosting choice fits the organizational context?
Select an answer to reveal the explanation.
Short Explanation
If the city already has a Kubernetes pit crew, don't make them race go-karts. EKS fits when those skills and multi-team platform habits are real—not when you pretend Lambda is a stateful app server.
Full Explanation
EKS versus ECS (or other platforms) is an organizational-context decision. When Kubernetes skills and multi-team platform operations already exist, Amazon EKS aligns with that investment. Forcing Beanstalk-only, banning containers, or stretching Lambda as a long-running stateful app-server replacement ignores that context.