Skip to content
This repository was archived by the owner on Aug 7, 2025. It is now read-only.

Fix doc on Lambda@Edge limitation #1757

Merged
merged 1 commit into from
May 7, 2025
Merged

Fix doc on Lambda@Edge limitation #1757

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions content/en/user-guide/aws/cloudfront/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,8 +79,7 @@ You can enable this feature by setting `CLOUDFRONT_LAMBDA_EDGE=1` in your LocalS
### Current limitations

- The [`UpdateDistribution`](https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_UpdateDistribution.html), [`DeleteDistribution`](https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_DeleteDistribution.html), and [`Persistence Restore`](https://docs.localstack.cloud/user-guide/state-management/persistence/) features are not yet supported for Lambda@Edge.
- Lack of full support for `viewer-request` and `viewer-response` event types.
Please expect inconsistencies and missing functionality.
- The `origin-request` and `origin-response` event types currently trigger for each request because caching is not implemented in CloudFront.

## Using custom URLs

Expand Down