ze3kr

<p>If you blog are using CloudFront on the main WordPress domain (e.g. www.example.com), and you want to cache HTML page for not logged in user. You could set a long “Default TTL” for these HTML pages if the cache could invalidate automatically.</p>
<h4>Invalidation behaviors</h4>
<ul>
<li>Invalidate the whole cache when a new post published</li>
<li>Invalidate a post page when a post updated</li>
<li>Invalidate a post page if have any comment has changed on that page</li>
<li>Each invalidation has a minimum interval of 10 minutes</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>PHP 5.4+</li>
<li>WordPress 4.4+</li>
<li>A CloudFront account and AWS Access Key and Secret Key to access <a href="https://tlo.xyz/create-cloudfront-distribution-for-wordpress/" rel="nofollow ugc">CloudFront distribution</a>.</li>
</ul>
<h4>Recommendations</h4>
<ul>
<li>Offload CSS, JS and medias file to another domain with a different distribution, because this plugin will invalidate the whole cache when updating the post.</li>
</ul>


Full Site Cache for CloudFront

This plugin can invalidate the cache automatically if you are using full site CDN.

kodeala

<p>RocketFront Connect simplifies cache management and ensures optimal content delivery by connecting WP Rocket Cache with AWS CloudFront through C3 Cloudfront Cache Controller. This plugin requires both WP Rocket and C3 Cloudfront Cache Controller to be installed and activated. With this integration, CloudFront cache is automatically cleared whenever WP Rocket cache is cleared, guaranteeing that your website’s content remains up-to-date and is delivered swiftly to your users.</p>


RocketFront Connect

Automate AWS CloudFront CDN clearing and cache management by seamlessly integrating the WP Rocket plugin with C3 Cloudfront Cache Controller.

Full Site Cache for CloudFront vs RocketFront Connect