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/
| Line 1: | Line 1: | ||
| − | [[Amazon CloudFront]] ([[AWS timeline|May 2021]]) <ref> https://aws.amazon.com/blogs/aws/introducing-cloudfront-functions-run-your-code-at-the-edge-with-low-latency-at-any-scale/</ref> allows to do securely deliver data, videos, applications, and APIs to your customers globally with low latency and high transfer speeds. | + | [[Amazon CloudFront]] ([[AWS timeline|May 2021]]) <ref> https://aws.amazon.com/blogs/aws/introducing-cloudfront-functions-run-your-code-at-the-edge-with-low-latency-at-any-scale/</ref> 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.<ref>https://aws.amazon.com/cloudfront/faqs/</ref> |
Latest revision as of 14:00, 27 August 2021
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
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 - CDN: AWS CloudFront, Cloudflare, Azure Front Door
az cdn, KeyCDN, Akamai, Gcore, Fastly
Advertising:
