AWS cloudfront grows upâ€¦ a little. Now allows Custom origins.
- First, we've removed the beta tag from CloudFront and it is now in full production. During the beta period we listened to our customers and added a number of important features including Invalidation, a default root object, HTTPS access, private content, streamed content, private streamed content,AWS Management Console support, request logging, and additional edge locations. We've also reduced our prices.
- There's now an SLA (Service Level Agreement) for CloudFront. If availability of your content drops below 99.9% in any given month, you can apply for a service credit equal to 10% of your monthly bill. If the availability drops below 99% you can apply for a service credit equal to 25% of your monthly bill.
While all this is a big step forward, its probably not enough for the more advanced CDN users to switch over yet.
Here are a couple of issues which stuck out in the Developer Guide.
- Query parameters are not used to generate cache key. So while it looks like it can pull content from an elastic loadbalancer, it still acts like a giant S3 accelerator.
- Doesnâ€™t support HTTP/1.1 yet. So if you have multiple domains on the same IP, this solution isnâ€™t for you.