And how we figured out it was not the right choice for us
TLDR: If you want multiple apps running separately in an EC2 instance, with some managed properties (Load balancer, health monitoring, etc). Elastic Beanstalk is NOT the way to go.At Remote Flags, I was in charge of setting up the infrastructure for a small service to facilitate demoing the main application to interested people.
As we're a small team, and budget is tight, I figured I would use a single "non-critical infrastructure" server; this would contain small tools that, if they went down, wouldn't impact the overall availability of our service.