Amazon CloudFront Reviews

We use Amazon CloudFront for offloading our media libraries for WordPress. It is mostly used for our clients' websites where we need to use a CDN for speed optimization of websites.

Using Amazon CloudFront drastically increases the performance of websites. The integration process is simplified and clear, especially with the plugin we use. This has improved our speed optimization effectively.

The best feature of Amazon CloudFront is its simplified process and easy integration. The plugin we use does most of the work, making it easy for us. The speed optimization is another valuable feature.

There are some solutions needed for integration that are not free. It would be better if there was a straightforward way to configure it without additional costs.

I have been using Amazon CloudFront for two years.

I do not remember having any difficulty with stability while using Amazon CloudFront.

Amazon CloudFront is easy to scale up or down as needed.

The initial setup of Amazon CloudFront requires experience and expertise.

I haven't compared pricing with other solutions, so I can't comment on it. Usually, it depends on the number of files you are uploading and the resources you are distributing. It is a pay-as-you-go model.

I would recommend Amazon CloudFront to other people.

I'd rate the solution eight out of ten.

We use Amazon CloudFront for various purposes based on our needs and budget considerations. For instance, if we have live content like static images or videos that should be quickly accessible on our website, the tool is handy. It enables us to deliver content swiftly to end users. The cache features also reduce the need to access the origin server, optimizing our website speed.

Previously, we were directly fetching videos from our Amazon S3 URL, resulting in slow image loading and high latency on our landing page. To address this, we explored Amazon CloudFront features with edge locations to improve content delivery speed. We integrated Amazon S3 with Amazon CloudFront, and now all content is served through the product, leading to better optimization than our previous setup.

The beneficial feature for the entire AWS community is the presence of edge location servers. These servers are strategically located in multiple locations, allowing efficient content delivery from the nearest server. 

We opted for the tool because we already used the Amazon S3 bucket. Since Amazon CloudFront is an AWS feature, integrating it with our S3 bucket was easy. Transferring data from one source to another within AWS is straightforward. The process might have been more time-consuming if we had chosen a different CDN provider. Amazon CloudFront, a managed service by AWS, offers an easy integration solution.

The solution can benefit from expanding its data center and server locations to multiple places for smoother content delivery with even lower latency. The latency we experience is sufficient for our needs, and we are doing well. However, if they expand their locations in the future, it could be a positive factor. Its competitors have multiple data and server locations. 

I have been working with the product for five years. 

I rate the tool's stability a nine out of ten. Customization is easy with the product. 

I rate Amazon CloudFront's scalability a ten out of ten. I use it 24/7. 

AWS technical support can't be fully assessed at the moment. In the basic support plan, users have the option to open basic support tickets, and AWS provides choices for responses through calls or live chat. To access advanced technical support, users need to subscribe to premium plans. Its response time is quick. Though they give a timeframe of 24 hours, support is immediately initiated.  

Positive

I have used Akamai CDN before. I chose the product since it integrates easily with my internal system. It is widely used and comes with rich documentation and resources. 

The tool's deployment is easy. For inexperienced resources, I rate deployment difficulty an eight out of ten. For me, it's nine point five out of ten. The product comes with a vast amount of resources and documentation. 

We had a deadline of one and a half months. However, we could go into production within four weeks, i.e., 25 days. Deployment includes quality assurance and staging processes. One resource is enough to handle the deployment process. The person responsible for deploying the solution should know CI/CD processes. They should understand security compliance, gate methodologies, and the functioning of code push and pull. Familiarity with Webhooks and the dashboard of AWS CodePipeline or check kits is necessary.

Once the setup is done, the tool doesn't require frequent changes. Two resources are needed for maintenance, and one would be enough later. 

We have seen an ROI of 45 percent with the tool's use. 

I rate the product's pricing an eight out of ten. The licensing follows a pay-as-you-go model. 

I rate the solution a nine out of ten. 

I use the solution to expose fact files to have more latency. We expose the front end of applications using the product.

We can personalize a lot of things inside CDN.

The product should be more intuitive. It should provide better descriptions of the fields. It can improve the cache and have some customization inside cache configurations. While the product is easy to understand for a developer, it is not so easy for a DevOps engineer like me.

Support is good. Once, I wanted to increase the response time and did not understand which feature to use. So I requested support to increase the timeout. At that moment, it was intuitive because I searched the Internet and understood the use case.

Positive

The ease of setup depends upon the use cases. If you are using the most common use case, it's not difficult to set up. We can put our application in origin. We can put an S3 bucket as the origin and research and request from there. You can limit the request to be private inside the product and S3. When we need to go a little bit deep, like when we need to customize some things related to cache, the setup is not intuitive.

We do not need to maintain the product after deployment and calibration. We customize the information from our application in the product and choose the use case. We do not need to worry about maintaining the solution after that.

Cloudflare is more simple, but it is more focused on other use cases. Most companies I work with use 90% CloudFront and 10% Cloudflare.

Overall, I rate the solution an eight out of ten.

We use the product as a CDN in front of several public websites.

The platform's most valuable feature is its ability to deliver content globally, optimizing website delivery for users worldwide. Additionally, it is an inexpensive product.

I encountered challenges with seamlessly integrating different services. Specifically, integrating a WAF (Web Application Firewall) with CloudFront took a lot of work. The process required managing infrastructure, including configuring VPC (Virtual Private Cloud) settings, setting up load balancers, and connecting them to the WAF. The lack of seamless integration made the setup process more complex and required additional research to manage all the services properly.

We've been using Amazon CloudFront for about 3 months now.

The platform is stable.

The product is highly scalable, even if you use it on a large platform. It's designed to handle increased demand without errors. Additionally, if you need more power or resources, you can easily find a solution within AWS.

The initial setup was straightforward, but it required some research. For a small website, it took about one day to one and a half days to complete the setup. Without prior research, it could take up to three hours to set up once you're familiar with the process. The complexity ultimately depends on the architecture, but managing the website takes two to three hours.

Our ROI with CloudFront is quite favorable. We can deliver our services without incurring significant outbound traffic costs, as it's included in the price and quite affordable. Compared to managing several instances implemented in different locations, it proves to be much more cost-effective. The exact ROI depends on the use case. Still, for scenarios like hosting a website that requires global accessibility, it can lead to significant savings, potentially up to 50% or more compared to alternative solutions.

The product has a mid-range pricing.

The security features have helped to protect the content. It is an expensive product with valuable features. I rate it an 8.

We use the solution to build social media solutions. They distribute the short videos using the cloud.

CloudFront is good, comparing all aspects of the platform. It has built-in DDoS protection, which protects against DDoS attacks.

Support needs to be enhanced.

I have been using Amazon CloudFront for 3 years.

The product is stable.

I rate the solution’s stability a ten out of ten.

10,000-20,000 users are using this solution, but it dropped these days.

I rate the solution’s scalability a nine out of ten.

We have basic customer service support. We usually use chat or call. It goes first to non-technical people, like salespeople or supports agents, who then forward the cases to a technical person.

Neutral

The initial setup is easy. You can do it on the dashboard itself. It requires minimal experience.

It takes five to ten minutes to deploy.

We have private pricing on AWS. We get a fifty percent discount.

I recommend the solution. It has good services. It is scalable and cost-effective. We can add a graph on the other security on top of Cloudflare.

Overall, I rate the solution a nine out of ten.

I've used CloudFront, as the company's CDN, to distribute content across better local servers to help the final user perform better.

The most valuable feature is the number of servers they can put your content in while being reliable. They are stable. It's a strong feature that helps distribute content close to the users.

The user interface could be improved. It's much easier to control or see financial results from similar solutions from Google.

The solution is very stable. I can only remember one or two times that the product was unstable, but overall, it is very hard for something to go wrong.

The solution is very scalable.

In the free tier, you receive very little support from Amazon. You get more support with premium support, but I believe Amazon lacks documentation. This is mainly a problem with people like us from abroad because it's not common for them to translate materials, and they are closed off from the community, so they do not offer the greatest support.

Neutral

It takes a long time to deploy the solution, but the most difficult part is deploying it nicely. The user should fine-tune the configuration to achieve the solution's full potential.

Depending on the complexity of the deployment, the number of people required varies. Just deploying the CDN on the cloud is not hard. If you have one or two good developers, they can deploy the solution themselves.

I rate Amazon CloudFront's pricing a five out of ten.

Amazon CloudFront is not the most complex application for Amazon to set up, but some complexities could be improved to get the most of the power out of this service. However, the solution works perfectly when designed well by the architect.

I rate the solution an eight out of ten.

We used the product for one of our projects associated with online gaming.

The product is very well interconnected with other Amazon services. It is very well connected with EC2, so the integration with S3 becomes easier. It reduces latency to some extent. If all our services fall under the AWS landscape, the user experience would be much better.

A lot of caching features must be added to the solution. It only has the standard caching features. Akamai has properties that have multiple features that can be added as rules. Something similar must be added to CloudFront.

I have been using the solution for more than three years.

The tool is stable.

The tool is scalable. A team of three people was using the product in our organization.

We opted for the standard support. The support was not the best. It was satisfactory. The support people took a lot of time to answer. Though we explained our issues well, they did not understand them clearly. It might be because the support team lacked skilled people. The expensive support packages might not have such issues.

Neutral

I have worked with Akamai.

The initial setup is easy.

The solution’s price is reasonable. It is much more reasonable than Akamai.

I would recommend CloudFront to people dealing with simple projects and AWS infrastructure. Overall, I rate the tool a seven out of ten.

Our developers developed something that needed cloud services and deployed it on the Amazon CloudFront server.

Amazon CloudFront is a stable solution.

Amazon CloudFront's pricing is a bit high, and we would appreciate it if they reduced it.

Amazon CloudFront's setup is a bit difficult, and we would love it if they made it easier.

I have been using Amazon CloudFront for the last six months.

Amazon CloudFront is a scalable solution. Four or five people are using Amazon CloudFront in our company.

Amazon CloudFront's initial setup is difficult, and it takes a lot of time to set it up.

Amazon CloudFront is an expensive solution.

I would recommend Amazon CloudFront to other users.

Overall, I rate Amazon CloudFront a seven out of ten.