When we first began evaluating solutions for managing containers, we knew very little about our options. We evaluated ECS, Fleet, and Kubernetes--eventually deciding to use Fleet. ECS had only just been released to general availability, and we were very unfamiliar with it. Kubernetes was significantly more complexity than we wanted to own. Ultimately, Fleet was the easiest option. Once we got to the double digits in services and had multiple developers launching and maintaining services, we found that Fleet was lacking in many ways, so we decided to reevaluate our options. Migrating to ECS allowed us to consolidate responsibility for managing containers in AWS--allowing us to focus on shipping features instead of building infrastructure tooling.
In this talk, we will explore the migration process, lessons learned, and what we plan to do to improve our internal developer experience for ECS.