Kybern S3 Storage

Kybern S3 Storage can keep regular WordPress Media Library files local while offloading attachments matched by configured Fluent Forms routing rules. It can also use one FileBird folder as the local exception: attachments assigned to any other FileBird folder are queued for S3 offload, while unfiled uploads remain local until an editor assigns a folder. Offloaded attachment URLs remain usable from WordPress, and the plugin can restore them back into local uploads later if you need a fallback.

It also adds optional Fluent Forms, FileBird, and protected PDF upload workflows:

• Route selected Fluent Forms IDs into custom upload subdirectories such as documents.

• Offload only those routed uploads into your S3 root prefix.

• Assign matching Media Library attachments into a chosen FileBird folder.

• Auto-create FileBird folders by name when a rule does not specify a folder ID.

• Generate signed URLs for private buckets.

• Preserve old /wp-content/uploads/... links for offloaded private files by redirecting them through signed S3 URLs.

• Use CloudFront-compatible public delivery URLs for public buckets.

• Queue migration batches in WordPress cron instead of one browser request.

• Restore offloaded Media Library files from S3 back into local WordPress uploads with one recovery action.

• Retry failed migration items without rerunning the whole library.

• Export and import non-secret plugin settings as JSON without exposing AWS credentials.

• Test your S3 credentials and permissions before migrating.

The plugin adds a settings page where you can configure:

• Bucket name

• Region

• Optional custom endpoint

• Optional public base URL or CDN URL

• Optional CloudFront base URL

• Root S3 prefix such as example.com/media-library

• Whether local copies of routed uploads should be deleted after successful upload

• A Local FileBird Folder ID that keeps one folder on the server while all other assigned FileBird folders offload to S3

• Whether S3 offload is limited to Form Routing Rules when no Local FileBird Folder ID is configured

• Whether private-bucket signed URLs should be used

• Per-form Fluent Forms routing rules

• Which FileBird folder should receive matching uploads, by ID or by auto-created folder name

• Multiple dedicated FileBird folders for Circulars, with year-based S3 keys such as circolari/2026/1234-circolare.pdf

• An administrator-only, resumable Circulars reorganisation tool for already offloaded PDFs

• An administrator-only, read-only S3 Delivery Health audit with background batches, status, and retryable failed checks

• An opt-in five-minute Circulars S3 incoming importer for verified direct S3 PDF uploads

• An authenticated KybernAI callback for registering a PDF already uploaded to its final Circulars S3 path

External services

This plugin connects to an S3-compatible object storage service that you configure, such as Amazon S3 or another provider with an S3-compatible API.

It sends:

• Uploaded file contents when offloading Media Library items or workflow-specific uploads

• File names, MIME types, and object keys derived from your WordPress upload paths

• Request metadata required by the S3 API, including bucket name, region, endpoint path, and AWS Signature V4 authorization headers generated from your configured credentials

This happens only when you:

• Run the S3 connection test

• Offload new or existing files to your configured bucket

• Delete remote objects during cleanup

• Recover an offloaded file back into local WordPress uploads

Service providers may include:

• Amazon S3: https://aws.amazon.com/s3/

• Any S3-compatible endpoint you configure yourself

If you use Amazon S3, review:

• AWS Customer Agreement: https://aws.amazon.com/agreement/

• AWS Service Terms: https://aws.amazon.com/service-terms/

• AWS Privacy Notice: https://aws.amazon.com/privacy/

If you use another S3-compatible provider, review that provider’s terms of service and privacy policy before enabling offload.