News for hackers. Stuff that matters.
Re:Ask HN: Why don't we see more HTTPS? Is CPU an issue? by izak30 on Thursday September 10, 2009 @03:31PM (#815993)
I don't support more HTTPS because of the cost of static IPs on EC2 (i.e. ~72/mo)
Re:Ask HN: Why don't we see more HTTPS? Is CPU an issue? by astrodust on Thursday September 10, 2009 @03:36PM (#816011)
Elastic IPs are $7/mo. only if they are unused. They cost nothing if attached to a running EC2 instance.

See: (http://aws.amazon.com/ec2/#pricing)

Re:Ask HN: Why don't we see more HTTPS? Is CPU an issue? by izak30 on Thursday September 17, 2009 @09:47PM (#829452)
Yeah, I know, but you can only attach one per instance, so the effective cost per elastic ip per month is 1 small instance.
Re:Ask HN: Why don't we see more HTTPS? Is CPU an issue? by gduffy on Thursday September 10, 2009 @03:36PM (#816008)
Huh? There is no cost for an elastic IP address when it is in use.
Re:Ask HN: Why don't we see more HTTPS? Is CPU an issue? by wmf on Thursday September 10, 2009 @03:57PM (#816053)
But there is a cost for running a separate instance for every IP since Amazon won't let you assign more than one address per instance.
Re:Ask HN: Why don't we see more HTTPS? Is CPU an issue? by izak30 on Thursday September 17, 2009 @09:47PM (#829448)
Thanks! I did lose points for this w/o clarifying..

I run multiple sites on a single instance (we're a webhost) We don't do shopping carts/ssl for our clients, because that would cost 1 - Small Instance/month, which is cost-prohibitive for them.

We are using the 1 static IP for our own SSL certificate.