https://serverless-stack.com/chapters/dynamically-generate-social-share-images-with-serverless.html Hi! Quick question about this guide. Since there is a cloudfront distribution with TTL of a year. There is no need to save the captured images to an s3 bucket right? Without the s3 component but with the same cloudfront configuration it would get run once, image would be captured on the fly and returned, and the result would be cached by cloudfront for a year so the api would never trigger again for the same social card request? Or is there something I'm missing? Just wondering because this guide is great and we're going to use it but the s3 + cloudfront felt like doing the same thing twice in terms of permanent caching

Hey @Tony J, afaik the CloudFront cache is per edge location. So requests from London and NYC will result in Api getting called twice.