adamtait/capify-ec2 — comment on commit 9aeca59e754125974f0cf4dabb33087bfc938132
File:  line 0
By adamtait:

Thanks Noah! I haven't checked back to the upstream basically since I forked it, and there have been some welcome improvements. My updates simply only helped recognize instances by a secondary tag ['ENVIRONMENT'] to differentiate between sets of machines. It was a quick fix, and it's possible that I could have replaced it with the :project_tag - but would require many ec2.yml-s.
I think that the better solution is to coordinate with capistrano/ext/multistage and add an :ec2_project_tag into the capistrano env-specific deploy script.

There's a good chance I'll be expanding further as we move more of our dev & prod environments onto EC2. There will definitely be a change required to by-pass instances on subnets lacking internet gateway access.
Will keep you in the loop :)