Eric Holmes

@osterman it's still used and supported internally at Remind, however, it's reached a level of stability where there's not much active feature development at this point. Most of our efforts...

Ok, going to update with my findings so far, at the moment, this appears to be a bug/race with how CloudFormation handles cancellation of custom resources, and isn't directly related...

We have no immediate plans to add this ourselves, but I agree this would be a great addition as deploying a different Docker image would almost never be desirable (there's...

On a related note, it would be nice if Empire integrated with content trust in Docker, so that you could only deploy images that you explicitly trust.

Once the work going into the extended Procfile completes, I'd imagine it would be easy for us to add support for this. But this will also depend on support in...

@louy yep, although, I think --read-only is already supported in ECS.

I think service discovery would be pretty cool to support. This is entirely possible by using the [DescribeTasks](http://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeTasks.html) api. It'll return information about the containers, including host port. We'd probably...

Hi @mwilliamson-healx. We have http://empire.readthedocs.io/en/latest/production_best_practices/, https://github.com/remind101/stacker_blueprints/tree/master/stacker_blueprints/empire and you can use the [demo cloudformation stack](https://github.com/remind101/empire/blob/master/docs/cloudformation.json) as a reference. All of these are really just guidelines for putting Empire into production, since...

Also, streaming the ECS service events while waiting for services to stabilize would be pretty handy to reveal scheduling problems.

I think I've run into this before as well. The problem was because I accidentally deleted the default subnets that a new AWS account creates by default. From http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/default-vpc.html#deleting-default-vpc >...