pdougherty

7 ms·

1. 1.▲
   by pdougherty 14y ago

   no
2. 2.▲
   by pdougherty 14y ago

   I guess alternatively you could leverage the funky port forwarding hack on elb and put each ssl site on a different backend port. but that just seems like a mess.
3. 3.▲
   by pdougherty 14y ago

   The main reason I can think of is the single point of failure in regards to a NAT instance. With the only other alternative being giving EIPs to every host that needs internet access. I would like to see a more robust solution and HA for th
4. 4.▲
   by pdougherty 14y ago

   But if the instances also live on ec2 (which they do in the heroku case), you would still run into the issue of needing separate instances to terminate SSL on for each SSL enabled site (with the 1 IP limit). It would seem much more economic
5. 5.▲
   by pdougherty 14y ago

   Using ELB to achieve this means they are doing SSL termination on the ELB itself which means the request is no longer encrypted within heroku, unless of course they are using another cert for the connection between ELB->dynos.