We had so much trouble deploying on ECS. Everything from its unhelpful debug&#x2F;troubleshooting tools to its unhelpful log&#x2F;event messages (yes, thanks for letting me know that you tried running a task 10 times and it failed; or that you had I&#x2F;O issues pulling from the AWS Docker Registry) were road blocks that when we finally got it working it still needed a lot of tuning. Even getting images from the AWS Docker Registry to work on ECS was a piece of work, and required a custom IAM policy configuration for which they hid on the marketing page of the AWS Docker Registry FAQ. Did I mention the documentation was bad?<p>In the end, we just opted to use GCE Kubernetes&#x2F;GKE, a really developed and thought-out product. Aside from being open-source and portable, we are still kicking ourselves for having devoted so much time on ECS (which EC2 is more expensive than GCE too!). We only spent a few hours getting it setup compared to the few all nighters we spent tuning AWS.<p>Plus, when container pods died, Kubernetes would automatically spin up a new pod (this sometimes happened on ECS), and for bonus points, everything from standard  output&#x2F;error in a container went to Google&#x27;s Stackdriver logging service without configuration. Google&#x27;s docs were actually quite good; much better than the unhelpful AWS docs.