Can Convox do non-internet-facing services? i.e. private internal services not routable from outside the VPC?
We also have plans on our roadmap to integrate with internal (inside the VPC only) ELBs for internal APIs and things of that nature.
This is what I'm getting at. Also just saw the issue pertaining to HIPAA, which probably requires the same thing.
Apps deployed on Empire apparently are only available inside the VPC unless a domain name is added, it doesn't actually work like that (when I deployed the Empire stack all boxes had public IPs and a security group allowing ingress from the internet 馃槗), but the idea is a good one I think.
Oh, and thanks. Knowing you're behind it I'm sure Convox will be great. I'm looking forward to watching it develop and using it myself.
We actually have a production ready example stack using our stack provisioning tool called stacker: https://github.com/remind101/stacker/pull/43.
Currently the EC2 instances in your Convox installation all have public IP addresses but this is currently being addressed