In addition to offloading traffic from your origin servers, this also helps enforce web traffic being processed at CloudFront edge locations according to your AWS WAF rules prior to being forwarded to your origin.ĪWS WAF is a web application firewall that helps protect your web applications from common web exploits that could affect application availability, compromise security, or consume excessive resources. By configuring your origin to respond to requests only when they include a custom header that was added by CloudFront, you prevent users from bypassing CloudFront and accessing your origin content directly. You can use custom headers to control access to content. These custom headers enable you to send and gather information from your origin that isn’t included in typical viewer requests.
HTTP header fields are components of the header section of request and response messages in the Hypertext Transfer Protocol (HTTP). You can configure CloudFront to add custom HTTP headers to the requests that it sends to your origin.
In this blog post, you’ll see how to use CloudFront custom headers, AWS WAF, and AWS Secrets Manager to restrict viewer requests from accessing your CloudFront origin resources directly. When you deliver web content through a CDN such as CloudFront, a best practice is to prevent viewer requests from bypassing the CDN and accessing your origin content directly. As a result, viewer requests travel a short distance, improving performance for your viewers. CloudFront ensures that end-user requests are served by the closest edge location. CloudFront is a web service that speeds up distribution of your web content through a worldwide network of data centers called edge locations. Whether your web applications provide static or dynamic content, you can improve their performance, availability, and security by using Amazon CloudFront as your content delivery network (CDN).
0 kommentar(er)
