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 2: | Line 2: | ||
| − | 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> | + | 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> |
Revision as of 13:14, 27 August 2021
One common use case is to use Lambda@Edge and Amazon DynamoDB to translate shortened, user-friendly URLs to full URL landing pages.[2]
See also
- 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:
