second on beanstalk/docker - beanstalk does simplify quite a bit about running a fleet of docker images (and non-docker stuff too), uses standard aws tools (cf, elb, rds, ecs, vpc), has zero downtime deployment built in, automated server upgrades, app monitoring, environment cloning etc...

one nick against beanstalk is that it could be faster doing all those things, but it's tolerable considering alternatives.

Terraform + any old CI + Elastic Beanstalk works wonderfully for deploying docker apps on AWS.

What does beanstalk do exactly? I stopped using it once I needed multi-container deployments but I know that's supported now.

No, elastic beanstalk is terrible.

Works great for us so far. Care to elaborate?

I've been using Elastic Beanstalk for some time now and while I find it quite useful for people who just want to get Docker to production without investing to much time into Orchestration, it looks to me like there is a bit of price to pay for that 'simplicity':

   - Elastic Beanstalk does not provide a native Docker experience. You're forced to use AWS own way of defining services and dependencies (Dockerrurn.aws.json, which comes in two versions). This means you cannot longer use docker-compose, and not all of the options from `docker run` are available (logging driver,  privileged containers, though I think the ability to run privileged containers was recently added).
    - From my personal experience deployment times can be unacceptable long ranging from 5 - 20 mins. They get longer as you add more instances to the environment or if the instances are not powerful enough.

I think Elastic Beanstalk makes a good choice for starters or for not so mission-critical applications.

As a result of the points explained above I'm now looking into more Docker-centric solutions such Rancher/Kubernete or Docker's UCP.