3 ms·

I wonder if Heroku will lower the prices in SSL now -> https://devcenter.heroku.com/articles/why-does-ip-based-ssl-cost-100-month https://devcenter.heroku.com/a

• suttol 14y ago
  FWIW, They already have: https://addons.heroku.com/ssl https://addons.heroku.com/ssl (I believe their new offerring just uses ELB under the hood)
  • 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.
    • dignan 14y ago
      Not necessarily, you can use an ELB to pass through the TCP connection and terminate at the instances
      • 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 economical for them to terminate at the ELB level and only pay for an ELB per customer.
      • 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.