Amazon CloudFront Reviews

We use the product to deliver our content. We can use it in end-to-end projects.

The solution has good security features. It has all the features we need. The solution provides more security to our applications. We can integrate the tool easily with other solutions if we follow the documentation properly.

Sometimes, the server goes down automatically. We do not know the reason yet.

I have been using the solution for the past two years.

The product is stable. It gives access to all customers.

I rate the product’s scalability an eight out of ten.

Whenever we contact the support team, the team solves the issue within a day. They respond on time. They put a lot of effort into solving our problems.

Positive

If we do not know anything about AWS, the setup is difficult. If we try to learn the tool, everything will be easier than on other cloud platforms like Azure, IBM, and GCP. AWS is easy to learn. The documentation is very clear. It provides step-by-step information for everything.

Kibana is a tool that is used for open-source data visualization. It is difficult to find information on Azure and GCP’s documentation. Everything is interlinked on AWS on the same page. AWS is one of the best platforms.

We monitor our environment using AWS. I like the EC2 instance. We also use Amazon GuardDuty. I do not have access to the production environment. GuardDuty and AWS Security Hub provide CSPM services to streamline security with automated and continuous security best practices. It provides NACLs and load-balancing features. I will recommend the product to others because it provides high security and high availability worldwide. Overall, I rate the tool an eight out of ten.

We use the solution for content delivery and website acceleration. We use it because AWS and CloudFront are under one environment. It requires AWS configuration.

We didn't face any issues. The AWS environment was very helpful in terms of integration.

The solution could be more simplified for new users. It could be more user-friendly. Also, support needs to be improved.

I have been using Amazon CloudFront for more than a month.

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

The solution is pretty scalable. It works as we expected. We are setting up this solution for a bank with 200 staff employees and more than 5000 users.

I rate the solution’s scalability a seven to eight out of ten.

It is hard to get technical support from Amazon. They have launched in the Philippines around June, but it's very limited.

Neutral

We have DigitalOcean but we use AWS because it is cheap.

The initial setup is moderate in AWS but difficult in Azure.

I rate the product’s pricing a six to seven out of ten, where one is cheap and ten is expensive.

Overall, I rate the solution a seven 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.

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.

Our primary use case for Amazon CloudFront is to cache content near users for faster delivery. For instance, when we need to deliver real-time reports to customers, we cache them in locations close to the users. It allows them to access the reports in a fraction of a second.

The product's most valuable feature is its ability to deliver content to users nearby. We have limited AWS regions, so accessing content directly from these regions can incur delays. However, with CloudFront, we can cache content closer to users, ensuring real-time access.

They could be expanding the number of locations available. It will help users easily access content.

We have been using Amazon CloudFront for six months.

While I have not encountered any major issues, sometimes it isn't easy to implement. However, considering these platforms are already extensively tested, any bugs encountered are usually addressed promptly. Overall, it works well. I rate the platform's stability an eight.

I rate the platform's scalability a nine out of ten.

One of my team members typically handles interactions with AWS support, and they have been able to provide satisfactory answers to our queries.

Positive

I have used Microsoft before.

The initial setup may seem difficult for first-time users, as is often with any cloud platform. However, with some work experience, navigating the screens and understanding the processes becomes easier. It takes only a few minutes or seconds to complete.

The security features provided by CloudFront have benefited our operations as we did not need to implement any additional security measures. The built-in security features were sufficient for our business requirements. I highly recommend a product if someone requires a solution for real-time access to data and content.

I rate it 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.