Skip to the products
LCPanelLicence Center Panel

Amazon S3 File Storage

Amazon S3 in every region with signed direct downloads and direct uploads, and a Connection Test page for every bucket-type server with the CORS rule. Free.

Plugins Updated 6 Nov 2026 27 / 50

BoxPuff can keep every file in an Amazon S3 bucket, or in any service that speaks the S3 protocol, instead of on the web server's own disk. Downloads then go straight from the bucket to the visitor with a signed, expiring link, and uploads can go straight from the browser into the bucket in parallel pieces - the web server only hands out tickets. Your site runs on a small host while the files, and the bandwidth, live with Amazon.

The core already contains the S3 driver and the Amazon S3 server type. This plugin completes it: it fills in Amazon's full region list and the correct per-region endpoint, and adds an S3 Connection Test page that checks every bucket-type file server with one click and prints the CORS rule a bucket needs for direct uploads. The same page tests the buckets of the premium presets (Wasabi, Backblaze B2, DigitalOcean Spaces, Contabo, Minio, Filebase, Cloudflare R2), which all use this driver.

Who it is for

Any site that will outgrow one disk, or that wants downloads served from Amazon's network rather than its own line. Also anyone whose host charges for bandwidth but not for a small PHP site.

Switching it on

Amazon S3 File Storage is free and works with every licence; a fresh install switches it on. Otherwise open Admin → Extensions → Plugins (Manage Plugins) and switch it on. Its page appears under Extensions as S3 Connection Test (/admin/plugin/storage-s3). The plugin has one setting of its own: Direct upload piece size (MB) (32; Amazon needs at least 5).

Making the bucket

In the AWS console: create a bucket (keep Block all public access on - BoxPuff signs every link), then an IAM user with programmatic access and a policy allowing s3:PutObject, s3:GetObject, s3:DeleteObject, s3:ListBucket and the multipart calls on that bucket. Note the access key and secret.

For Direct Uploads the bucket also needs a CORS rule, because the browser will PUT pieces to it from your site's address. The Connection Test page prints the exact rule for your site; it looks like

[
  {
    "AllowedOrigins": ["https://your-site"],
    "AllowedMethods": ["GET", "PUT", "POST", "HEAD"],
    "AllowedHeaders": ["*"],
    "ExposeHeaders": ["ETag"],
    "MaxAgeSeconds": 3000
  }
]

Paste it under the bucket's Permissions → Cross-origin resource sharing (CORS).

Adding the file server

Infrastructure → File Servers → Add File Server, type Amazon S3. Besides the common fields of every server (label, status, CDN, max storage, priority, geo and account-type targeting; see File servers) the type asks for:

FieldWhat it is
Access Key, Secret KeyThe IAM user's keys.
BucketThe bucket name.
RegionA list of every Amazon region (us-east-1, eu-central-1, ap-south-1, ...). The endpoint s3.{region}.amazonaws.com is filled from it.
EndpointHost name only; change it only for an S3-compatible service that is not Amazon.
Path-style URLshttps://endpoint/bucket/key instead of https://bucket.endpoint/key. Off for Amazon.
Key PrefixAn optional folder inside the bucket, e.g. files/.
Direct Downloads (on)Send downloaders straight to the bucket with a signed link. Off: every file streams through the site, slower but the bucket stays hidden.
Direct Uploads (on)Browsers upload straight into the bucket in parallel pieces (needs the CORS rule). Off: pieces land on the site first and the site copies the file up.
Public / CDN URLA CloudFront or other CDN in front of the bucket; public links are served from here.
Signed Link Lifetime (3600)Seconds a signed download link stays valid.

Press Save and test: the driver writes a tiny test object, deletes it and reports Connected to … and wrote a test object, or the bucket's own error text.

How uploads and downloads flow

With Direct Uploads on, the fast road described in Uploads changes shape: the site starts a multipart upload, the browser asks for one presigned PUT address per piece and sends the pieces to the bucket side by side, then the site completes the multipart upload, checks the bucket holds exactly the file's size, and records the file. Nothing passes through PHP. Pieces are at least 5 MB.

A download token still comes from the site (so limits, countdown pages and the download tracker all apply - see Downloads); the visitor is then redirected to a signed bucket link that dies after Signed Link Lifetime. The setting Site Settings → File Downloads → Direct bucket links only for unlimited speed streams a package with a speed cap through the site instead, so the cap can be applied.

Storage keys inside the bucket follow the file's hash (9c/9cfc…) with the extension added, or userid/name when Storage filename structure is User Id/Original Filename.

The S3 Connection Test page

Lists every bucket-type file server (Amazon and the presets) with its type, bucket and endpoint, a Test connection button per server, and the CORS rule block for the first bucket. Use it after rotating keys or changing a bucket policy.

Tips

  • Keep the local server too and use the selection method under Site Settings → File Uploads (or account-type targeting on the server) to decide who lands in the bucket - free accounts on cheap local disk, premium on S3, for example.
  • Amazon charges for egress; for a download-heavy site the presets with free egress (Wasabi, Cloudflare R2, Backblaze) cost far less and plug into the same driver.
  • When Direct Uploads fails with a CORS error in the browser console, the rule's AllowedOrigins does not match your site exactly (scheme, www, port).
  • Thumbnails and the trash purge still run on the main server and the cron: deletes are queued in Files → Action Queue and sent to the bucket by process_file_queue.
Was this helpful?
Share this chapter