Starting from May 9, 2022, COS will stop supporting default CDN acceleration domains for buckets that have never used them. This change will not affect buckets that are using or once used default CDN acceleration domains. However, we recommend you switch to custom CDN acceleration domains instead. To learn more about CDN acceleration, see Setting CDN Acceleration.
The change will affect users differently.
COS will not support default CDN acceleration domains for COS users registered after May 9, 2022.
Bucket | Support for Default CDN Acceleration Domain |
---|---|
New buckets | COS will not support default CDN acceleration domains for buckets created after May 9, 2022. |
Existing buckets that have never used default CDN acceleration domains | COS will not support default CDN acceleration domains for buckets that have never used them before May 9, 2022. |
Existing buckets that once used default CDN acceleration domains | Buckets that used default CDN acceleration domains before May 9, 2022 can continue to use them. |
Existing buckets that are using default CDN acceleration domains | Buckets that are using default CDN acceleration domains can continue to use them after May 9, 2022. |
Buckets that are using or once used default CDN acceleration domains can continue to use them after May 9, 2022. You can view the default CDN acceleration domains under your account via two methods.
Go to the CDN console > Domain Management to view the default CDN acceleration domains you used or are using. If a domain is in the format of “
Note:Buckets whose default CDN acceleration domains are disabled as of May 9, 2022 can continue to use the domains. However, the CDN console does not keep records of deleted CDN acceleration domains. Therefore, buckets whose default CDN acceleration domains are deleted can no longer use them after May 9, 2022.
Apakah halaman ini membantu?