Regions and Access Endpoints

Last updated: 2021-12-15 17:56:09


    A region is an area where a Tencent Cloud managed data center is deployed. COS data is stored in buckets in these regions. You can use COS to store your data in multiple regions. In general, you are advised to create buckets in the region closest to the location where your business is conducted. In this way, latency and costs can be reduced and compliance requirements can be met.

    For example, if your business is distributed in South China, creating buckets in the Guangzhou region can accelerate the object upload and download speeds.

    Default endpoint refers to the COS bucket’s default domain, which is automatically generated when the bucket is generated. Buckets residing in different regions have different default domains. To can view the default domain, you can go to the COS console, click the name of the desired bucket, click Overview, and find the Domain Information area.

    Chinese mainland

    Region Abbreviation Default Endpoint (Upload/Download/Management)
    Chinese mainland Public cloud regions
    Beijing ap-beijing <BucketName-APPID>
    Nanjing ap-nanjing <BucketName-APPID>
    Shanghai ap-shanghai <BucketName-APPID>
    Guangzhou ap-guangzhou <BucketName-APPID>
    Chengdu ap-chengdu <BucketName-APPID>
    Chongqing ap-chongqing <BucketName-APPID>

    Outside Chinese mainland

    Region Abbreviation Default Endpoint (Upload/Download/Management)
    Asia Pacific Public cloud regions Hong Kong (China) ap-hongkong <BucketName-APPID>
    Singapore ap-singapore <BucketName-APPID>
    Mumbai ap-mumbai <BucketName-APPID>
    Jakarta ap-jakarta <BucketName-APPID>
    Seoul ap-seoul <BucketName-APPID>
    Bangkok ap-bangkok <BucketName-APPID>
    Tokyo ap-tokyo <BucketName-APPID>
    North America Silicon Valley (US Wes) na-siliconvalley <BucketName-APPID>
    Virginia (US East) na-ashburn <BucketName-APPID>
    Toronto na-toronto <BucketName-APPID>
    South America Sao Paulo sa-saopaulo <BucketName-APPID>
    Europe Frankfurt eu-frankfurt <BucketName-APPID>
    Moscow eu-moscow <BucketName-APPID>

    Global acceleration endpoint

    A global acceleration endpoint is formatted as <BucketName-APPID> For more information about global acceleration endpoints and the use cases, please see Overview.


    Assume that you have logged in to the COS console as the root account (APPID is 1250000000) and created a bucket named examplebucket in the Guangzhou region, the default endpoint of the bucket will be:

    • examplebucket-1250000000: The bucket belongs to the user whose APPID is 1250000000. APPID is a permanent and unique ID automatically assigned upon your application for the Tencent Cloud account. You can view your APPID at Account Information.
    • cos: Cloud Object Storage (COS)
    • ap-guangzhou: abbreviation of the bucket region
    • endpoint of Tencent Cloud, fixed

    If you store an image (picture.jpg) to a created bucket, the access URL of the image will be:

    If you have set the access permission of your image to public read and private write, you can copy the image access URL and paste it in the browser to view the image details.

    Private Network and Public Network Access

    If an intra-region CVM instance accesses COS using the default domain, data will be transferred over a private network by default. In this case, data uploads and downloads will generate private network traffic, but this traffic will not be billed. However, please note that you will still be charged for the number of requests.

    Tencent Cloud COS adopts intelligent resolution for COS endpoints. In this way, the optimal linkage can be provided for you to access COS with different ISPs.

    If you deploy a service in Tencent Cloud to access COS, intra-region access requests will be automatically directed to a private network address. Currently, cross-region requests do not support private network access and will be resolved to a public network address by default.

    For more information about private network and public network access, please see Creating Request Overview.