Overview

BOS supports the setting of multiple domain names for the created Bucket to release the stored data.

Domain Name Type and Usage Scenarios

BOS currently supports Bucket official domain names, custom domain names, and CDN official domain names. Different domain names correspond to different usage scenarios. You can configure and use the domain name as needed.

Domain Type	Usage scenarios
Bucket official domain	When you create a Bucket, BOS will automatically generate the Bucket official domain name for the Bucket. For the domain name EndPoint in different regions, please refer to Get access domain name
Custom domain name	BOS supports adding a custom domain name to a Bucket. After binding the custom domain name to the Bucket, you can use the custom domain name to release the data in the Bucket. You can use a custom domain name to directly access the bound Bucket. The added custom domain name needs to be added to the DNS resolution management of the domain name registrar. After the CNAME resolution of the custom domain name is completed, it can be accessed through the custom domain name only after the resolution takes effect.
CDN official accelerated domain name	BOS currently supports Bucket binding CDN accelerated domain name. After binding, you can use the edge nodes of Baidu AI Cloud content distribution network (CDN) to accelerate the downstream delivery of content in BOS. After you bind the CDN domain name to Bucket, the DNS resolution of the Bucket domain name will be automatically modified to the CNAME domain name provided by the CDN, so as to access the CDN node and enable CDN acceleration. CDN official acceleration applies to the downstream acceleration of files in edge scenarios. Baidu AI Cloud BOS and CDN provide cache management. When you open Baidu AI Cloud BOS and CDN at the same time and use BOS as the source station of CDN service, you can perform intelligent cache management operations. BOS supports the CDN uplink acceleration feature to meet users' acceleration requirements in the upstream scenario when using BOS. The uplink acceleration feature needs to be activated separately, and the upstream domain name is the same as the official CDN accelerated domain name.

Bind Bucket Domain Name

BOS supports the binding of bucket domain names, which can be directly published on the external Internet and directly accessed by users.

Binding Rules

• The bound domain name must not include protocols, ports and paths, but only the domain name itself.
• Each bucket can bind up to 20 different domain names.

Operation Steps

1.Click the name of bucket to enter the bucket Management page and select the "Release Management" tab.

2.Click "Add customized domain" to complete bucket domain name binding; After the addition is completed, it will be displayed in the list of custom domain names below.

Note: The added custom domain name needs to be added to the DNS resolution management of the domain name registrar. After the CNAME resolution of the custom domain name is completed, it can be accessed through the custom domain name only after the resolution takes effect.

• If you need to turn on CDN acceleration for custom domain names, click "Turn on CDN Acceleration: in the corresponding operation column of domain names.
• If you want to unbind the custom domain name, click "Delete: in the corresponding operation column of the domain name.

CNAME Domain Name Resolution

After completing the binding, please log in to the background of the domain name service provider, add CNAME domain name resolution in domain name management, and transfer the required domain name CNAME to the domain name <region>. bcebos.com 'of BOS ( ` is the region where bucket is located, please refer to Region Selection Description to complete all domain name binding configuration.

E.g.:

• If your bucket is located in Beijing, please CNAME to bj.bcebos.com.
• If your Bucekt is located in Guangzhou, please CNAME to gz.bcebos.com.
• If your bucket area is in Suzhou, please CNAME to su.bcebos.com.

Note: For example, in case there are other resolution records in the bound domain name, the original resolution record needs to be deleted when CNAME reaches <region>.bceBOS. com.

Bind Https Certificate

After you have finished CNAME resolution, if you want to access this custom domain name as https, you can bind your https certificate to this custom domain name.

Baidu AI Cloud SSL Certificate Service provides a complete one-stop service for certificate application and management. Users can purchase, manage and use https certificates on Baidu AI Cloud. For details, please refer to Certificate Management

After you hold the available certificates in Baidu AI Cloud SSL Certificate Service, in BOS custom domain name console, you can click the "HTTPS Certificate: function item when creating the custom domain name for the first time or modifying the existing custom domain name. The drop-down will show all the certificates you manage in Baidu AI Cloud SSL Certificate Service and select the corresponding certificates as needed.

When the certificate bound to the domain name expires or becomes invalid, you can also select the custom domain name, click the "HTTPS Certificate: function item, and select the available certificate in the drop-down menu to replace it.

Note:

1. When the range of domain names covered by the certificate you selected does not match the custom domain name you expect to bind, the interface will prompt you to replace other available certificates.
2. It is recommended that you check the effective time of the binding certificate in Baidu AI Cloud SSL certificate service to avoid the unavailability of https access after the certificate expires.
3. The current BOS temporarily supports configuring https certificates for custom domain names of bucket under bj, su and gz regions.
4. After you choose to bind a custom certificate, it usually takes 5-10 minutes to establish the binding relationship. Please wait patiently and then try to use it.

Access Address

After the binding is completed, the bucket can be accessed directly by using the bound domain name.

E.g.: To bucket: The domain name bound to video is video.51mingxi.com, please change the domain name video.51mingxi.com CNAME to <region>. bcebos.com in the background of the domain name service provider. When finished, you should use the URL: http://video.51mingxi.com/ can direct access the bucket.

CDN Accelerated Publication

BOS currently supports the use of CDN to accelerate the specified bucket. After the selection of the Bukcet that needs to be accelerated, the DNS resolution of the domain name corresponding to the bucket in BOS is modified to the CNAME domain name provided by CDN, thus accessing the CDN node and starting CDN acceleration.

CDN Configuration Rules

• CDN does not cache data if that expiration time is not configured in the CDN and the source station does not display a control header providing http cache. In this case, CDN acceleration cannot be realized after the data in Bukcet is updated, and the cache needs to be manually refreshed in CDN. For specific operations, please refer to Refresh Cache.
• The expiration time can be configured in CDN to automatically update the cache. For specific operations, please refer to Configure cache Expiration Time.

Operation Steps

1.Click the name of bucket to enter the bucket Management page and select the "Release Management" tab.

2.Click "Open Acceleration" on the right side of the official acceleration domain name to directly open the official CDN acceleration domain name.

After the acceleration is successfully started, the refresh page can show that the button on the right side of the official domain name changes to "Manage CDN Acceleration:. Click to enter the CDN domain name management page to manage the domain name details.

Note:

• Bucket is created without CDN acceleration turned on by default.
• BOS provides the official CDN acceleration domain name, namely bucketname.cdn.bcebos.com. The official acceleration domain name is the official CDN acceleration domain name opened by BOS bucket. CNAME resolution does not need to be configured and the domain name cannot be modified.

3.If you need to add a customized acceleration domain name, click "Add customized domain" and it will be displayed in the list of custom domain names after adding. If you need to manage the accelerated domain name, click "Manage CDN domain name" in the corresponding operation column.

Note:

• Before adding a custom domain name, you need to go to the DNS resolution management of the domain name registrar, and resolve the custom domain name CNAME to the CNAME address provided by CDN. Only after the resolution is successful can you accelerate access through CDN. Please refer to Binding CNAME for specific operations.
• If the added custom domain name is occupied, submit the work order for processing.

Overview

BOS releases the fresh new CDN uplink acceleration feature, so as to meet the need for acceleration in uplink scenarios when BOS is used. Enabling CDN uplink acceleration needs a certain preceding rules:

• Enable the CDN official acceleration of the Bucket;
• Enable the CDN dynamic acceleration feature. After enabling the above-mentioned two preceding features, you can enable the uplink acceleration feature on the console. After it is enabled, CDN dynamic acceleration costs will incur.

Scenarios to use CDN uplink acceleration

CDN uplink acceleration feature of BOS can meet the demand of use in the uplink scenarios, such as:

• File upload acceleration scenario
• Remote file uploading scenario
• Large file uploading scenario
• Dynamically updated file uploading scenario

You can also view the best practices for CDN uplink acceleration to understand more information about use.

Enabling steps

1. Open the release management page

Log in the console and open the release management page of the Bucket needing to enable the uplink acceleration.

2. Enable uplink acceleration

Before you enable the uplink acceleration feature of the Bucket, you need to enable CDN official acceleration of the Bucket, and enable CDN dynamic acceleration feature. If you have not enabled the preceding feature yet, please enable it according to the guidance on the console.

If the above-mentioned preconditions are met, you can enable the uplink acceleration feature. When enabling, the system will set the request mode to "PUT" and "POST" by default, and does not support for modification. Click "OK" to enable the CDN uplink acceleration. After it is enabled, it defaults to support the uplink acceleration of all types of files.

Note: The CDN domain name of Bucket uplink acceleration feature is the same as the CDN official domain name of the Bucket.

3. Disable uplink acceleration If you no longer need CDN uplink acceleration, you can disable this feature on the console.

Cache Management

When you open CDN service, you often have the following business requirements:

• Data is added in the source station, CDN cache node needs to be refreshed in the first time, but this process wants to be automated
• In case there are file changes in the source station, the CDN cache node needs to update the cached old data so that users can access the correct business information
• After the source is audited, the source station finds the non-conforming file which has been cleared by the administrator, the CDN cache node also needs to clear the cache in the first time

Based on the above scenarios, Baidu AI Cloud BOS and CDN provide cache management. When you open Baidu AI Cloud BOS and CDN at the same time and use BOS as the source station of CDN service, you can perform intelligent cache management operations.

Operation Steps

1.Click the bucket name to enter the bucket management page, select the "Release Management" tag, and click the "Edit" button of "publish cache configuration" to configure cache management.

2.Define the linkage logic of CDN node for the events occurred in the three source stations of "New File Upload: "File Update: and "File Delete.

• In the new file upload scenarios, if "Preload Cache" is configured, it will automatically preheat to each node when a new file upload is generated at the source station.
• In the file update scenarios, if you configure "Clear Cache", the CDN node will automatically clear the cache corresponding to the original file after the original file is updated; if you configure "preload after clear", the CDN node will generate a new cache after the original cache is cleared.
• In the file deletion scenarios, if you configure "Clear Cache", the CDN node will clear the corresponding cache synchronously when the file deletion occurs at the source station.

3.After the linkage logic of the cache node is configured, effective resources can also be specified. Currently, it is supported to take effect on the whole bucket or some resources within the bucket.

Note: Each resource is separated by a line break, with a maximum of 20 added.

At the same time, after the cache management is enabled, BOS will automatically perform the source return in accordance with the configuration and CDN linkage. At this time, the generated source return traffic will generate corresponding fees. Please refer to BOS Pricing for the price standard.