-
Hello Awsbroz,
Good day!
Thank you for your question and feedback.
The explanation aims to clarify that while Lambda@Edge isn’t primarily for caching large datasets, it can enhance content delivery by executing logic at edge locations. However, you are correct that Lambda@Edge is mainly designed for computing, and the actual caching happens in Amazon CloudFront. What Lambda@Edge does is allow custom behavior—such as modifying requests or responses or implementing specific logic—closer to the user. In this context, the explanation focused on its limitations in handling traffic rather than pointing out that caching itself is handled by CloudFront.
We agree that the emphasis on not needing Lambda@Edge for caching in this specific scenario could have been more precise. The explanation will be updated to reflect that distinction better and avoid confusion between computing functions and actual caching mechanisms.
We appreciate your keen observation and will make adjustments to improve clarity going forward!
Regards,
Neil @ Tutorials Dojo
