Title: CloudFront
Last modified: December 21, 2022

---

# CloudFront

 *  Resolved [fujiwarayuko](https://wordpress.org/support/users/fujiwarayuko/)
 * (@fujiwarayuko)
 * [3 years, 5 months ago](https://wordpress.org/support/topic/cloudfront-6/)
 * We encountered following exception from CloudFront. We doesnot change any php
   source code for 1years. Thus, we are not sure why path is judged as “invalid 
   invalidation paths “.
 * I have attached exception log.
 * Could someone suggest any possible reason?
 * [12-Dec-2022 04:13:25 UTC] exception ‘Aws\CloudFront\Exception\CloudFrontException’
   with message ‘Error executing “CreateInvalidation” on “[https://cloudfront.amazonaws.com/2020-05-31/distribution/E248NT5PQCQNPI/invalidation&#8221](https://cloudfront.amazonaws.com/2020-05-31/distribution/E248NT5PQCQNPI/invalidation&#8221);;
   AWS HTTP error: Client error: `POST https://cloudfront.amazonaws.com/2020-05-
   31/distribution/E248NT5PQCQNPI/invalidation` resulted in a `400 Bad Request` 
   response:
 * Sender< (truncated…) InvalidArgument (client. – ): Your request contains one 
   or more invalid invalidation paths Sender`InvalidArgument`Your request contains
   one or more invalid invalidation paths.a1fc1ecd-18c3-4780-929f-20543c30ed1f’
    -  This topic was modified 3 years, 5 months ago by [fujiwarayuko](https://wordpress.org/support/users/fujiwarayuko/).
    -  This topic was modified 3 years, 5 months ago by [fujiwarayuko](https://wordpress.org/support/users/fujiwarayuko/).
    -  This topic was modified 3 years, 5 months ago by [fujiwarayuko](https://wordpress.org/support/users/fujiwarayuko/).
    -  This topic was modified 3 years, 5 months ago by [fujiwarayuko](https://wordpress.org/support/users/fujiwarayuko/).

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [Chris Grycki](https://wordpress.org/support/users/cgrycki/)
 * (@cgrycki)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/cloudfront-6/#post-16452908)
 * This sounds like the same issue that I encountered recently for post types that
   did not have an archive page. I believe the issue was introduced with the release
   of version 6.1.4 of the plugin. If you check your CloudTrail logs and see “://*”
   listed among the invalidation paths in the request, then that is likely the problem.
   I submitted a pull request to the plugin’s GitHub repo to address this.
 * [https://github.com/amimoto-ami/c3-cloudfront-clear-cache/pull/108](https://github.com/amimoto-ami/c3-cloudfront-clear-cache/pull/108)
 *  Thread Starter [fujiwarayuko](https://wordpress.org/support/users/fujiwarayuko/)
 * (@fujiwarayuko)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/cloudfront-6/#post-16468167)
 * Thank you for your reply.
 * I understand that as long as we download PHP files to wordpress environment, 
   we can apply modification.
 * However, our company does not have PHP developer.
 * Because of that, it is better for our campany that just roll back **CloudFront**
   to ver6.1.1.
 * I will issue another ticket to know how to roll back.
 * For this issue, I would like to close.
 * Again, thank you very much.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘CloudFront’ is closed to new replies.

 * ![](https://ps.w.org/c3-cloudfront-clear-cache/assets/icon-256x256.jpg?rev=3337009)
 * [C3 Cloudfront Cache Controller](https://wordpress.org/plugins/c3-cloudfront-clear-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/c3-cloudfront-clear-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/c3-cloudfront-clear-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/c3-cloudfront-clear-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/c3-cloudfront-clear-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/c3-cloudfront-clear-cache/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [fujiwarayuko](https://wordpress.org/support/users/fujiwarayuko/)
 * Last activity: [3 years, 3 months ago](https://wordpress.org/support/topic/cloudfront-6/#post-16468167)
 * Status: resolved