-
### Issue Summary
Cloud Front Cache invalidation fails with error
botocore.exceptions.ParamValidationError: Parameter validation failed:
Invalid type for parameter InvalidationBatch.Paths.Items, …
-
### Before opening, please confirm:
- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched fo…
-
A cloudfront invalidation step may be required to clear CF cache after some syncs.
Check the default settings.
Otherwise patience required for an expiration to occur and the changes to appear.
lkurz updated
3 weeks ago
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…
-
Hello,
It looks like in version 6.1.4, when a new post is made or page updated, the request that we are sending to Cloudfront to clear the cache is being reported as malformed and results in 502. T…
-
**Describe the bug**
A clear and concise description of what the bug is.
Running `parseDocument(content).toString()` on the following:
```yml
run: aws cloudfront create-invalidation
--distr…
-
Usign fileset strategy to invalidate objects
-
Hello there.
Thank you for the great project.
I'm trying to attach a webAcl to Cloudfront.
Currently I'm working on AstroJS.
Transform is the key of solve this issue but it seems not working…
-
Amazon CloudFront does not automatically detect file changes, even when using an S3 bucket as an origin. The solution to this is that after a syncmedia, a CloudFront invalidation batch must be formed …
-
##### SUMMARY
When requesting `cloudfront_invalidation` the module is firstly trying to fetch **every** existing/passed `invalidation` to determine if the `invalidation` has not already be done…