Re:Global Outage of AWS CloudFront CDN on Nov 26 2014
by ceejayoz on Thursday November 27, 2014 @12:56PM
(#8668246)
Yes. Instead of using pqowieurpqoiwer.cloudfront.net, you can point one of your own subdomains at it. Leaves you in control. The only complexity is SSL certificates - you either have to pay $600/month for a custom cert, or use SNI and ditch some older IEs.
[ Parent
| on HN ]
Re:Global Outage of AWS CloudFront CDN on Nov 26 2014
by Xorlev on Thursday November 27, 2014 @01:44PM
(#8668411)
They do offer free SSL with SNI. But that's not viable for most people given the number of popular older browsers missing SNI support.
Re:Global Outage of AWS CloudFront CDN on Nov 26 2014
by kbuck on Thursday November 27, 2014 @02:07PM
(#8668475)
Browsers that do support SNI include:
IE7+ (unless running on Windows XP)
Firefox 2.0 and later
Opera 8.0 and later
Chrome 6 and later (unless running on Windows XP)
Safari 3.0 and later
Android default browser on Android 3.0 and later (this is probably the biggest chunk of users)
Windows Phone 7
So, realistically, you're looking at people who still use Windows XP (unless they're using Firefox) and people with really old Android phones that'll never receive a manufacturer firmware update.
Re:Global Outage of AWS CloudFront CDN on Nov 26 2014
by micro-ram on Thursday November 27, 2014 @01:35PM
(#8668370)
Could you add a global variable to your site code with the fqdn of your assets to point to the origin for times like this?
Re:Global Outage of AWS CloudFront CDN on Nov 26 2014
by sbarre on Thursday November 27, 2014 @01:15PM
(#8668317)
$600 per month for what exactly? (honestly asking here)