Instantly helps achieve scalability to deliver millions of videos, images and other static content without setting up your own content network or buying into expensive solutions. Cloudfront's edge delivery capabilities makes the entire content experience super fast for all clients. Encryption and storage management comes out of the box with right infrastructure and cloud setup.

Cloudfront can use better, simpler documentation. It's also missing more out of the box solutions, for ex. how to setup and a on-demand-video delivery setup or templates for its cloud deployment. There are templates available in AWS China but no within US, it's missing english documentation. With SDK, there can be more default integrations with established CMS systems like JamStack to simplify development experience.

Most of my usage of CloudFront was coupled with AWS CloudFormation. This meant I was able to quickly use sample stacks to deploy and test my infrastructure. I was also able to use the same stack to deploy to multiple environments (dev, staging, production).

Easy to use, fast, reliable, cheap. CloudFront is a great CDN for static websites and media. It's easy to use and configure. It's fast and reliable. It's also cheap. I have used it for a few years and I only had minor issues with it. It makes serving static (cache-able) content very easy. It's also very easy to integrate with other AWS services such as S3, Route53, and Lambda Edge to customize the behavior of the CDN. Security best practices are builtin and usage with AWS IAC tool (CloudFormation) was a delight. I would recommend it to anyone who wants to serve static content from AWS.

CloudFront itself is a global service, however, Lambda Edge which integrates with CloudFront can only be deployed on a specific AWS region (North Virginia). This means you will be forced to deploy parts of your infrastructure in that region. This is not always (allowed) by certain companies policies.

It's okay. It often looks like the grass is greener for companies and products who focus specifically on CDN services, but in general it's nice to work within one ecosystem.

With CloudFront we were able to correct incorrect response headers from sources such as s3 buckets, api gateways, and lambdas that were returning valid results but invalid response headers. This helped us fix some SEO issues. Additionally since it is a CDN it helps deliver our content faster and more reliably.

This software can make debugging more difficult. In general I do not like how AWS handles logging. I also dislike that other AWS services initially returned errors that necessitated the use of a CloudFront to correct incorrect headers.

We need a CDN to deliver large and static files and execute some logic before send the response. The logic is contained inside a Lambda function which calculate the resource to send back to the requester using a mapping file.

You pay only bandwith costs, so it's really unexpensive for us. Statistics are really usefull and quite complete. Integration with Lambda is a really powerfull tool to execute complicated logic before sending a response.

Setting up can be a quite difficult and the documentation is not really clear sometime.

Seamless and scalable setup for bringing lambda functions to the edge.

As with other AWS services - the UI feels a bit convoluted and requires some time getting used to.

A great infrastructure and a platform with great performance that can definitely be improved in terms of accessibility and overall customer support

I love their network and the functionality they have to offer great service, the performance has never let me down and I must say they are one of the top providers in the category.

It's not easy to set up at all. There are so many pitfalls while settings things up that a small mistake can set you back by hours of your time. A very dated interface for their platform leaves you guessing most of the time on how to achieve simple things. Be ready for a ton of tech jargon that you are definitely not going to understand if you are new to this. Customer support for some plans is non-existent and for other plans, it is not so accessible. The pricing is not so transparent as it at times it can leave you guessing what the actual price you would be charged after adding up everything.

1) Easy to implement for a WordPress blog. 2) Good speed. 3) Ample of features. 4) Easy to integrate with other AWS products. 5) More than 200 points of presence across the globe. 6) AWS Shield Standard is available to all customers at not additional cost and is always on to protect your Amazon infra from Layer 3 and 4 attacks. 7) Discounts are available when you commit to minimum 10TB/month. 8) Save costs by selecting Amazon Price Class 200 which serves content from all locations except South America and Australia instead of Price Class All which serves from all location globally. Price Class 100 is the cheapest among all as it serves content only from US and Europe. 9) Regional caches so less requests to origin. 10) Restrict access to authenticated people with Token Authentication. 11) With Geo Restriction prevent people in certain regions to access your content. 12) Origin Shield creates a cache copy at a central location which saves your server during traffic spikes. 13) If one origin fails another can be enabled.

1) Little pricy but one gets good performance. 2) Customer support not for all. Pay extra. 3) Complicated pricing. 4) Pay extra for Amazon Shield Advanced. 5) Pay extra for Web Application Firewall.

For what it's supposed to do, it's a good product. This is more an indictment of me, but some of the language and concepts feel overly industry-specific and technical.

Strictly as a matter of opinion, I most appreciate the more fine-grained controls I can put on my S3 bucket exposure. Instead of just making the bucket public, I can allow CloudFront to peek in.

To me, there's been a steep learning curve. I still don't feel confident about a lot of the language/relevant vocabulary (e.g. "invalidations"). It doesn't feel like many of the concepts have been abstracted out to the same degree as some other AWS services.

Fantastic!

I thoroughly enjoyed working with CloudFront. It was used in order to shorten the delivery time of static content in our web application (Video, Images). By using CloudFront we managed to decrease the delivery time via network by more than 300%. It is very easy to configure and does not many maintenance processes.

To be honest, I did not find cons about this Software - the only disadvantage are raising costs when used intensely, but this is the case with all of the CDN providers (Akamai, CloudFlare, Google CDN, Azure CDN).

It's very easy to start to use the CDN service once you host your website on Amazon

You will need a specialist to manage it, it's not user friendly at all.