- 최신
- 최다 투표
- 가장 많은 댓글
CloudFront functions are more limited than Lambda#Edge. You can find the differences here. Those are the only two options for running your code at the edge.
To the list of differences between CloudFront Functions and Lambda@Edge I can add that looking at the latency and cost, you should go with CloudFront Functions as long as you don't have a reason to use Lambda@Edge.
Going back to your question about routing, I think it's a perfect case for CloudFront Functions and this is how AWS is doing it in their samples.
Headers can be added using Response Headers Policy, but it's not your case I suppose.
Thanks MG. Can you also help answer following question please? In AWS CloudFront, at the origin server, the content is divided into media segments which are further distributed through edge locations. But there does not seem to be any details to indicate that the privacy protections envelopes/details were also injected from the content source along with the file segments. Since the origin server adds the privacy protection envelopes to the consecutive segments, can it be inferred that the origin server also injects the privacy protection envelope along with the consecutive file segments? Thank you so much for your quick and timely response.
관련 콘텐츠
AWS 공식업데이트됨 2년 전
Thanks Uri. Can you or also help answer following question please? In AWS CloudFront, at the origin server, the content is divided into media segments which are further distributed through edge locations. But there does not seem to be any details to indicate that the privacy protections envelopes/details were also injected from the content source along with the file segments. Since the origin server adds the privacy protection envelopes to the consecutive segments, can it be inferred that the origin server also injects the privacy protection envelope along with the consecutive file segments? Thank you so much for your quick and timely response.