ECS deploy

[tabletcorry]

Basically, I tease the existing docker-compose file into three parts, for the major services that need to run in production. In order to function, the env files need to specify all the required variables in the new yaml files. I will document this.

This isn't perfect. An alternative solution would be to build the component compose files "on-the-fly" by parsing the base compose YAML. That may be the evolution of this change, but I wanted to prove out the basic ECS deployment.

Comments very welcome. I don't think this is merge-worth just yet, so I am interested in thoughts from the SM maintainers.

Changes:

• Add individual docker compose files for ECS Compose tooling
• Add script to deploy code to ECS
• Make all docker init scripts exit on failure (to prevent zombie containers)
• More env vars!

Todo:

• [ ] Document new vars required
• [ ] Add scripts to create ECS services

[coveralls]

Coverage decreased (-0.007%) to 72.427% when pulling 4a6408035f44c3a588d03456da6472db276dc4dd on tabletcorry:ecs_deploy into adfe60674df22fb52d51d9794820009dfdf6c20f on Netflix:develop.

[mikegrima]

Will be very interested in the docs.

[badllama]

I'm definitely looking into an ECS Fargate deployment. Any chance for further progress on this PR?

[ollytheninja]

I have Security Monkey running on ECS in prod based on this PR so I'll have a dig tomorrow and see if I made any major changes

[tabletcorry]

I never pursued the Fargate changes @badllama, as the ECS deployment was functional and cheaper.

@ollytheninja 🎉

[tabletcorry]

The only missing item is a script to create the ECS services/cluster. But I don't have the time to create that now.

@mikegrima I am fine with this being merged now, especially since it worked for @ollytheninja. But I leave it up to you.

[mikegrima]

Can you do me a favor and rebase it with the latest develop?