6 ms·
It's not an issue with multiple IP addresses, but rather with being able to host multiple SSL-enabled domains on a single IP (which is what CDNs need to do). Th
by anderiv 13y ago
It's not an issue with multiple IP addresses, but rather with being able to host multiple SSL-enabled domains on a single IP (which is what CDNs need to do). That is where SNI[1] comes in, along with all of its compatibility issues with older network stacks.
[1] http://en.wikipedia.org/wiki/Server_Name_Indication http://en.wikipedia.org/wiki/Server_Name_Indication
- justincormack 13y agoSo IPv6 would not be an issue then, I gues, every client could have an IP on each edge node...
- anderiv 13y agoYes, that is a possibility. SNI will also become a more realistic option as older devices get retired. I've implemented several sites with SNI, and as long as you're aware of what devices/browsers/OSes will be connecting to your site (and their SNI support), things work great.
- pgrote 13y agoSo why is it so expensive?
- anderiv 13y agoWhat is what so expensive?
- eli 13y agoWhy is it so expensive to add SSL with a custom domain to Amazon CloudFront? Because Amazon actually needs to acquire hundreds of individual certificates on your behalf and distribute them to its edge servers.
- Kudos 13y agoNo they don't, you provide them with a single cert and they use that on every edge node.
- chris 13y agoSSL requires additional CPU resources, and is often coupled with hardware acceleration. All of this equates to higher hosting costs.