Amazon CloudFront Reviews

My use case with Amazon CloudFront is as a CDN solution. It is used for distribution, as my customer told me they needed global delivery to reduce latency and distribution capabilities, so we suggested Amazon CloudFront.

It makes services more useful and reduces latency, making them more efficient.

It drastically reduces latency, which is very useful for web performance and user experience.

Sometimes it is tricky to determine what should be cached and what should not be cached from the user perspective. I need to decide what kind of content requires caching.

It would be nice if they improved the user interface and made it more user-friendly.

The pricing for Amazon CloudFront is quite expensive; I would rate it six if we use all edges. The price could be optimized.

I used Amazon CloudFront around five to six months ago.

It takes about a day to deploy Amazon CloudFront.

From designing architecture and preparing everything for actual use took about a day.

First, I design the architecture to determine what is important, what kind of caching I want, and for how much time. It does not involve any complex processes; deployment is much simpler compared to the architecture design.

It is quite stable with a rating of 10.

Stability is important, but not critical because users might face latency. If Amazon CloudFront is present, it will decrease latency; if it is not, then latency would be slightly greater, but it would still work.

Scalability is 10 out of 10; there are no issues.

I have not used their technical support teams as I did not require it, so I believe it would be 10.

Positive

I would rate my initial setup experience of Amazon CloudFront an eight.

I did work with Amazon CloudFront but am not working with it currently. It was around five to six months ago. I worked with it for approximately two months, implementing it three or four times.

I was not a customer; I implemented it for my clients. Latency for my clients on the projects I worked on was not an issue because Amazon CloudFront was a bonus feature that added value but was not necessarily compulsory.

The documentation for Amazon CloudFront is proper; I would rate it nine, but it depends much on the application side, so it will not help since the SaaS work is harder. My customers do not share that data with us.

I rate Amazon CloudFront a 9 out of 10 overall.

My role demands me to create applications on Amazon using multiple Amazon services. This includes working on greenfield projects and migration projects. In the case of migration projects, if there are applications running on-premise, I have to design them on the cloud using compatible services like EC2, S3, CloudFront, and others.

Hosting static content or with engineering dynamic content is beneficial. CloudFront provides a common access point, manages routing to different methods, and serves as an access point plus API routing. 

With AWS, maintenance is not required as it's a service offered by AWS which maintains itself. Security concerns are manageable through AWS's security mechanisms, with additional security enhancement possible through options like WAF and NACL.

AWS is redesigning its user interface and user experience for CloudFront, and there is room for improvement in certificate management. The current certificate management is through ACM, and a better way of managing certificate changes could make it easier for people to implement and work with.

So far, I have had no problems with respect to the stability of the service itself.

I feel it's fully scalable and responds well to the demands.

I would rate customer support nine out of ten. I find Amazon to be competitive, and its pricing mechanism is considered good.

Positive

Azure is mentioned as offering some things at a lower cost, however, I did not specifically switch from another solution.

I find Amazon's pricing good, rating it eight out of ten and considering it affordable and rightly placed, not expensive.

Azure offers a lower cost for some services compared to AWS.

Amazon has implemented certain improvements over the years. Monthly, I have used some AI features like GitHub Copilot and ChatGPT along with Code Jam. 

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

I utilize Amazon CloudFront for hosting and deploying customer web applications, which are connected to a database. It is used for website content delivery, video streaming, and API acceleration for dynamic content delivery.

Amazon CloudFront optimizes performance and reduces travel time for data requests, improving our system's efficiency. It has also helped us achieve a ten to fifteen percent reduction in data transfer cost.

The solution improves performance by reducing latency and cost. It also has automatic scaling, global reach, lower data transfer costs, and easy setup and configuration, which I find extremely valuable. 

Additionally, integrating CloudFront with other AWS security services provides robust protection against DDoS attacks.

Amazon CloudFront could improve by making it easier to integrate with components from different cloud providers. There are no specific features missing that come to mind right now.

I have been working with Amazon CloudFront for around two to three years.

I have not experienced any performance or stability issues with Amazon CloudFront thus far.

Scalability is handled within the AWS network, allowing automatic scaling to manage increased traffic and ensure consistent performance during spikes in demand.

The technical support service aligns with agreed timelines. Responses are timely and come with actionable solutions. I would rate the support around eight out of ten.

Positive

I have worked with CloudFlare and the Azure content delivery network before using Amazon CloudFront.

The initial setup is straightforward, with steps like selecting the origin, applying encryption, and selecting edge locations. Deployment depends on data volume.

Amazon CloudFront has shown measurable benefits, such as a thirty percent increase in website requests compared to the previous year, and a reduction in data transfer costs for clients.

I find the pricing for Amazon CloudFront to be reasonable. It reduces costs for request handling.

I have evaluated CloudFlare and Azure content delivery networks before choosing Amazon CloudFront.

I would recommend Amazon CloudFront to organizations that host their applications and resources on AWS, particularly for industries like e-commerce, online shopping, and gaming.

I'd rate the solution eight out of ten.

I used it for distributing it with the infrastructure of serverless architecture in Lambda front functions and using it for projects like in adding layers for serverless triggers and using it for building content on storage.

The UI and the functionality in AWS for CloudFront is much better as compared to Azure and GCP.

The distribution networks need to be a little bit more user-friendly in the way that new users are not able to configure the CloudFront distribution as easily as experienced users. I faced quite many difficulties in my early days with CloudFront compared to now.

I started using CloudFront in February of 2022, so around two and a half years.

I haven't faced any issues like breaking down or being unreliable. But if you don't configure it properly in the distribution network, it won't give you any results, and you won't be able to actually find out where you made the mistake.

The scalability is good. That part is good. No doubt.

There have been a few times that I have had to contact the support system, and they've been pretty much responsive. They really helped me out by sharing documentation. There are really few instances that you have to actually contact the support team. But when you do, they respond.

Positive

Compared to other services, CloudFront is expensive as opposed to alternative services of Azure and GCP. However, the scalable part and the availability part from support networks give an advantage and a kick-off that you can enjoy the UI and the scalable aspects.

We compared the solution to Azure and GCP.

Practice as much as you can, set up distribution networks, and make sure that you do not make solutions more complex than they need to be. Divide your whole infrastructure into multiple Check Points and steps. Don't make a single layer of series. Make sure that you have multiple Check Points and different distribution points set up so that you can identify where the problems occur.

I'd rate the solution eight out of ten.

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.

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.

If you're using AWS entirely, it's smooth sailing. But with a mixed stack, things get complicated.

With a mixed stack, things become a problem. With GCP and Azure, the DNS setup gets tricky when using CloudFront. With AWS, it's smooth and streamlined. Their GUI provides all the details and is very easy to navigate. 

The challenge starts to occur because AWS gives you only one DNS endpoint for the entire service. This single endpoint covers your CDN, AWS server, and domain migration needs.

If you use any other solution like GCP or Azure, you face additional configuration changes and account management. You need separate accounts for AWS CloudFront and your chosen platform, like GCP. This means securing and managing two separate accounts – an extra responsibility.

With Cloudflare, you just need one account and pay for it. Managing the complex DNS details isn't your burden. However, on the flip side, CloudFront might require more hands-on management on your part.

I have been utilizing it for the past three years. 

Amazon is top-notch in terms of customer service, on par with the quality of their services. They've been very supportive. Though, if I had to compare, I'd rate Akamai's support slightly higher.

Positive

We utilize all products: Akamai, CloudFront, and even Cloudflare. We have many clients who work with different technologies, so we get the chance to experience diverse options as tech partners.

As tech advisors, it's our responsibility to offer informed recommendations because we're partnering with the client and ultimately responsible for ensuring which tech is suitable. 

Our task is to offer them the best XYZ stack options based on their needs. They want to avoid tech hassles, so they've outsourced everything. We provide our best recommendations through consultations and design based on those consultations. Then, there's a back-and-forth with the client regarding budget, team analysis, and deployment decisions. 

Once we have all the information, we move forward. We don't have complete control, but we have a significant influence, around 60%, on the technology chosen for migration.

CloudFront itself is relatively easy to configure, much easier than Akamai. But using it with other server platforms like GCP or Azure can be a real pain.

So, on CloudFront, the ease of use comes at the cost of managing a single endpoint for everything, while Cloudflare offers more flexibility but requires more management effort.

There is an ROI. Our organization is based in India, a lot of our clients are multinational enterprises or even non-profits.  

We've been using CloudFront to provide a good user experience and security, and we've been pretty happy with it. Especially for non-profits where cost optimization is crucial, CloudFront has kept things moving in the optimal direction.

For CloudFront, I'm quite satisfied with the pricing. Initially, it doesn't require many resources for this specific solution. 

Additionally, the pay-as-you-go model with a generous free tier makes it easy to onboard and pay for what you use. This is a big advantage for SMEs, making it very convenient.

Overall, I would rate the solution an eight out of ten if it is in the AWS ecosystem. So, it's mainly great on AWS.

If you're using another ecosystem, like Azure or something else, then it might be more like five 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.

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.

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.