TrustRadius: an HG Insights company
Amazon CloudFront Logo

Amazon CloudFront Reviews and Ratings

Rating: 7.9 out of 10
Score
7.9 out of 10

Reviews

17 Reviews

My 2 Years Experience with CloudFront

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

We use Amazon CloudFront to serve static media content like (images & videos) to users. We wanted a solution to serve static content without latency and AWS CloudFront addressed this problem. CloudFront also helps to deliver HLS videos to users. With CloudFront, we can sign the URL and server to users with this feature URL gets expired after a certain time and if someone embedded our content then it would be inaccessible. If you want to serve HLS videos then I suggest using signed cookies instead of signed URL. With signed cookies, we do not need to append an authentication token on each URL and it gets authenticated through cookies that pass on each network call.

Pros

  • 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

Cons

  • 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.

Likelihood to Recommend

Amazon CloudFront is the perfect solution for any type of company. If a company is small or medium size, CloudFront offers 1 TB monthly free bandwidth which is more than for any small and medium size companies. If we compare the speed of CloudFront with other CDN, CloudFront is way ahead of their competitors and with 1 TB free bandwidth. If someone is ready to invest time in CloudFront documentation then he/she definitely go for it.

AWS Cloudfront review from Experience Certified Solutions Architect

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

The main reason we use Cloudfront is to serve our Global Customers in a significantly faster manner. This happens through the concept called edge locations. Our static data will be present in edge locations distributed across the globe. Using this our customers will be able to interact with our website faster. Also, this improves our Customer experience as well. Also, it has inbuilt WAF(Firewall) and we can even restrict to which geography locations we need to serve our website.

Pros

  • 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)

Cons

  • 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

Likelihood to Recommend

Cloudfront is an excellent service when you have a website and its customers are globally distributed and you need to give them the best customer experience by providing the content in a reliable and faster manner. Also, Cloudfront distributes from more than 200 edge locations and to note it has the largest number of edge locations among its competitor on a big scale. And includes WAF and can interact with the authorization technique.

Amazon CloudFront is the optimal cloud solution

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

I used Amazon CloudFront in my organization to ensure to distribute my service to many users and to make sure my service is always secure. We faced many different technical challenges the most of them is the access issues with most of our users and clients. We trying to keep up always and let our users and clients happy with our service.

Pros

  • Secure
  • easy to access
  • available all the time

Cons

  • add more function codes
  • improve the cache key normalization
  • provide the clear and detail guide for the way of use cloud front

Likelihood to Recommend

It's easy to distribute your services with a secure channel, As I mentioned in the beginning we are trying to find a way to deliver our services to the users and clients. It's improving and making our business in the top of other competitors. We so satisfied with Amazon CloudFront's solution

A reliable workhorse which is essential for anyone who cares for good end user experience

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

It is used to deliver images on the website so that they load really fast for our users and the end user experience is optimized.

Pros

  • Serving images
  • Serving Videos
  • Serving static JS files

Cons

  • Dynamic content being served
  • Different content for different regions
  • Allowing running some code before serving content

Likelihood to Recommend

It is really well suited when you want to serve some static content really fast and in an optimized way.

It is not as good for something where you need to modify the content before it is served. You then need to use something like Lambda on the edge. While some competitors have made it simpler.

Vetted Review
Amazon CloudFront
10 years of experience

Best value for such quick load times

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

We use CloudFront to host our assets and digital media in order to speed up webpage load times. It allows us to use higher quality images and full 4K video without suffering massive load times. It is used in our Marketing department and solves the issues we have with needing to show off high-quality media.

Pros

  • Serves quickly
  • Easy setup
  • Fast load times

Cons

  • Wordpress integration
  • Easier out of the box CDN solution
  • Built mainly for IT/server admins

Likelihood to Recommend

CloudFront is well suited for websites that use a lot of digital media and assets like photos, videos, PDFs, and other downloads. It is less appropriate for anyone looking for a ready-made solution for websites and marketing as it offers a high level of customization and is very easy to implement into custom setups.

Vetted Review
Amazon CloudFront
2 years of experience

Great cloud experience; safe and fast deployment

Rating: 9 out of 10

Use Cases and Deployment Scope

The resources we need are available to us at any time and we activate them on the server and pay according to the amount of consumption. Amazon CloudFront is a professional CDN. Amazon servers have relieved us of the worry of being disconnected or overloaded. All this is accessible with just a few clicks and you have access to all the features of the server. Server management has never been this fast and easy. You will definitely need it for big and complicated projects.

Pros

  • Easy variation in server location selection
  • Extensive server and resource settings; highly configurable

Cons

  • Prices should fall a little more
  • Expenses and payments are not transparent
  • Configuration and customization could be easier with a better UI

Likelihood to Recommend

<ul><li>There is no need to worry about security and server updates, and you are always up to date. More reliable than other CDN competitors in market. High speed servers, accessible support team, great features, and many different server locations. </li><li>For startup projects, you can easily control the server resources required by each project.

</li></ul>

Speed up static content delivery using AWS edge locations

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

We use Amazon CloudFront to distribute and speed up the delivery of our static content (audio and image) to end-users across the world. Technically we use it for hosting website content (CSS, JS, Images) and speeding up content delivery from S3 and other origins with different behaviors.

Pros

  • 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

Cons

  • 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

Likelihood to Recommend

Well suited to start with a CDN within the AWS infrastructure, hosting static contents for web sites, and managing custom SSL certificates.

My experience using CloudFront

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

We currently deploy Amazon CloudFront, and it enables us to speed up the delivery of our static content such as images, style sheets, JavaScript, etc. to our clients across the world. We take advantage of the Amazon web server's backbone network using Amazon CloudFront to give our customers a fast, safe, and reliable experience when they visit our website.

Pros

  • It enables us to customize at the edge.
  • Deliver private content to our customers by using Lambda@Edge Customization's.

Cons

  • Cost of deploying solutions
  • Skillset required for deployment

Likelihood to Recommend

Amazon CloudFront is well suited for accelerated static web content delivery.

AWS CloudFront: Quick Way To Get A CDN. Great If You're Already Using AWS Services.

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

Cloudfront is being used to distribute audio and image content to end-users. The end users are medical professionals relying on the content as part of a subscription service to maintain their career skills. To keep the content private and accessible to subscribers only, we implemented token-based security between CloudFront and our web servers.

Pros

  • Highly available content delivery.
  • Improved speed of content delivery to end users.

Cons

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

Likelihood to Recommend

If your content is vital to the product you sell, or if your content IS what you sell, then you need some kind of content delivery network service. You get redundancy at many levels, protecting you from outages. The speed of access to your content for your customers is improved and stabilized. You don't have to pay for all the hardware and technicians to get the infrastructure set up, which is a huge benefit. AWS tech support is very good in case you need assistance in setting up your CloudFront CDN. The best use for CloudFront is also as part of a 100% AWS-based infrastructure. AWS's services all work well together, but sometimes have issues with outside integration. If your content is not a big piece of your money-making operation, you can probably get away with something simpler.

Vetted Review
Amazon CloudFront
4 years of experience

If you need a CDN and already use AWS, then Amazon CloudFront is a no brainier...

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

We've used Amazon CloudFront as a Content Delivery Network (CDN) to increase the availability of resources across multiple geographic regions while minimizing our need for EC2 instances to deliver such content. From a simple form of hosting website content (CSS, JS, Images) along with building products to utilize Amazon CloudFront as a more friendly manner to serve content within S3 and other origins.

Pros

  • Allow you to create and manage your own CDN.
  • Improving performance of serving S3 content.

Cons

  • For new users, it could be easier to implement an initial stack.
  • Better tutorials on different configurations.

Likelihood to Recommend

<ul><li>Amazon CloudFront is excellent for serving static content as objects are cached and reserved.</li><li>Dynamic content is more challenging because you lose some control as to what is being cached based on the access.</li></ul>