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

The support team is knowledgeable.

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.

We can personalize a lot of things inside CDN.

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.

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

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 most valuable feature of the solution is the speed of delivery. For example, if we have HTML, CSS, PHP, images, and media files, CloudFront can deliver them quickly and reliably through its worldwide network of edge locations. This reduces latency, allowing webpages to open faster, while also providing high performance.

If the content is not stored in the Amazon CloudFront location, it will be retrieved from an origin, such as Amazon S3, a MediaPackage Channel, or an HTTP file server. For example, if the content is stored on a web server, that server can be identified as the source for the requested content. Suppose that we are hosting an image on a traditional web server, such as a PNG file. We might place the image on a website with the image name adhikary.png. This way, our users can easily navigate to the URL and see the image. When we use Amazon CloudFront, however, they may not be aware that the request is routed from one network to another. This is because the complex connections of interconnected networks that comprise the internet are hidden until the image is found.

The product is very well interconnected with other Amazon services. It is very well connected with EC2, so the integration with S3 becomes easier. It reduces latency to some extent. If all our services fall under the AWS landscape, the user experience would be much better.

Feature-wise, I like the solution's signed URL because it provides security for me.

The speed and usability of the solution are valuable. It's part of AWS. It’s pretty useful.

Amazon CloudFront is a stable solution.

The solution has many features that are comprehensive.

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.

CloudFront is good, comparing all aspects of the platform. It has built-in DDoS protection, which protects against DDoS attacks.

It is stable.

The product’s most valuable feature is the availability of the websites.

The tool is highly available and reliable. It helps to access server applications easily. Integrating Amazon CloudFront with other AWS services was very easy, I would rate it eight out of ten.