Create, modify, and delete an OSS accelerator

Prerequisites

OSS accelerators are supported in the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Ulanqab), China (Shenzhen), Singapore, US (Virginia), and China (Hong Kong).

Considerations

• The accelerated endpoint of an accelerator provides access only over an internal network. To cache OSS data accessed over the Internet, use a CDN service.

• An accelerator supports cross-zone access within the same region. Cross-zone access introduces network latency. For optimal performance, deploy your computing services in the same zone as the accelerator.

• The cached data in an OSS accelerator is a single replica. If the cache hardware fails, the data must be reloaded from OSS. Access is slower until the data is reloaded.

• You can modify an accelerator's capacity only once per hour. For example, if you create an accelerator or modify its capacity at 08:10:00, you can modify the capacity again only after 09:10:00.

Create accelerator

1. Create an accelerator.

   1. Log on to the OSS console.

   2. In the left-side navigation pane, click Buckets. On the Buckets page, find and click the desired bucket.

   3. In the left-side navigation pane, choose Bucket Settings > OSS Accelerator.

   4. On the OSS Accelerator page, click Create Accelerator.

   5. In the Note dialog box, read the terms of service and click Next.

   6. In the Create Accelerator panel, select a Zone supported by the accelerator in the region where the target bucket is located, configure the Capacity, and then click Next.

      Important

      • You can modify an accelerator's capacity only once per hour. For example, if you create an accelerator or modify its capacity at 08:10:00, you can modify the capacity again only after 09:10:00. If you find that the capacity is incorrectly configured immediately after you create an accelerator, you can delete the accelerator, create a new one, and configure its capacity.

      • Configure the capacity of the accelerator based on your business requirements. For example, you have 50 GB of hot data. The data volume is expected to increase by 20% to 30% in the coming months due to rapid business growth. In this case, you can set the capacity to a value from 70 GB to 80 GB.

2. Create an accelerated path.

   1. In the Create an accelerated path panel, configure the following parameters.

      Parameter	Description
      Acceleration Policy	Select an acceleration policy for the accelerator. Paths: Specify the directory access paths. You can add up to 10 paths. After you specify the paths, the accelerator accelerates only the files whose paths start with the specified prefixes. If you need to accelerate only a few critical directories and want to control costs, select Paths to allocate acceleration resources more precisely and avoid waste. Entire Bucket: Accelerates all files in the bucket. If your business requires high access speeds for all files in the bucket and cost is not a concern, you can select Entire Bucket to ensure comprehensive high-performance access.
      Synchronous Cache Warmup	After you enable synchronous cache warmup, when you write data to OSS by using the accelerated endpoint of an OSS accelerator, the data is written to both the OSS bucket and the OSS accelerator cache. On subsequent reads, you access the accelerator cache through the accelerated endpoint for lower latency. In synchronous cache warmup mode, a regular OSS endpoint provides access only to the OSS bucket, not the accelerator cache. Enable synchronous cache warmup for scenarios that are sensitive to user experience and require high real-time performance with frequent read and write operations. This feature is not recommended for cost-sensitive scenarios that do not have strict latency requirements, involve frequent writes but infrequent reads, or contain large volumes of data that can lead to high storage costs.

   2. After you complete the configuration, click Next. In the Confirm Billable Items dialog box, click OK.

3. Create a batch prefetch task (Optional).

   The batch prefetch feature asynchronously imports OSS data into the accelerator cache. This reduces latency for subsequent data access. If you do not want to use this feature now, click OK to skip this step and finalize the accelerator creation.

Modify accelerator capacity

1. Log on to the OSS console.

2. In the left-side navigation pane, click Buckets. On the Buckets page, find and click the desired bucket.

3. In the left-side navigation pane, choose Bucket Settings > OSS Accelerator, and then in the Actions column, click Details.

4. On the accelerator details page, in the Basic Information section, click the icon next to Capacity.

5. In the Edit OSS Accelerator panel, modify the Capacity and click OK.

   Important

   You can modify its capacity only once per hour. For example, if you create an accelerator or modify its capacity at 08:10:00, you can modify the capacity again only after 09:10:00.

6. In the confirmation dialog box that appears, click OK.

Delete accelerator

Deleting an accelerator clears only its cache. Data in the source OSS bucket is not affected.

1. Log on to the OSS console.

2. In the left-side navigation pane, click Buckets. On the Buckets page, find and click the desired bucket.

3. In the left-side navigation pane, choose Bucket Settings > OSS Accelerator.

4. In the OSS accelerator list, click Delete in the Actions column. Alternatively, click Details to go to the OSS Accelerator page. In the Basic Information section, click the icon in the upper-right corner.

5. In the dialog box that appears, enter the name of the accelerator and click OK to delete it.

Next steps

You can use an OSS accelerator with common OSS developer tools and OSS SDKs. For more information, see Use an accelerator.