When long-distance data transfers are required, transfer acceleration provides an end-to-end acceleration solution for uploads and downloads through globally distributed cloud data centers and intelligent routing. It optimizes issues such as high latency and unstable transmission in cross-region access, improving transfer speed and user experience.
How it works
When a user accesses a bucket through a transfer acceleration domain, the request is intelligently routed to the nearest Alibaba Cloud access point. The data is then transmitted at high speed to the region where the target bucket is located over the Alibaba Cloud internal backbone network, avoiding long-distance transmission over the public Internet.
For example, when a user in Beijing accesses a bucket in Chengdu: the regular public endpoint requires multiple hops over the public Internet. When the transfer acceleration domain is used, data enters the Alibaba Cloud access point in Beijing and is directly transmitted to Chengdu over the internal backbone network, reducing the public Internet transmission distance and improving speed and stability.
Transfer acceleration improves speed and stability by optimizing the transmission link, but it cannot completely eliminate the impact of public Internet and cross-border network fluctuations. The actual acceleration effect is affected by factors such as the user's geographic location, carrier link quality, and network congestion, particularly in cross-border scenarios.
Enable transfer acceleration access
Step 1: Enable transfer acceleration
-
Go to the Bucket List and click the target bucket.
-
In the left-side navigation pane, click .
-
Click the enable icon on the right of Transfer Acceleration, carefully read the prompt in the pop-up window, and then click OK.
After transfer acceleration is enabled, it takes approximately 30 minutes for the configuration to take effect globally. Perform the verification test after the configuration takes effect.
After transfer acceleration is enabled, the original bucket domain (such as the public endpoint) remains functional. You can flexibly choose the optimal access method based on user geographic location and network conditions.
Step 2: Use the transfer acceleration domain to access
After transfer acceleration is enabled, you must replace the endpoint in access requests with the transfer acceleration domain (oss-accelerate.aliyuncs.com) to benefit from acceleration.
Unregistered custom domains cannot be resolved to IP addresses in the Chinese mainland. To use a CNAME record for transfer acceleration with an unregistered custom domain, point the CNAME record to the transfer acceleration domain outside the Chinese mainland (oss-accelerate-overseas.aliyuncs.com).
Public-read and public-read/write buckets
Access the bucket directly through a URL in a browser. For example, https://example-bucket.oss-accelerate.aliyuncs.com/example.jpg accesses the file example.jpg in example-bucket.
Private buckets
To access a private bucket, the file URL must include signature information. The following procedure demonstrates how to obtain the signed URL of a file in the console. For more information about signatures and how to generate them, see (Recommended) V4 signatures in presigned URLs.
-
Go to the Bucket List and click the target bucket.
-
Click Details in the Actions column of the target file.
-
Click Copy Object URL, and replace the public endpoint (such as
oss-cn-hangzhou.aliyuncs.com) in the URL with the transfer acceleration domain (oss-accelerate.aliyuncs.com). -
Access the modified URL in a browser.
When accessing OSS using SDKs, ossutil, ossbrowser, or other tools, configure the endpoint as oss-accelerate.aliyuncs.com without the bucket name. If you mistakenly configure the endpoint as <BucketName>.oss-accelerate.aliyuncs.com, domain resolution will fail.
Test the acceleration effect
The following example demonstrates the actual effect of transfer acceleration by using ossutil on an ECS instance in the Japan (Tokyo) region to download a file from the China (Hangzhou) region.
Without acceleration
ossutil cp oss://example-bucket/ossutil-2.1.2-mac-arm64.zip ossutil-2.1.2-mac-arm64.zip -e oss-cn-hangzhou.aliyuncs.com
The download took the following amount of time:
Success: Total 1 object, size 9281195 B, Download done:(1 files, 9281195 B), avg 8.733 MiB/s
1.013983(s) elapsed
With acceleration
ossutil cp oss://example-bucket/ossutil-2.1.2-mac-arm64.zip ossutil-2.1.2-mac-arm64.zip -e oss-accelerate.aliyuncs.com
The download took the following amount of time:
Success: Total 1 object, size 9281195 B, Download done:(1 files, 9281195 B), avg 20.155 MiB/s
0.440160(s) elapsed
Apply to production environments
Best practices
-
CDN with transfer acceleration: A multi-layer acceleration architecture
You can configure both CDN acceleration and transfer acceleration at the same time. Configure the CDN origin-pull to point to the transfer acceleration domain to build a dual-acceleration system of "CDN edge caching + OSS transfer acceleration". CDN handles caching and responding to user requests at the nearest edge node, while transfer acceleration optimizes the CDN origin-pull link. This is particularly suitable for global distribution of static resources, achieving full-link optimization of both cache hits and origin-pull transmission.
-
Large file transfer optimization: Combining multipart upload with acceleration
For GB- or TB-level large file transfers, combine transfer acceleration with Multipart upload and Resumable download to form a complete long-distance large file transfer solution. Transfer acceleration optimizes the network link quality, while multipart upload and resumable download improve concurrency and fault tolerance. The combination of both significantly reduces the risk of transfer timeouts and improves overall transfer efficiency.
-
Cost optimization: An intelligent domain selection strategy
Implement differentiated domain strategies for different user groups and access scenarios. For users in the same region or with good network conditions, use the public endpoint to save transfer acceleration costs. For users across regions or with poor network quality, use the transfer acceleration domain to improve the experience. We recommend that you develop a domain selection strategy based on the geographic distribution of users, business criticality, and cost budget.
Fault tolerance strategy
-
Domain degradation mechanism
When the transfer acceleration domain encounters access issues, your application should be able to automatically degrade to the public endpoint to ensure business continuity. The transfer acceleration service and the public endpoint are independent of each other. A failure in one does not affect the normal use of the other, providing dual protection for your business.
Quotas and limits
|
Item |
Description |
|
Supported protocols |
The transfer acceleration domain supports only API access over HTTP/HTTPS. Non-HTTP/HTTPS protocols such as RTMP are not supported. |
|
Time to take effect |
Enabling or disabling transfer acceleration takes approximately 30 minutes to take effect globally. |
|
Access mode |
The transfer acceleration domain supports only the third-level domain access mode with a bucket name. It cannot be used for management operations such as listing buckets. Use the public endpoint for management operations. |
|
Secure transmission |
The transfer acceleration backend may use HTTPS for data transmission. When clients access over HTTP, the access log may display the protocol as HTTPS. |
Billing
The transfer acceleration feature itself is free to enable. Additional accelerated upload traffic and accelerated download traffic fees are incurred only when accessing OSS through the transfer acceleration domain. For more information, see Transfer acceleration fees.
FAQ
Why do I get 502 or 504 errors when accessing through the transfer acceleration domain?
This issue is usually caused by the automatic path switching mechanism of OSS transfer acceleration, and it is a normal phenomenon. To handle network fluctuations and changes in link quality during long-distance transmission, this service dynamically selects the optimal transmission path. When a path switch occurs, a small number of requests may be interrupted and return 502/504 errors. This situation cannot be completely avoided. We recommend that you implement an exponential backoff retry logic in your client code to improve the access success rate.
Why is there no acceleration effect after I enable transfer acceleration?
After you enable transfer acceleration, you must also replace the endpoint in access requests with the transfer acceleration domain (oss-accelerate.aliyuncs.com) to benefit from acceleration. If you only enable the feature without changing the domain, access is still performed through the regular public endpoint.
Why do I get errors when accessing immediately after enabling transfer acceleration?
After transfer acceleration is enabled, it takes approximately 30 minutes for the configuration to take effect globally. If you use the transfer acceleration domain immediately after enabling it, errors may occur because the configuration has not yet taken effect. Wait for some time and try again.
Why is cross-border access still slow when I use the transfer acceleration domain?
Transfer acceleration improves cross-region access speed by optimizing the transmission link. However, the actual effect in cross-border scenarios is affected by the quality of the cross-border carrier link. When cross-border links are congested or unstable, transmission speed may decrease. Recommendations:
-
Verify that the endpoint configuration is correct. The format should be
oss-accelerate.aliyuncs.comwithout the bucket name. -
For large files, combine transfer acceleration with Multipart upload and Resumable download to improve transmission reliability.
-
Implement a domain degradation mechanism at the application layer. When the transfer acceleration domain is unstable, automatically switch to the public endpoint to ensure business continuity.
How are transfer acceleration fees calculated? Are they charged in addition to Internet traffic fees?
Transfer acceleration fees and Internet outbound traffic fees are calculated independently.
-
When you access OSS through the transfer acceleration domain, both transfer acceleration traffic fees and Internet outbound traffic fees are incurred.
-
When you access OSS through the regular public endpoint, only Internet outbound traffic fees are incurred. No transfer acceleration fees apply.
Enabling the transfer acceleration feature itself is free. Fees are incurred only when data is actually transmitted through the transfer acceleration domain.