Live data from Hacker News

Ask HN: Why don't we see more HTTPS? Is CPU an issue?

news.ycombinator.com

31–32 of 32 posts

Re: Ask HN: Why don't we see more HTTPS? Is CPU an issue?

#31
post #17
post #11

Earlier quoted context omitted.

Huh? There is no cost for an elastic IP address when it is in use.

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 .

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.

Re: Ask HN: Why don't we see more HTTPS? Is CPU an issue?

#32
post #10

I don't support more HTTPS because of the cost of static IPs on EC2 (i.e. ~72/mo)

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 )

Yeah, I know, but you can only attach one per instance, so the effective cost per elastic ip per month is 1 small instance.
Post reply on HN