Takayuki Miyauchi

Okamoto Hidetaka

AMIMOTO

DigitalCube Inc.

wokamoto

John Blackbourn

Bartosz Gadomski

Hinaloe

Sander van Dragt

jepser

<p>This is simple plugin that clear all cloudfront cache if you publish posts.<br />
You can easy use CloudFront in front of WordPress.</p>
<h3>Fixtures</h3>
<ul>
<li>
<p>wp_is_mobile()<br />
Check device viewer type by CloudFront header.<br />
Now supports <code>HTTP_CLOUDFRONT_IS_MOBILE_VIEWER</code> and <code>HTTP_CLOUDFRONT_IS_TABLET_VIEWER</code>.</p>
</li>
<li>
<p>preview url<br />
In preview page, plugin add <code>post_date</code> query to avoid CloudFront cache.<br />
And set <code>wordpress_loginuser_last_visit</code> cookie for avoid CloudFront cache too.</p>
</li>
</ul>
<p>The <code>wordpress_loginuser_last_visit</code> cookie will be removed if user sign out.</p>
<h4>Invalidation(Clear Cache) Page URL</h4>
<p>This plugin send following page url to CloudFront Invalidation API.</p>
<ul>
<li>TOP page URL</li>
<li>Published Post Page URL</li>
<li>Category Archive Page URL</li>
</ul>
<h3>AWS IAM Policy Example</h3>
<pre><code>{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "cloudfront:GetDistribution",
                "cloudfront:ListInvalidations",
                "cloudfront:GetStreamingDistribution",
                "cloudfront:GetDistributionConfig",
                "cloudfront:GetInvalidation",
                "cloudfront:CreateInvalidation"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}
</code></pre>
<p><strong>Note:</strong> The <code>cloudfront:GetInvalidation</code> permission is required for viewing detailed invalidation information. If this permission is not granted, the detail view feature will be disabled gracefully without affecting other plugin functionality.</p>
<h3>Adding your configuration through env vars</h3>
<p>The plugin can be configured by defining the following variables:</p>
<ul>
<li><code>AWS_ACCESS_KEY_ID</code></li>
<li><code>AWS_SECRET_ACCESS_KEY</code></li>
<li><code>C3_DISTRIBUTION_ID</code></li>
</ul>
<p>You can put these variables like the code into the wp-config.php</p>
<pre><code>php
define( 'AWS_ACCESS_KEY_ID', '' );
define( 'AWS_SECRET_ACCESS_KEY', '' );
define( 'C3_DISTRIBUTION_ID', '' );
</code></pre>
<h3>Cookie</h3>
<p>This plugin set a Cookie named <code>wordpress_loginuser_last_visit</code> to the user.<br />
It prevents CDN caching when the user is previewing his posts or contents.<br />
Once logging out from Dashboard, plugin removes this cookie from user.</p>
<h3>7.1.0</h3>
<ul>
<li>[Feature] Add invalidation detail view with modal popup showing invalidation paths, caller reference, and status</li>
<li>[Fix] Fix invalid path returned for post type without archive page</li>
</ul>
<h3>7.0.1</h3>
<ul>
<li>[Update] Improved AWS API call processing for better security and PHP 8.x compatibility</li>
</ul>
<h3>7.0.0</h3>
<ul>
<li>[Breaking Change] Remove AWS SDK dependency and implement custom HTTP CloudFront API client</li>
<li>[Update] Add comprehensive invalidation logging with c3_log_invalidation_list filter</li>
<li>[Update] Add configurable CloudFront region and HTTP timeout settings</li>
</ul>
<h3>6.1.6</h3>
<ul>
<li>[Fix] Fixed PHP 8 syntax errors by adding nullable type hints</li>
<li>[Fix] Fixed deprecation warnings about creation of dynamic properties in Invalidation_Service.php</li>
<li>[Fix] Fixed deprecation warnings about creation of dynamic properties in Cron_Service.php</li>
<li>[Fix] Fixed PHP 7.4 syntax errors in test files</li>
</ul>
<h3>6.1.5</h3>
<ul>
<li>[Fix] Changed to install the AWS SDK using composer instead of aws.phar.</li>
</ul>
<h3>6.1.4</h3>
<ul>
<li>[Update] Support post_type_archive_link</li>
</ul>
<h3>6.1.3</h3>
<ul>
<li>[Fix] Lost filter c3_invalidation_items From v6.0.0</li>
</ul>
<h3>6.1.2</h3>
<ul>
<li>[Fix] php version compare issue</li>
</ul>
<h3>6.1.1</h3>
<ul>
<li>[Fix] Plugin deactivation issue</li>
</ul>
<h3>6.1.0</h3>
<ul>
<li>[Update] Flush cache by post_ids</li>
</ul>
<h3>6.0.0</h3>
<ul>
<li>[Breaking Change] Re-write entire code</li>
<li>[Update] Add <code>c3_log_cron_invalidation_task</code> filter to show cron job Logs</li>
<li>[Update] Add <code>c3_aws_sdk_path</code> filter to change or remove bundled AWS SDK path</li>
</ul>
<h3>5.5.1</h3>
<ul>
<li>[Update] Replace the top level menu with a Settings submenu</li>
</ul>
<h4>5.5.0</h4>
<ul>
<li>[Update] Can use defined variables for AWS Credentials</li>
</ul>
<h4>5.4.2</h4>
<ul>
<li>[Bug fix] Set cookie path in preview page</li>
</ul>
<h4>5.4.1</h4>
<ul>
<li>[Bug fix] Undefined Paths index in invalidation query cron event</li>
</ul>
<h4>5.4.0</h4>
<ul>
<li>[Update] Update preview fix plugin</li>
</ul>
<h4>5.3.4</h4>
<ul>
<li>[Bug fix] Small bug fix</li>
</ul>
<h4>5.3.3</h4>
<ul>
<li>[Change SDK] replace sdk</li>
</ul>
<h4>5.3.2</h4>
<ul>
<li>[Bug fix] Use EC2 role if using as AMIMOTO Managed hosting</li>
</ul>
<h4>5.3.1</h4>
<ul>
<li>[Add filter] Can select AWS SDK version by filter</li>
</ul>
<h4>5.3.0</h4>
<ul>
<li>[Update SDK] Use AWS SDK v3 when you using php 5.6 or later</li>
</ul>
<h4>5.2.1</h4>
<ul>
<li>[For AMIMOTO Managed] bug fix to run by WP-CLI</li>
</ul>
<h4>5.2.0</h4>
<ul>
<li>[Add filter] We can disable to register wp-cron that retry request invalidation.</li>
<li>[Readme] Update readme to see IAM Policy example.</li>
</ul>
<h4>5.1.0</h4>
<ul>
<li>[Update preview fixture] Set cookie to avoid CloudFront cache if user sign in</li>
<li>[Update preview fixture] Unset cookie for avoide CloudFront cache if user sign out</li>
</ul>
<h4>5.0.0</h4>
<ul>
<li>Support CloudFront viewer params on <code>wp_is_mobile()</code>.(4.9.0 or later)</li>
</ul>
<h4>4.4.0</h4>
<ul>
<li>Fix small bug</li>
<li>Add some feature for AMIMOTO Managed hosting user</li>
</ul>
<h4>4.3.1</h4>
<ul>
<li>Fix cron interval</li>
<li>add filters <code>'c3_invalidation_interval</code>, <code>c3_invalidation_cron_interval</code>, <code>c3_invalidation_item_limits</code>.</li>
<li>update default invalidation interval & items.</li>
</ul>
<h4>4.3.0</h4>
<ul>
<li>Schedule cron event if you published many post at the same time</li>
</ul>
<h4>4.2.1</h4>
<ul>
<li>Fix ‘c3_credential’ filter position</li>
</ul>
<h4>4.2.0</h4>
<ul>
<li>Support AMIMOT Dashboard</li>
</ul>
<h4>4.1.0</h4>
<ul>
<li>Show Invalidation Logs</li>
</ul>
<h4>4.0.3</h4>
<ul>
<li>Auto Deploy by Travis</li>
</ul>
<h4>4.0.2</h4>
<ul>
<li>Add WP-CLI param check ( wp c3 flush)</li>
<li>change transient_key</li>
</ul>
<h4>4.0.1</h4>
<ul>
<li>Bug fix ( conflict Nephila Clavata )</li>
</ul>
<h4>4.0.0</h4>
<ul>
<li>Support AWS SDK Version3</li>
<li>Remove action hook -> ‘c3_add_setting_before’<br />
use ‘c3_after_title’ filter hook instead.</li>
<li>Remove action hook -> ‘c3_add_setting_after’<br />
use ‘c3_after_auth_form’ filter hook instead.</li>
</ul>
<h4>3.0.0</h4>
<ul>
<li>Include CF Preview Fix plugin</li>
<li>Rename</li>
</ul>
<h4>2.4.3</h4>
<ul>
<li>Fix Catch Exception BUG</li>
</ul>
<h4>2.4.2</h4>
<ul>
<li>Fix CLI BUG</li>
</ul>
<h4>2.4.1</h4>
<ul>
<li>Fix CLI BUG</li>
</ul>
<h4>2.4.0</h4>
<ul>
<li>Add WP-CLI Command ( Update Settings )</li>
</ul>
<h4>2.3.0</h4>
<ul>
<li>Add WP-CLI Command</li>
</ul>
<h4>2.2.2</h4>
<ul>
<li>Force Invalidation</li>
</ul>
<h4>2.2.1</h4>
<ul>
<li>Fix Typo</li>
</ul>
<h4>2.2.0</h4>
<ul>
<li>Add Filter for using EC2 Instance Role.</li>
<li>Translationable in t.w.org</li>
</ul>
<h4>2.1.1</h4>
<ul>
<li>Fix too many invalidation url error.</li>
</ul>
<h4>2.1.0</h4>
<ul>
<li>Add hook to customize invalidation URL</li>
<li>support new invalidation url, terms.</li>
<li>Manualy invalidation button added</li>
</ul>
<h4>2.0.2</h4>
<ul>
<li>Change AWS SDK</li>
<li>code refactoring by wokamoto</li>
<li>Invalidation URL</li>
</ul>
<h4>2.0.1</h4>
<ul>
<li>Change AWS SDK</li>
<li>code refactoring by wokamoto</li>
<li>Invalidation URL</li>
</ul>
<h4>1.0</h4>
<ul>
<li>Initial released.</li>
</ul>
<h3>6.1.0</h3>
<ul>
<li>[Fix] Plugin deactivation issue</li>
</ul>


C3 Cloudfront Cache Controller

This is simple plugin that clear all cloudfront cache if you publish posts.

Angelo Mandato

Painless Analytics

<p>Welcome to FrontPup, your CloudFront companion.</p>
<p>FrontPup allows you to maximize your WordPress website using the AWS CloudFront Content Delivery Network (CDN).</p>
<h3>REQUIREMENTS</h3>
<p>You <strong>must</strong> be using the Amazon Web Services (AWS) <a href="https://aws.amazon.com/cloudfront/" rel="nofollow ugc">CloudFront</a> service to utilize this plugin.</p>
<h3>FrontPup Features</h3>
<ul>
<li>Non-intrusive Clear Cache (new) admin bar menu option, now you can clear the cache in any view without impacting other work.</li>
<li>Clear CloudFront Cache (creates an Invalidation request)</li>
<li>Set no-cache headers for all pages (great for development or testing)</li>
<li>Set public and private Cache-Control headers for caching in CloudFront and Browsers</li>
<li>Set separate max-age (browser) and s-maxage (CloudFront) cache duration values</li>
</ul>
<h3>Non-intrusive Clear Cache (new)</h3>
<p>The Non-intrusive Clear Cache admin bar menu option can clear your cache in any view without causing any disruption to your work. The <em>Clear CloudFront Cache</em> option is found under the “FrontPup” menu. Requests are performed behind the scenes. The returned status is added to the menu bar as an italics message in the menu. Feedback is reported with the icon to the left of the FrontPup menu option.</p>
<h3>Turbocharge your WordPress Website with CloudFront</h3>
<p>Using Amazon CloudFront in front of your WordPress website offers significant benefits by improving performance, security, and scalability. CloudFront is a Delivery Network (CDN) with over 750+ Points of Presence (PoPs) around the world plus over 1,100 PoPs within ISP networks. This highly optimized network makes it <em>extremely efficient</em> at delivering your website to your visitors anywhere around the world. “PoP” locations are designed to reduce latency by caching content closer to your site’s visitors.</p>
<p><strong>Performance</strong></p>
<ul>
<li><strong>Faster Loading Times</strong>, static content (pages, images, CSS, JavaScript) is cached at “edge locations” around the world</li>
<li><strong>Improved User Experience</strong>, Faster load times lead to higher user engagement, reduced bounce rates, and improved search engine optimization (SEO) rankings</li>
<li><strong>Reduced Server Load</strong>, by serving cached content from edge locations, CloudFront minimizes requests to your WordPress website</li>
</ul>
<p>When your website is optimized for performance your <a href="https://pagespeed.web.dev/" rel="nofollow ugc">PageSpeed Lighthouse scores</a> should improve.</p>
<p><strong>Enhanced Security</strong></p>
<ul>
<li><strong>DDoS Protection</strong>, includes AWS Shield Standard</li>
<li><strong>SSL/TLS Security</strong>, force https only and includes free SSL Certificates</li>
<li><strong>AWS WAF</strong>, a Web Application Firewall with a depth of options including specific WordPress protections (may incur additional costs)</li>
</ul>
<p>You should achieve a grade of “A” on <a href="https://www.ssllabs.com/ssltest/" rel="nofollow ugc">Qualys SSL Server Test</a> when CloudFront is configured with the recommended TLSv1.2_2021 or newer security policy.</p>
<p><strong>Scalability and Reliability</strong></p>
<ul>
<li><strong>Global Reach</strong> with over 750 PoPs plus over 1,100 PoPs within ISP networks</li>
<li><strong>High Availability</strong>, can serve cached content when site is down</li>
<li><strong>Cost Efficiency</strong>, can be cost-effective, especially for websites with high traffic with the new <a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/flat-rate-pricing-plan.html" rel="nofollow ugc">CloudFront flat-rate pricing plans</a></li>
</ul>
<p><strong>Technology</strong></p>
<ul>
<li><strong>IPv6</strong>, a superior protocol to IPv4 and in some regions of the world is the only protocol that is available</li>
<li><strong>HTTP/2 and HTTP/3</strong> improve web performance through faster loading speeds, enhanced security, and better resource handling</li>
<li><strong>Gzip and Brotli compression</strong>, smaller file sizes improve application performance by delivering your content faster to visitors</li>
<li><strong>Multi-Proxy</strong>, route specific path patterns to other web applications easily by adding additional “Origins”, allowing you to host more than just WordPress with the same hostname</li>
</ul>
<p>Learn more about <a href="https://aws.amazon.com/cloudfront/" rel="nofollow ugc">AWS CloudFront</a>.</p>
<h3>Developed by an AWS Community Builder</h3>
<p>FrontPup is developed and maintained by <a href="https://angelo.mandato.com" rel="nofollow ugc">Angelo Mandato</a>, an <a href="https://builder.aws.com/community/@angelomandato" rel="nofollow ugc">AWS Community Builder</a>. Angelo has been developing WordPress plugins and themes since 2005 and has been architecting applications including WordPress hosted on Amazon Web Services since 2007.</p>


FrontPup

Your AWS CloudFront companion. Clear cache and optimize your CloudFront distribution for your WordPress website

C3 Cloudfront Cache Controller vs FrontPup