You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7Lines changed: 7 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -64,6 +64,13 @@ The Next.js Terraform module is designed as a full stack AWS app. It relies on m
64
64
65
65
This is a second CloudFront distribution that serves a special JSON file that the Proxy ([`III`](#III-lambda-edge-proxy)) fetches as configuration (Contains information about routes).
66
66
67
+
-**CloudFront Invalidation Queue**
68
+
69
+
When updating the app, not the whole CloudFront cache gets invalidated to keep response times low for your customers.
70
+
Instead the paths that should be invalidated are calculated from the updated content.
71
+
Depending on the size of the application the paths to invalidate could exceed the [CloudFront limits](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html#invalidation-specifying-objects%23InvalidationLimits) for one invalidation.
72
+
Therefore invalidations get splitted into chunks and then queued in SQS from where they are sequentially sent to CloudFront.
0 commit comments