Help Center/ DataArts Studio/ FAQs/ Consultation and Billing/ Regions and AZs
Updated on 2022-09-28 GMT+08:00
View PDF

Regions and AZs

Concepts

We use a region and an availability zone (AZ) to identify the location of a data center. You can create resources in a specific region and AZ.

  • Regions are divided from the dimensions of geographical location and network latency. Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS), are shared within the same region. Regions are classified as universal regions and dedicated regions. A universal region provides universal cloud services for common tenants. A dedicated region provides services of the same type only or for specific tenants.
  • An AZ is a physical location using independent power supplies and networks. Faults in an AZ do not affect other AZs. A region can contain multiple AZs, which are physically isolated but interconnected through internal networks. This ensures the independence of AZs and provides low-cost and low-latency network connections.

Figure 1 shows the relationship between the regions and AZs.

Figure 1 Regions and AZs

Region Selection

When selecting a region, consider the following factors:
  • Location

    You are advised to select a region closest to your target users. This reduces network latency and improves access rate. However, Chinese mainland regions provide the same infrastructure, BGP network quality, and operations and configurations on resources. Therefore, if your target users are in the Chinese mainland, you do not need to consider the network latency differences when selecting a region.

    The countries and regions outside the Chinese mainland, such as Bangkok, provide services for users outside the Chinese mainland. If your target users are in the Chinese mainland, these regions are not recommended because there may be a latency in accessing resources.

  • Relationship between cloud services

    Cloud services in different regions cannot communicate with each other through an internal network.

    For example, if you want to enable communication between DataArts Studio (containing modules such as Management Center and CDM) and services in other regions (such as MRS and OBS), use a public network or Direct Connect. If DataArts Studio and the other services are in the same region, instances in the same subnet and security group can communicate with each other by default.

  • Resource price

    Resource pricing may vary in different regions.

AZ Selection

AZ to which the CDM cluster in the DataArts Studio instance belongs. The DataArts Studio instance communicates with other services through the CDM cluster.

When you buy a DataArts Studio instance or incremental package for the first time, there is no requirement on the AZ. When you buy a new DataArts Studio instance or incremental package, determine whether to select the same AZ as the existing one based on your DR and network latency demands.
  • If your application requires good DR capability, deploy resources in different AZs in the same region.
  • If your application requires a low network latency between instances, deploy resources in the same AZ.

Changing the Region or AZ of an Instance

  • During the validity period of your yearly/monthly DataArts Studio package, you can unsubscribe from the package in the current region and purchase a package in another region.
  • You cannot change the region or AZ of an instance.

Regions and Endpoints

An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. You can obtain endpoints from (Optional) Obtaining Authentication Information.

Parent topic: Consultation and Billing