Manual Cache Clearing
One-click cache invalidation from the WordPress admin. Instant feedback on success or failure. Displays the date and time of the last successful clear.
Lightsail CDN Cache Manager gives you complete control over your AWS Lightsail CDN cache from the WordPress admin. Clear manually, invalidate automatically on publish, or schedule recurring clears β no AWS Console required.
Three ways to clear cache β whichever fits your workflow.
One-click cache invalidation from the WordPress admin. Instant feedback on success or failure. Displays the date and time of the last successful clear.
Fires a full CDN invalidation automatically whenever a post or page is published or updated. Choose exactly which post types trigger the clear β including custom post types.
Set up recurring cache clears on a fixed interval (every 5 minutes to 24 hours), on specific days of the week, or on specific dates each month. Uses your WordPress timezone.
When scheduling is active, a live countdown timer shows exactly how long until the next cache clear β with the precise date and time displayed alongside it.
AWS credentials are defined as constants in wp-config.php β never stored in the database. The access key is masked in the admin UI after entry. All API calls use AWS Signature Version 4.
At-a-glance status panel showing your AWS connection state, auto-clear toggle, active schedule mode, and the last time cache was successfully cleared.
Verify your AWS access key, secret key, and Lightsail distribution name with one click β calls the read-only Lightsail API and never touches your cache, so you know it's working before you rely on it.
No SDK. No AWS Console after setup. Just four constants and you're done.
Search for Lightsail CDN Cache Manager in the WordPress plugin directory, install, and activate. Or download the ZIP from WordPress.org and upload manually.
Add four constants to wp-config.php: your AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_DEFAULT_REGION, and LIGHTSAIL_DISTRIBUTION_NAME.
Go to Settings β Lightsail Manager. Clear cache manually, enable auto-clear for specific post types, or configure a recurring schedule β all from one tab-based admin panel.
Your IAM user needs two Lightsail actions: lightsail:GetDistributions and lightsail:ResetDistributionCache. Create a custom IAM policy with only these two actions for minimal permissions.
Credentials are defined as PHP constants in wp-config.php β they are never written to the database. The admin panel displays only the last four characters of the access key for verification. All API calls go directly from your server to AWS; nothing passes through ByteCore Stack servers.
Yes. The plugin uses the ResetDistributionCache API action, which is the standard way to invalidate a Lightsail CDN distribution. You need an active Lightsail distribution and its exact distribution name from the AWS Lightsail console under Networking β CDN distributions.
No. This plugin is built specifically for AWS Lightsail CDN distributions. CloudFront uses a different API. A separate BCS CloudFront Manager is on the roadmap for Q4 2026.
Yes. The Schedule tab offers three modes: Interval (every 5 minutes to 24 hours), Weekly (specific days of the week at a set time), and Monthly (specific dates each month at a set time). All times use your WordPress timezone setting. A live countdown timer shows when the next clear will run.
No. Auto-clear only fires when a post reaches publish status. WordPress autosaves and draft saves are ignored. Media attachments are also excluded regardless of your post type selection.
Use the Test Connection button on the Configuration tab. It calls the read-only lightsail:GetDistributions action to verify your access key, secret key, and distribution name β without clearing your cache β and tells you exactly what's wrong if something fails.
Yes β always. Lightsail CDN Cache Manager is 100% free and GPL v2 licensed, with no paid tier, no feature gating, and no upsell β consistent with all other ByteCore Stack plugins.
Free, open source, and live on WordPress.org.
Install in seconds β no accounts, no subscriptions, no upsell.