CloudFront

  • Resolved fujiwarayuko

    (@fujiwarayuko)


    2 years, 3 months ago

    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”; 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 SenderInvalidArgumentYour request contains one or more invalid invalidation paths.a1fc1ecd-18c3-4780-929f-20543c30ed1f’

    • This topic was modified 2 years, 3 months ago by fujiwarayuko.
    • This topic was modified 2 years, 3 months ago by fujiwarayuko.
    • This topic was modified 2 years, 3 months ago by fujiwarayuko.
    • This topic was modified 2 years, 3 months ago by fujiwarayuko.
Viewing 2 replies - 1 through 2 (of 2 total)

  • 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

    Thread Starter fujiwarayuko

    (@fujiwarayuko)

    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.