📘

This page is deprecated

The Limited Availability (LA) release in London, Singapore, and Melbourne successfully completed on January 13, 2025. These endpoints are now Generally Available (GA). As a result, you can find the product documentation previously available on this page in the following locations:

Supported endpoint types by region
Product Limits

The remaining regions, Frankfurt, Seattle, and Mumbai will remain in LA and are also supported using the public product documentation.

If you have any questions please feel free to reach out to your account team or contact support.

Limited Availability notes

The following notes apply during the Limited Availability period of November 18, 2024 to January 13, 2025.

• Content will be charged at the standard rates specified on the pricing page.
• All support requests should follow the standard support process.
• S3 endpoint hostnames for the new E2 and E3 endpoints that you have been approved to use will be provided to you
• Bucket names must be unique across all endpoints within a region
  • For example, in Seattle, if you or any other customer has a bucket within the region that has the same name of a bucket that is being created, the create bucket request will fail with a 429 response code.

Known Issues

• The bucket rate limits on the Create Bucket page in Cloud Manager are greyed out and cannot be selected
  • If bucket rate limit increases are required please open a support ticket
• The bucket rate limits on Bucket Properties page in Cloud Manager are greyed out, cannot be selected, and do not reflect approved rate limit increases
  • Rate limit increases will be confirmed in the support ticket request
• If access keys are created without a region specified when using the linode-cli, the new E2 and E3 endpoints may not be automatically included in the key scope. To workaround this issue, and as best practice, you should always define the region(s) in scope for the key when it is created.
  • The list of regions to use during access key creation can be found in the region column of the table within the Supported endpoint types by region section.

Example: Creating an access key for 1 region:

linode-cli object-storage keys-create --label "my-new-access-key" --regions us-sea

Example: Creating an access key for multiple regions:

linode-cli object-storage keys-create --label "my-new-access-key" --regions us-sea --regions de-fra-2

• You cannot currently create Limited Access keys for E2 and E3 endpoints using Cloud Manager
  • For instructions on how to create Limited Access keys using the Linode CLI go to Create Limited Access keys using the Linode CLI.

More information on how to get started with Object Storage can be found in the Object Storage product documentation.

👍

The content below is a preview of the new documentation that will be available in January of 2025.
If you have any feedback, please use Suggest Edits at the top of this page.

Endpoint types

An endpoint type defines the performance and limits when working with content stored on that endpoint. All endpoints have an assigned type of E0, E1, E2, or E3.

In any region that has more than one endpoint type we recommend using the endpoint with the highest performance and scale. For example, in Seattle, please choose the E3 endpoint over the E1 endpoint for all new content to gain the performance and scale benefits of the E3 endpoint.

The Object Storage product limits topic in this guide provides the performance and limits and for each endpoint type.

Supported endpoint types by region

Review the table below to see which regions support each of the available endpoint types.

👍

Some regions support more than one endpoint. You should select the highest standard endpoint available when creating a new bucket. E3 endpoints offer the highest performance and capacity, followed by E2, then E1.

*This endpoint is in Limited Availability status, if you would like to request access please open a support ticket.

Supported features by endpoint type

Feature support is consistent across endpoints, with the exception of the following three items.

*For static website support you should use the CDN vs. supporting out of Object Storage directly.

Product limits

Object Storage limits by endpoint type

Note 1: Lifecycle Policy deletes execute over a 24 hour period. The Lifecycle delete rate per second, per bucket, is the maximum rate that can be expected over a 24 hour period.

Multi-part uploads

The maximum upload size of a single object is 5 GB. You can use multi-part uploads to upload an object that exceeds this limit. Both s3cmd and Cyberduck will do this for you automatically as part of the upload process.

Bucket rate limits

Bucket rate limits specify the maximum Requests Per Second (RPS) for an endpoint. The rate limits for E0 and E1 endpoints are calculated differently than the E2 and E3 endpoints.

• For E0 and E1 endpoints all operations count towards one rate limit for the bucket.
• For E2 and E3 endpoints there are separate rate limits for each operation.

*Contact support to request an increase to the default RPS, per bucket.

Optimize to avoid rate limiting

The rate limit for the number of RPS applies to a bucket and is evaluated against each bucket once per second. If the duration of any request is greater than one second, any open requests will count against the rate limit in the next one second window.

For example, assume there are 750 requests for a single bucket with a duration of two seconds each. All of the requests that do not complete within the first second will count against the rate limit in the next second. With a rate limit of 750 RPS for the bucket, no additional requests can be processed within the two second window until the first 750 requests complete. Any requests that are rate limited will receive a 503 response.

To help avoid rate limiting you can structure your data across multiple buckets, each of which will have its own rate limit.

Create a bucket

One of the first steps to using Object Storage is to create a bucket. Here's how to create a bucket using Cloud Manager. Cloud Manager support for creating buckets is available on December 16, 2024. You can also use the Linode CLI, s3cmd, and s4cmd.

1. Navigate to the Object Storage page in Cloud Manager (see View buckets).

2. Click the Create Bucket button to open the Create Bucket panel. If you have not created an access key or a bucket on this account, you are prompted to enable Object Storage.

   📘

   Billing starts as soon as Object Storage is enabled on the account. See Object Storage Pricing for more detail on the minimum flat-rate and per GB charge. See Cancel Object Storage for instructions on cancelling this service.

3. Within the Create Bucket form, add a Label for the new bucket. This label must be unique and should not be used by any other bucket (from any customer) in the selected region. Keep the following requirements in mind:

• Must be between 3 and 63 characters in length.
• Can only contain lower-case characters, numbers, periods, and dashes.
• Must start with a lowercase letter or number.
• Cannot contain underscores (_), end with a dash (-) or period (.), have consecutive periods (.), or use dashes (-) adjacent to periods (.).
• Cannot be formatted as IP addresses.
• You cannot upload files to Object Storage that contain the following characters, " ' < > & + = when using Cloud Manager or the Linode CLI.

📘

If you intend to use this bucket with a custom domain, the bucket must be labeled as your fully qualified domain name, such as assets.example.com or any subdomain of *.your-domain.tld.

4. Choose a Region for the bucket to reside. See the Availability section on the Object Storage Overview page for a list of available regions.
5. Review the Endpoint Type information.

Most regions only support one endpoint type. For these regions the endpoint type information is read only. There are, however, a few regions that support more than one endpoint type. You should select the highest option available to take advantage of the greater performance and capacity limits.

To learn more, go to the Endpoint types section in this guide. You can also review the Product limits topic to review the performance, capacity, and rate limits available for each endpoint type.

6. Click Submit to create the bucket.

You are now ready to upload files to the bucket.

Object Storage pricing

There are three components to Object Storage pricing:

• Content stored
• Network transfer
• Request pricing

Content stored

Object Storage costs a flat rate of $5 a month, and includes 250 gigabytes of storage. This flat rate is prorated, so if you use Object Storage for a fraction of the month you are charged a fraction of the cost. For example, if you have Object Storage enabled for half of the month and use up to 250 gigabytes of storage you are billed $2.50 at the end of the month. The default cost of storage per gigabyte over the first 250 gigabytes is $0.02, and this usage is also prorated based on usage time.

Storage overages for Object Storage vary by data center due to regional infrastructure costs. The below table includes overage costs for different data centers where Object Storage is available:

Once you enable Object Storage you will be billed at the flat rate regardless of whether or not there are active buckets on your account. You must Cancel Object Storage to stop billing for this service.

Network transfer

You can find details on network transfer pricing in the Network transfer usage and costs guide.
Network transfer overages for Object Storage vary by data center due to regional infrastructure costs. The below table includes overage costs for different data centers where Object Storage is available:

📘

If creating a bucket in our Jakarta or São Paulo data centers, note that no additional transfer is added to their region-specific transfer pools

Request pricing

With the introduction of the high-performance E2 and E3 endpoints, we will be introducing charges for requests to the Object Storage service. To allow our customers time to optimize usage of object storage prior to the introduction of this new pricing, charges will appear on Object Storage bills no earlier than October 1, 2025.

Requests charges are organized by Class A and Class B requests. Class A operations include requests to write content (PUT) and high overhead operations such as LIST. Class B operations include read requests (GET) and operations with lower overhead.

Both Class A and Class B include a base quota of free operations per month.

A full list of all operations by S3 API and their mapping to class A and B will be provided at a later date.

Free Operations

Delete operations are always free.