The cloud architect's guide to CloudFront

CloudFront is AWS's content delivery network. It consists of more than 200 edge locations around the world, which makes sure no visitor is too far from one of them. Each edge is a full-fledged data center, connected by dedicated data cables which makes the connection reliable and fast.

You can take advantage of this global network with the CloudFront service. Using it, you can route your users to locations closer to them, making the waiting times between pressing enter and seeing the results a lot shorter.

But CloudFront is not just about moving connections closer to users. It is also a routing engine, a proxy that sits between the visitors and the servers. You can configure path-based routing where a visitor uses a single connection to communicate with multiple backend services. This hides the complexities of an architecture consisting of multiple services, and also allows a single point of contact where you have a single point to configure modern communication protocols and all the other services benefit from it. You can use HTTP/2, IPv6, and your custom domain name even with services that do not support them.

On the other hand, CloudFront is not easy to configure. Routing itself has multiple parts that can break if you are not careful, and setting up caching is a lot more complicated than what the relatively simple interface would suggest.

In this course, you'll learn how to use CloudFront from the ground up. We'll start with a high-level overview of the service and the key terms that are all over the documentation and the console. Then we'll move on to the finer details of the available configuration options. The two most important and error-prone concepts, routing and caching, are discussed in-depth, as well as how to use your own domain name.

During the course, you'll see the best practices and the common problems with configurations, and also how to debug CloudFront when something is not working.

This course is for architects who have some experience with the AWS platform. We won't go into detail how to configure an S3 bucket or how to create an API Gateway, but no prior experience with CloudFront is necessary.