Difference between revisions of "CloudFront Functions"
Jump to navigation
Jump to search
↑ https://aws.amazon.com/blogs/aws/introducing-cloudfront-functions-run-your-code-at-the-edge-with-low-latency-at-any-scale/
↑ https://aws.amazon.com/cloudfront/faqs/
| (One intermediate revision by the same user not shown) | |||
| Line 9: | Line 9: | ||
* [[HTTP header]] manipulation | * [[HTTP header]] manipulation | ||
* [[Access authorization]] | * [[Access authorization]] | ||
| + | |||
| + | |||
| + | == Related == | ||
| + | * [[Cloudfront HTTP redirections management]] | ||
| + | * [[Redirect the viewer to a new URL]] | ||
==See also== | ==See also== | ||
Latest revision as of 12:43, 12 August 2024
Amazon CloudFront (May 2021) [1] allows to do securely deliver data, videos, applications, and APIs to your customers globally with low latency and high transfer speeds. CloudFront Functions is meant to compliment Lambda@Edge, not replace it.[2]
Functions[edit]
- Cache-key manipulations and normalization
- URL rewrites and redirects
- HTTP header manipulation
- Access authorization
Related[edit]
See also[edit]
- AWS CloudFront, distributions, Invalidations, Amazon CloudFront Ready,
aws cloudfront, CloudFront Functions, Lambda@Edge, Origin Shield, Signed URL, OAI, Origin Access Control (OAC), Amazon CloudFront edge locations, cloudfront.net, invalidations, CloudFront Security Savings Bundle (CFSSB) - CDN, Multi CDN: AWS CloudFront, Cloudflare, Azure Front Door
az cdn, KeyCDN, Akamai, Gcore, Fastly, coin.host, EDNS Client Subnet, cache
Advertising:
