Akamai Linode
Connect a Linode Object Storage bucket to give people and systems a Files.com access point to data already held in Akamai's cloud. The Remote Server uses Linode's S3-compatible API over HTTPS, with the bucket's region and an Object Storage access key identifying the connection.
A Mount exposes the bucket as a Files.com folder. A Sync transfers files between it and another location. These arrangements let an existing workload keep using Linode storage while staff or partners reach its files through Files.com accounts and permissions.
Connection Details
Select Akamai Linode when adding the Remote Server. Give the connection an identifiable Internal name for this connection and provide the following storage details.
| Setting | Value |
|---|---|
| Bucket | The Linode Object Storage bucket name, shown under Object Storage > Buckets in the Linode portal. |
| Akamai Linode region | The region containing that bucket, shown with the bucket details. |
| Access Key | The Object Storage access key from Object Storage > Access Keys. |
| Secret Key | The secret corresponding to that access key, supplied when the key was created. |
Enter the credentials directly or select a saved credential from the Remote Server Credential Manager. The key's permissions must cover the intended operations on the selected bucket.
For a bucket with network restrictions, use the connection's routing settings and source addresses to establish access. The Remote Server also offers dedicated-IP and regional-routing choices.
Transfers and Stored Objects
Eligible client uploads and downloads use Direct Routing automatically, avoiding the relay through Files.com and its Transfer Usage for those contents. Web uploads use Files.com's network. Client versions, required processing, and connection routing determine the path for a particular transfer.
Linode Object Storage is case-sensitive. Resolve names that differ only by capitalization before transferring to a case-insensitive destination, where they can identify the same file or folder.
With object versioning enabled, Linode retains previous versions. Files.com's regular listing shows current files; retained versions remain subject to Linode's recovery and lifecycle rules. Object Storage Behavior explains folder placeholders, moves, replacements, and retained content at old paths.