Amazon CloudFront Reviews

We use Amazon CloudFront to upload our content instead of dealing with hardware. We use cloud software to arrange resources based on the situation. We provide training courses and work mainly on web applications. Most resources are arranged for the front end. During major events, we leverage its scalability features to handle traffic spikes effectively.

Amazon CloudFront allows us to concentrate more on business by reducing complexity. It enables us to manage resources without having to deal with maintenance on-premises, thus saving time and financial investment.

The most beneficial aspect of Amazon CloudFront is its capacity to automatically arrange resources depending on user needs, eliminating the need for on-premises management. 

The security aspect is also beneficial, as it provides various security packages. Furthermore, it alleviates concerns over hardware, computing server capacities, and comes complete with everything needed for cloud work.

Amazon CloudFront seems to have too many unnecessary products, which makes it cluttered. There is also an issue with latency, which is a significant concern. I sometimes find that the environment is overcrowded with different packages and items that don't differ much. 

Additionally, the UI could be enhanced.

We have been working with Amazon CloudFront for six to seven years now.

I rate the stability of Amazon CloudFront a seven out of ten. It can sometimes slow down, likely due to being used by many people simultaneously.

We can set up Amazon CloudFront to handle increased traffic automatically, eliminating the need to manually adjust settings during spikes, which makes it very helpful.

Technical support is generally helpful, earning an eight out of ten. However, there can be delays in getting replies or waiting on the phone, especially when you're under time pressure.

Positive

I have used Oracle, but not in the same scale. On a smaller scale, we had our servers. Once the need for more significant content delivery arose, we switched to Amazon CloudFront.

The initial setup is consumer-oriented and straightforward. Anyone can handle it unless coding is involved, which requires a different expertise level.

Amazon CloudFront offers return on investment by reducing the need to buy and maintain servers and hire additional personnel. It helps save costs substantially.

I do not know the latest pricing details, however, it can be quite expensive. Overall, the pricing seems reasonable, although it could be lowered.

Amazon CloudFront reduces complexity and allows more focus on business objectives. However, latency remains a significant issue. If there were alternatives with lower latency, numbers of users could switch.

I'd rate the solution nine out of ten.

My primary use case for Amazon CloudFront involves utilizing it as a CDN service from AWS. It is used mainly for e-commerce websites and for clients who have critical applications that require faster loading of their mobile applications and websites. 

I've worked with clients in the e-commerce industry who seek to load pages and products faster and in an efficient manner. 

Additionally, I've supported EdTech clients who use videos on their site and conduct live classes; CloudFront aids in delivering content quickly.

CloudFront has allowed organizations to enhance their applications and websites' overall performance, significantly impacting user experience and customer retention. 

It helps regain customers by ensuring that websites load quickly, preventing potential users from switching to competitors' sites. This enhanced user experience translates to higher customer trust and retention, assisting in achieving business goals.

One of the most valuable features of CloudFront is the reduced latency due to its edge locations, which results in a very fast delivery of data. It also offers encryption capabilities and DDoS attack protection, which can be monitored and managed efficiently. 

Another highlight is its user-friendly nature, particularly for developers and DevOps teams, due to complete APIs and arrangements, which simplify integration within applications and websites.

CloudFront could improve in the areas of auto-scaling, reports, and insights. End clients desire more detailed reports to understand usage patterns better. 

There's an opportunity to modernize modules to support organizations completely on cloud with AI and ML solutions, making it more robust and flexible for contemporary technological demands.

I have been working with CloudFront for approximately one or two years.

During my experience with CloudFront, I encountered only a few instances of downtime, not exceeding one or two minutes per occurrence, and it has not been a major issue overall.

CloudFront supports scalability through its auto-scaling feature, using container services like Kubernetes, crucial for handling unpredictable traffic spikes. It is highly beneficial for content delivery and offers significant support during major events.

While there are occasional technical queries regarding latency from multiple data sources, interactions with AWS technical support have been rare due to the minimal technical issues faced.

Positive

I have experience with Azure CDN, which offers a more flexible pricing model for end clients. However, CloudFront is slightly faster than Azure CDN.

I am not involved in the initial setup or deployment directly. That said, I understand CloudFront is user-friendly.

I am not part of the deployment or implementation team. I am more involved in sales, account management, and consulting.

Clients who have used CloudFront, particularly in the e-commerce sector, have seen an increase in profitability. They have acquired new customers and experienced approximately ten to fifteen percent improvements in their ROI.

The pricing of CloudFront is generally reasonable, offering a pay-as-you-go model with a twelve-month free trial for smaller websites. There is room for improvement, especially considering competition from other providers.

I have considered Microsoft Azure CDN.

I recommend CloudFront for any business, application, or website that aims to enhance end-user experience by providing fast content delivery. It is particularly beneficial for e-commerce but can also assist any content-focused endeavor.

I'd rate the solution eight out of ten.

The front end of most of our websites is by CloudFront. It works as a CDN. More than the CDN and the performance, we use Amazon CloudFront for its security. It frontends most of our sites, so we don't have to expose it directly.

Amazon CloudFront is a robust solution. We can use the solution to block certain countries. Since it frontends our S3, we don't directly expose or make public all the media files. We route it through Amazon CloudFront. The tool integrates with AWS's WAF (Web Application Firewall), which adds a lot of L7 security for us.

Those are the primary things that we look at. We can use the solution to host things on EC2 instances or S3 buckets. You can choose what to cache and what not to cache. That feature allows you to work with policies, and we use it heavily. It's very easy to integrate Amazon CloudFront with other AWS services. The solution is very easy to use.

I have been using Amazon CloudFront for more than five years.

We haven’t faced any issues with the solution’s stability.

The solution’s initial setup is very easy.

The solution has improved the performance of our applications. Since we run websites, we usually block certain countries because we get a lot of DDoS attacks and hits from them. Although it's a CDN service, we look at Amazon CloudFront more from a security standpoint than the CDN. I would recommend the solution to other users.

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.

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.

My primary use case involves setting up Amazon CloudFront and then using C# code to generate a token to get files from the S3 bucket. It mainly provides an additional security layer when accessing files.

Amazon CloudFront provides valuable security by ensuring secure file access when accessing files from S3. This security layer is essential for maintaining privacy and data protection in our operations.

I recommend Amazon CloudFront for situations requiring secure file management in the cloud environment.

I haven't worked extensively with CloudFront to identify any specific areas that need improvement. However, it might benefit from multi-region support to enhance performance.

I have been using Amazon CloudFront for one year.

Amazon CloudFront has been very stable and reliable in my experience. It has performed well for our specific use cases.

I have not yet performed any large-scale performance tests, so I cannot comment on the scalability of Amazon CloudFront.

I have not contacted Amazon for any technical issues, so I cannot comment on their technical support. However, in general service interactions, they have been very helpful.

Positive

I also use Azure's cloud environment.

The initial setup of CloudFront is not straightforward and requires some research, however, it is not overly complicated. On a scale of one to ten, where ten is the easiest, I would rate it a five.

I handle the deployment and implementation of Amazon CloudFront by myself.

The pricing for Amazon CloudFront is acceptable and comparable to similar solutions.

I have experience with Azure's cloud environment - not with other CDN services like Fastly or Azure Front Door.

I recommend Amazon CloudFront when security for files is a priority. Overall, I would rate the solution at eight out of ten.

I primarily use it to serve static content and to provide an additional call drive to the API Gateway.

It is very effective in enhancing our application's global reach with its distributed network across geographical locations. It has improved both the performance and reach of our applications.

The most beneficial feature is capturing the static data, which is crucial for our operations.

There is a bit of a workaround required for custom domain management on CloudFront. Mapping the domain involves some complexity with the domain provider, and it's tricky when doing it for the first time.

I have been using CloudFront for five years.

Stability is good. It does not face significant issues or break down.

Scalability is good, there are no issues observed.

Customer support is rated six out of ten due to knowledge-related aspects.

Neutral

The initial setup is not straightforward and requires some prior knowledge and experience.

CloudFront is relatively cheap and worth the money.

One needs to be aware of how data caching works, especially when trying to refresh data, as it involves cache invalidation, which requires some management.

I'd rate the solution eight out of ten.

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.