Connect Akamai (Linode) Object Storage to WordPress

1. 1

   Create the bucket

   In Cloud Manager, go to Object Storage and select Create Bucket.

   Label: lowercase letters, numbers, hyphens and periods. If you want files served from your own domain (see the domain step), the label must be that full domain name, for example media.yoursite.com.

   Region: pick the one closest to most of your visitors and enter the same region in Offloft.

   Bucket label

   my-site-media

   Copy

   Open Akamai (Linode)'s consoleAkamai (Linode)'s documentation

2. 2

   Create an access key for this bucket

   Go to Object Storage, open the Access Keys tab and select Create Access Key. Pick the bucket's region.

   Turn on Limited Access and set "my-site-media" to Read/Write, leaving every other bucket at None. A key's permissions cannot be changed later; you would make a new key.

   Copy the Access Key and the Secret Key into Offloft, then select I Have Saved My Secret Key. The secret is shown only once.

   Open Akamai (Linode)'s consoleAkamai (Linode)'s documentation

3. 3

   Let visitors read the files

   Files are private unless each file is marked public. Offloft marks every file it uploads as public; the delivery check confirms it works. There is nothing to switch on.

   Leave the bucket's own access setting on Private, so visitors can open a file but cannot list the bucket.

   Open Akamai (Linode)'s consoleAkamai (Linode)'s documentation

4. 4

   Serve files from your own domainOptional

   This needs a bucket labelled with the full domain name, for example media.yoursite.com (a subdomain; the bare domain does not work).

   At your DNS provider, add a CNAME record for media.yoursite.com pointing to media.yoursite.com.your-region.linodeobjects.com.

   In Cloud Manager, open the bucket's SSL/TLS tab, paste your certificate and private key for the domain and select Upload Certificate.

   In Offloft, use https://media.yoursite.com as the delivery address.

   CNAME target

   media.yoursite.com.your-region.linodeobjects.com

   Copy

   Delivery address

   https://media.yoursite.com

   Copy

   Open Akamai (Linode)'s consoleAkamai (Linode)'s documentation

5. 5

   Allow your site to read files (CORS)Optional

   This step is optional. Images on your pages load without it. You need it only when your site's own scripts read files from storage, for example image editors, web fonts or 3D viewers. The rule below lets only your site read files, and only read them.

   Object Storage sets CORS through its S3 API. With the AWS CLI configured for this key, run the command below.

   AWS CLI command

   aws s3api put-bucket-cors --bucket my-site-media --endpoint-url https://your-endpoint --cors-configuration '{"CORSRules":[{"AllowedOrigins":["https://yoursite.com"],"AllowedMethods":["GET","HEAD"],"AllowedHeaders":["*"],"MaxAgeSeconds":3600}]}'

   Copy

   Akamai (Linode)'s documentation

6. 6

   Run the connection test and the delivery check

   In Offloft, paste your values and run the connection test. It checks your credentials, finds the bucket, uploads a test file, reads it back and deletes it. The delivery check then loads a small test image from your public address. Offloft serves nothing from the cloud until both pass.

The steps above match the guide inside the plugin, checked against Akamai (Linode)'s documentation on 2026-10-26. Example values are shown here; the plugin fills in your own.