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/
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Lambda@Edge | + | [[Wikipedia:Lambda@Edge ]] ([[AWS timeline|2017]]) <ref>https://aws.amazon.com/blogs/aws/lambdaedge-intelligent-processing-of-http-requests-at-the-edge/</ref> |
| + | * https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-at-the-edge.html | ||
| + | |||
| + | |||
| + | One common use case is to use Lambda@Edge and [[Amazon DynamoDB]] to translate shortened, user-friendly [[URLs]] to full URL landing pages.<ref>https://aws.amazon.com/blogs/aws/introducing-cloudfront-functions-run-your-code-at-the-edge-with-low-latency-at-any-scale/</ref> | ||
| + | |||
| + | |||
| + | == Related terms == | ||
| + | * [[Lambda@Edge function]] | ||
| + | * [[URL redirection]]: [[subdomain redirections]] | ||
| + | * [[HTTP redirect using lambda handler]] | ||
== See also == | == See also == | ||
| + | * {{URL redirection}} | ||
* {{CloudFront}} | * {{CloudFront}} | ||
[[Category:AWS]] | [[Category:AWS]] | ||
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:
