Amazon CloudFront

Serving images

Serving Videos

Serving static JS files

Dynamic content being served

Different content for different regions

Allowing running some code before serving content

Serving HLS Videos with CloudFron Signed Cookies

Serving Static content on the website

Helps to hide your S3 bucket url in public

Deliver files without any latency

Easy to get usage statistics and logs

Add settings to prevent access of any particular file type

Integration of CloudFront Signed Cookies is difficult can provide better documentation

Adding custom domain is tricky sometime because we have to create certificate first and region should be N. Virginia otherwise you will not see the certificate while attaching in CloudFront settings. I think there is need of improvement here.

Setting CloudFront for different file type, I find difficulty when I was integrating it

I guess CloudFront has all the features which any CDN should have. Only a better documentation is required. Currently it is really overwhelm.

Delivers our Content faster all over the Globe

Inbulit WAF

Inbulit Geography Restrictions

We can even stop the unnecassry requests

And Many ways to setup Cloudfront(CLI, CFT, Console)

Kinda of costlier when compared to rivals providing the same service

The setup of Distribution is kinda little complicated, need good exposure before setting up the service

Sometimes we can go with S3 Delivery service rather than Cloudfront if the website is providing static content and its way cheaper

Secure

easy to access

available all the time

add more function codes

improve the cache key normalization

provide the clear and detail guide for the way of use cloud front

Serves quickly

Easy setup

Fast load times

WordPress integration

Easier out of the box CDN solution

Built mainly for IT/server admins

Easy variation in server location selection

Extensive server and resource settings; highly configurable

Prices should fall a little more

Expenses and payments are not transparent

Configuration and customization could be easier with a better UI

Manage CDN properly

Fast and reliable

Distributed across the world

Improved way to serve existing content from S3 or other origins

Allows customization at edge locations

Skillset required for deployment (initial learning curve)

Need more examples of different usages and all the options available

The UI is not intuitive at all

Talking about just price, CloudFront is not the cheapest

It enables us to customize at the edge.

Deliver private content to our customers by using Lambda@Edge Customization's.

Cost of deploying solutions

Skillset required for deployment

Highly available content delivery.

Improved speed of content delivery to end users.

The token-based authentication is a little complicated to implement.

Allow you to create and manage your own CDN.

Improving performance of serving S3 content.

For new users, it could be easier to implement an initial stack.

Better tutorials on different configurations.

CloudFront, like other CDNs, is a very reliable content delivery network for delivering content like images, videos, HTML, and javascripts that are run on browsers across the world.

It provides secure hosting of content at no extra cost. AWS Certification Manager also provides the ability to create and manage custom SSL certificates at no extra cost for our websites.

It is secure, which means that it uses AWS Shield for Layer 3/4 DDoS mitigation and AWS WAF for Layer 7 protection. Hence seamlessly integrating with other AWS services. So you do not have to shop outside of AWS ecosystem

I cannot think of a lot of examples where CloudFront could be improved. One thing could be an enhanced integration with its CI/CD services like Code Deploy and Code Pipeline. Currently, we use Code Pipeline to build static content and push to S3 and then push to CloudFront.

Distribution - Easily deployed globally with proper configuration

Speed - No customers complain about delivery issues or slow loading

Delivery - we can rely on the service to stay up and deliver our assets

The UI is godawful. I would almost say you need to be technical to feel confident that you're not going to break something, which is an issue for us as not all of our graphics team can use it.

Reduces requests to S3

Easy integration into our platform

Easy scalability to add more servers

I'd like the ability to update a cached location by just appending an action to the end of the url to bust the cache. For example http://foo.bar/f9asjdf9jasdf90adfa/update

First-party integration with S3, EC2, ElasticBeanstalk, etc.

Generous free tier for organizations that are just starting to work with CDNs

Packaged into existing AWS ecosystem with consolidated billing, support, etc.

Incredibly solid and reliable service

If price is the main concern, CloudFront is not the cheapest-in-class by a wide margin

Some of the settings are not obvious to new users, and the management dashboards could use work

Lacks fine-grained access controls and statistical reports for usage

Integrates seamlessly with Amazon Web Service's asset storage solution (S3). If you've already committed to the AWS ecosystem, this synergism is one of the perks.

Easily allows for serving assets from custom domains.

Fine-grain control over caching logic and response headers. It's a simple, but very powerful interface.

It would be appreciated if there were more inline documentation regarding what some of the charts and menu options do. As this was my first time using a Content-Delivery Network, decreasing my need to do research elsewhere would be appreciated.

Solid CDN services, does what it says on the tin

Lots of configuration options, which allow for different setups and pricing strategies

Lambda@Edge integration allows for really quite complex behaviours to be executed in the cloud at the edge node itself. This means there are a huge amount of possibilities for shaping and altering traffic close to the viewer.

Simple integration to other AWS services (e.g. S3)

It isn't the cheapest option out there, nor is it the most simple to set up. The likes of CloudFlare may be a better choice for small / simple sites, especially if there isn't any need for other AWS services.

if a website’s static data are based in New York City, people in Boston will get the content faster than people in San Francisco or Tokyo. The farther away customers are from a company’s data center, the slower the website or application loads. This problem can be fixed with a content delivery network like Amazon CloudFront

When a visitor requests a file from your website, Amazon CloudFront automatically sends the request to a copy of the file at the nearest edge location. This results in faster download times.

You may have great hosting but it doesn’t have the capacity or scalability offered by Google, Microsoft or Yahoo. The better CDNs like Amazon CloudFront offer higher availability, lower network latency and lower packet loss.

Amazon CloudFront provides 24/7 email and phone support

Amazon CloudFront Free Tier allows you to free up to 50 GB of data transfer and 2,000,000 HTTP and HTTPS requests / month for one year.

Amazon CloudFront can improve the security of the files that are being delivered from edge locations.

Amazon CloudFront should increase the number of edge location around the world for high data availability

you will probably get better performance and price of Amazon CloudFront when you are hosting your web servers in EC2