Difference between revisions of "CloudFront Lambda@Edge"
Jump to navigation
Jump to search
↑ https://aws.amazon.com/blogs/aws/lambdaedge-intelligent-processing-of-http-requests-at-the-edge/
↑ https://aws.amazon.com/blogs/aws/introducing-cloudfront-functions-run-your-code-at-the-edge-with-low-latency-at-any-scale/
| Line 7: | Line 7: | ||
== Related terms == | == Related terms == | ||
| + | * [[Lambda@Edge function]] | ||
* [[URL redirection]]: [[subdomain redirections]] | * [[URL redirection]]: [[subdomain redirections]] | ||
* [[HTTP redirect using lambda handler]] | * [[HTTP redirect using lambda handler]] | ||
Latest revision as of 10:39, 21 June 2023
Wikipedia:Lambda@Edge (2017) [1]
One common use case is to use Lambda@Edge and Amazon DynamoDB to translate shortened, user-friendly URLs to full URL landing pages.[2]
Related terms[edit]
See also[edit]
- URL redirection, Subdomain redirection, Lambda@Edge: HTTP redirect using lambda handler, Redirect: HTTP status codes 3xx
- 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)
Advertising:
