4 ms·

Absolutely! You can decide not to use a front-end load balancer. We have one user using Convox to spin up large worker pools on AWS. We also have plans on our

by ddollar 11y ago

Absolutely! You can decide not to use a front-end load balancer. We have one user using Convox to spin up large worker pools on AWS. We also have plans on our roadmap to integrate with internal (inside the VPC only) ELBs for internal APIs and things of that nature.

sjtgraham 11y ago
> 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.
- ddollar 11y ago
  That's very kind of you to say :) Currently the EC2 instances in your Convox installation all have public IP addresses but this is currently being addressed https://github.com/convox/kernel/issues/92 https://github.com/convox/kernel/issues/92
- ejholmes 11y ago
  Hey! Creator of Empire here. The demo stack we provide isn't suitable for production use as you found out already. Empire can definitely be deployed in a production ready manor where you can have internal and external services, which is how we have it setup at Remind. The docs are a little lacking right now unfortunately, but we'll be improving this in the future. We actually have a production ready example stack using our stack provisioning tool called stacker: https://github.com/remind101/stacker/pull/43 https://github.com/remind101/stacker/pull/43.

4 ms·

Absolutely! You can decide not to use a front-end load balancer. We have one user using Convox to spin up large worker pools on AWS. We also have plans on our

by ddollar 11y ago

sjtgraham 11y ago
> 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.
- ddollar 11y ago
  That's very kind of you to say :) Currently the EC2 instances in your Convox installation all have public IP addresses but this is currently being addressed https://github.com/convox/kernel/issues/92 https://github.com/convox/kernel/issues/92
- ejholmes 11y ago
  Hey! Creator of Empire here. The demo stack we provide isn't suitable for production use as you found out already. Empire can definitely be deployed in a production ready manor where you can have internal and external services, which is how we have it setup at Remind. The docs are a little lacking right now unfortunately, but we'll be improving this in the future. We actually have a production ready example stack using our stack provisioning tool called stacker: https://github.com/remind101/stacker/pull/43 https://github.com/remind101/stacker/pull/43.