Amazon CloudFront enables rapid content delivery with its global network of edge locations, providing enhanced security through DDoS protection and seamless integration with AWS services like S3 and EC2.
| Product | Mindshare (%) |
|---|---|
| Amazon CloudFront | 5.2% |
| Cloudflare | 14.7% |
| Akamai | 11.3% |
| Other | 68.8% |
| Company Size | Count |
|---|---|
| Small Business | 17 |
| Midsize Enterprise | 4 |
| Large Enterprise | 10 |
| Company Size | Count |
|---|---|
| Small Business | 115 |
| Midsize Enterprise | 43 |
| Large Enterprise | 127 |
Amazon CloudFront is a powerful content delivery network used for delivering content efficiently with reduced latency, leveraging a worldwide network for enhanced speed and security integration with AWS services. Known for stability and comprehensive features, it simplifies caching content near users, encrypting data, and offering customizable content management.
What are CloudFront's key features?In industries requiring rapid content access, such as e-commerce and media distribution, Amazon CloudFront is frequently used for hosting media files and enhancing website performance. Its integration capabilities with AWS services make it suitable for businesses optimizing for speed and security. By offloading media libraries and employing serverless architectures, it is a go-to choice for companies looking to accelerate APIs and improve user experiences globally.
Unilever, Spotify, Pinterest, MLB Advanced Media, Foursquare, PBS, Airbnb, Netflix, WIX, Comcast, Automobili Lamborghini, Rovio, Discovery Communications
| Author info | Rating | Review Summary |
|---|---|---|
| Head of Data & Content at a transportation company with 10,001+ employees | 3.5 | I've had a positive experience with Amazon CloudFront, appreciating its scalability and integration with other AWS services, though I see room for added features. Setup was smooth, support is satisfactory, and I find the pricing reasonable. |
| Cloud Support Engineer at Operisoft Technologies | 4.5 | I use Amazon CloudFront as a CDN solution for global content delivery to reduce latency effectively. While it enhances web performance and efficiency, the user interface could be more user-friendly, and the pricing is relatively high. |
| Infrastructure Architecture at Capgemini | 4.5 | I find CloudFront excellent for content hosting and routing, appreciating its stability and scalability. While UI/UX and certificate management could improve, its security, maintenance, and competitive pricing are strong. I rate it 8/10. |
| Product Manager at Infozion | 4.0 | We experience smooth sailing with AWS CloudFront, but it becomes complicated with mixed stacks like GCP or Azure due to DNS setup challenges. Despite requiring more management, CloudFront offers ROI and optimal cost management, especially benefiting non-profits. |
| Cloud Software Engineer at a comms service provider with 51-200 employees | 4.5 | I value Amazon CloudFront for secure S3 file access, finding it very stable despite a non-straightforward setup. It offers valuable security and acceptable pricing. I recommend it for secure file management, rating it eight out of ten. |
| Consultant at NatWest Group | 4.0 | We use Amazon CloudFront at our bank to host public websites with ease due to its user-friendly configuration and reduced latency. However, support response times need improvement. Overall, CloudFront significantly outperforms our previous on-premise solution by making sites faster. |
| Consultant at NatWest Group | 3.5 | I used Amazon CloudFront to host a public website. The support team is knowledgeable, but the UI needs to be more user-friendly due to excessive technical terms. I compared it with Windows Azure CDN, finding similar functionalities. |
| Infrastructure manager | 4.5 | I use Amazon CloudFront for fast content delivery, benefiting from edge locations and easy integration with Amazon S3. While we have a 45% ROI, expanding server locations would further reduce latency. Previously, I used Akamai CDN. |
| senior IT professional at ThinkSmart for Development and Training | 4.0 | I utilize Amazon CloudFront for hosting and deploying web applications with improved performance through reduced latency and cost. Its automatic scaling, global reach, and integration with AWS security are valuable, though integration with other providers could be easier. |
| Global Business Client Partnership Management at Bahrain Telecommunication Company BSC (Batelco) | 5.0 | We initially faced high latency with our AWS connection in Europe. Moving it to Bahrain improved performance for regional operators in Bahrain and Saudi Arabia. AWS issues are rare and quickly resolved, making it a reliable choice for us. |
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.
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.
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 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
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.
We work for a bank. We use the solution to host some public websites. The CDN hosts images and static content related to the website. We are not working in an active production environment. Currently, we are conducting User Acceptance Testing. We have only released it to a few focus development groups to check how the site is used.
I like the solution’s ease of use and configuration. Getting the certificate signed and using it in CDN was easy. It is easy to configure. The product is easy to configure compared to other AWS services. We can choose locations close to our users. It helps reduce latency and improves the time it takes to refresh the site.
It normally takes over a day to get a reply from the support team. The support must be improved.
I have been using the solution for seven months.
We are still testing the tool in the UAT phase. So far, our experience with the tool’s stability has been good.
Globally, we have 60,000 to 80,000 users. We plan to deploy a full-scale production. We might have almost five million users.
The support team does not provide immediate responses.
The setup was straightforward. Most of the features are available out of the box. The learning experience was very straightforward. The answers to a lot of our questions were available in the UI. There is a link that we can click to learn more about the features. It was quite user-friendly. The tool is deployed on the cloud.
The setup time was much less when we deployed the tool on the cloud. The procurement of the services, testing, and deployment was quick and easy compared to on-premise provisioning. We have a team of eight people for deployment, including managers, developers, and testers. The setup was very smooth and easy to configure.
The product provides reduced latency and quicker site refreshes. We have seen a significant improvement over the on-premise version we used earlier. The sites appear faster to the users.
The product must enable cost optimization. We do not have many options to optimize costs. Most of the prices are fixed. It would be good if the vendor could provide different tiers or allow users to optimize prices.
We have not used the security features to the fullest extent. Initially, we had an on-premises solution. I recommend that people use the tool. Overall, I rate the product an eight out of ten.
We used the solution to host a public website.
The support team is knowledgeable.
The UI could be more user-friendly. There were a lot of technical terms on the UI page.
I have been using the solution for three to four months.
Once the product was deployed, it was stable. Other than human errors, we did not face any issues. I rate the stability an eight out of ten.
The product is quite scalable. Even high-definition images load up pretty quickly. I rate the scalability an eight out of ten. We have 20,000 users.
The response time is better than that of Microsoft.
Getting the correct documents for the setup was a little difficult. It was easier to find information on Microsoft. It took us a few weeks to deploy the tool. It is a cloud-based solution. Some configuration parameters were a little difficult to understand. I had to go through a lot of documents to understand the configurations.
The deployment was done in-house. We had five members, including managers, on our technical team.
We developed POCs using Amazon CloudFront and Windows Azure CDN. The functionalities of both products are the same. We used Amazon S3 and Amazon CloudFront for hosting. We also did automation using AWS Lambda.
People who want to use the solution must first go through the documentation. It is much easier than directly jumping into the service. The documentation helps us understand what we need to get the configuration done. Overall, I rate the solution a seven 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 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 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.
Our newest AWS connection was initially in Europe and we experienced very high latency. However, bringing it to Bahrain has drastically improved performance, not just for us but for all the regional operators connected to our ISN, including entities in Bahrain and Saudi Arabia. The ultimate users of these services are the enterprises themselves. However, we don't sell directly to them. Instead, we sell to operators, both Bahraini and regional, who then sell the services to the enterprises.
Its main advantage is that it offers something in this region that wasn't available before; previously, you had to go outside the region to get the same level of service you can now access right here in Bahrain. It's truly incredible. Our customers are more interested in accessing CDNs and peering with each other. Moreover, building this IX has significantly changed how traffic is handled. It has enabled better regional connectivity and access to content, which was our main goal. It has saved us money and time.
The only issues we've faced were when AWS itself had problems, and that's very rare. I can only recall one instance when they had issues, but they managed to resolve it quickly.
I have been using the solution for three years now.
The technical support is good.
Positive
The initial setup is very straightforward. We support our customers by shipping the equipment and providing all the necessary information they need. Our team receives and keeps the equipment until the customer is ready to install it. The deployment time depends on the customer, but we provide all the support and cross-connects they need. We've even done same-day setups when needed. While not everything is urgent, we're happy to accommodate when there is a sense of urgency.
The tool is affordable.
Going for the tool really depends on the preferences of the company. Both Azure and AWS have their own advantages and disadvantages, which is why they're both in the market today. Some people prefer using Microsoft Azure, while others prefer AWS. However, it's important to note that switching from one cloud provider to another is not an easy decision. It requires a significant investment of time and effort in training and setting up equipment on a particular cloud platform.
Overall, I rate the solution a perfect ten.
