Head of Data & Content at a transportation company with 10,001+ employees
Real User
Top 10
Nov 28, 2025
From my perspective, I see some weaknesses in Amazon CloudFront; I would rate the product something around nine out of ten, but there are disadvantages compared to its competitors. Talking specifically about Amazon CloudFront, I think they could have some additional features in the future, and I believe they may lack certain functionalities.
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.
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.
AWS Developer at a insurance company with 10,001+ employees
Real User
Top 5
Oct 10, 2024
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.
Wordpress Developer & AWS Solution Architect at Seahorse Data
Real User
Top 5
Sep 23, 2024
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.
Consultant Architect - Cloud Deployments, DevOps and Information Security at a tech services company with 11-50 employees
Real User
Top 10
Apr 2, 2024
The policies and prices keep on changing frequently with AWS solutions, including Amazon CloudFront. One of the biggest challenges with Amazon CloudFront is their pricing policy, which if mishandled can land a user with huge bills.
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.
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.
Amazon CloudFront can improve by accurately determining the latency of a non-defined URL that the solution encounters. For example, if we have a direct connection, the solution will link to the data in a fraction of a second but if we don't have a direct connection and are using a domain name instead, it will take longer to connect. To improve this, we should consider getting a direct connection.
Solution architect at a integrator with 51-200 employees
Real User
Jul 7, 2021
Its price is really high and can be improved. From the technology perspective, they should have some multi-platform integration. When you are configuring something on top of it, it is geoblocking. There are some limitations for the IP addresses, which other solutions don't have. They should have more Edge locations so that CloudFront can be used much more. If they can make it a little bit cheaper and better than other networks, we will be able to use it more. They don't have a lot of PoPs in Asia-Pacific. That's one of the reasons why there is some latency. They can reduce this latency by adding multiple PoPs. If we are concentrating on markets, such as Vietnam, the Philippines, where we don't have PoPs, we have to ride on other providers.
Amazon CloudFront is a global content delivery network (CDN) service that accelerates delivery of your websites, APIs, video content or other web assets. It integrates with other Amazon Web Services products to give developers and businesses an easy way to accelerate content to end users with no minimum usage commitments. Amazon CloudFront can be used to deliver your entire website, including...
From my perspective, I see some weaknesses in Amazon CloudFront; I would rate the product something around nine out of ten, but there are disadvantages compared to its competitors. Talking specifically about Amazon CloudFront, I think they could have some additional features in the future, and I believe they may lack certain functionalities.
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.
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.
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.
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.
Sometimes, the server goes down automatically. We do not know the reason yet.
Amazon CloudFront is harder to understand compared to Azure.
Improvements are needed as per customer requirements.
The policies and prices keep on changing frequently with AWS solutions, including Amazon CloudFront. One of the biggest challenges with Amazon CloudFront is their pricing policy, which if mishandled can land a user with huge bills.
Support needs to be enhanced.
The UI could be more user-friendly. There were a lot of technical terms on the UI page.
The solution could be more simplified for new users. It could be more user-friendly. Also, support needs to be improved.
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.
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.
The tool must provide regional control. It must provide features to allow only one region to reach the content via CDN.
The user interface could be improved. It's much easier to control or see financial results from similar solutions from Google.
I have utilized certain characteristics and invested effort in reading the documentation, which proved to be challenging.
Amazon CloudFront can improve by accurately determining the latency of a non-defined URL that the solution encounters. For example, if we have a direct connection, the solution will link to the data in a fraction of a second but if we don't have a direct connection and are using a domain name instead, it will take longer to connect. To improve this, we should consider getting a direct connection.
Its price is really high and can be improved. From the technology perspective, they should have some multi-platform integration. When you are configuring something on top of it, it is geoblocking. There are some limitations for the IP addresses, which other solutions don't have. They should have more Edge locations so that CloudFront can be used much more. If they can make it a little bit cheaper and better than other networks, we will be able to use it more. They don't have a lot of PoPs in Asia-Pacific. That's one of the reasons why there is some latency. They can reduce this latency by adding multiple PoPs. If we are concentrating on markets, such as Vietnam, the Philippines, where we don't have PoPs, we have to ride on other providers.