Region
Region refers to the geographical area of a physical data center. A region is divided based on geographical location and network latency. Within the same Region, shared elastic computing, block storage, object-oriented storage, VPC networking, EIP, images, and other public services are available.
eSurfing Cloud's different regions are completely isolated, ensuring maximum stability and fault tolerance between regions. To reduce access latency and improve download speeds, it is recommended that you select the region closest to your business needs.
Related Features
The networks between different regions are completely isolated, and cloud products in different regions cannot communicate via the internal network by default.
If there is a need for communication between cloud products in different regions, it can be achieved through public IP addresses, VPNs, and other similar methods.
How to Choose a Region
In eSurfing Cloud, once resources are created or purchased, they cannot be moved to a different region. Therefore, when selecting a region, you should carefully consider the following factors:
Geographical Location: The closer the distance between users and the deployed resources, the lower the network latency and the faster the access speed. It is recommended that you choose a region based on the latency requirements of your business scenario.
a) Mainland China: Generally, it is recommended to select the data center closest to the region where your target users are located to further improve user access speed. If you use eSurfing Cloud to host all your business, the telecommunications network can ensure fast access between regions in Mainland China.
b) Other Countries and Regions: The bandwidth provided in other countries and regions is primarily targeted at users outside Mainland China. If you are based in Mainland China, using these regions may result in longer access latency, and it is not recommended for use.Resource Pricing and Overwrite: There may be differences in resource pricing across different regions, and the product offerings may vary by location. Please choose an appropriate region based on your requirements and budget.
Business Filing: If you are using an ECS instance as a web server, you will need to complete the business filing, and you must also purchase instances in the designated regions. (The approval requirements for business filing vary by provincial (or municipal) communications administration, please refer to the content published on the local administration's business filing website.)
Availability Zone
An Availability Zone (AZ) refers to a physical region within the same geographic area where power and networking are independently provided. An Availability Zone (AZ) is a collection of one or more physical data centers with independent utilities such as power, fire protection, and water supply. AZs are typically within 100 kilometers of each other, and multiple AZs within a Region are connected by high-speed fiber optics to meet users' needs for building highly available systems across AZs.
Related Features
The goal of dividing into Availability Zones is to ensure that faults are isolated between AZs (except in the case of major disasters or large-scale power outages), preventing fault propagation and keeping the user's services continuously available online. By launching instances within separate Availability Zones, users can protect their applications from being affected by faults at a single location.
Cloud products that are in the same region but in different Availability Zones under the same Virtual Private Cloud (VPC) can all communicate with each other through the Intranet and can be directly accessed using Intranet IP addresses.
How to Choose an Availability Zone
Within the same region, there is internal network communication between Availability Zones. Fault isolation can be achieved between different Availability Zones, meaning that if one AZ experiences a fault, it will not affect the normal operation of other AZs. Whether to place instances within the same Availability Zone depends primarily on your application's requirements for disaster recovery capabilities and network latency.
If your application requires high disaster recovery capabilities, it is recommended that you deploy instances across different Availability Zones within the same region.
If your application requires low network latency between instances, it is recommended that you create instances within the same Availability Zone.
The relationship between a region and Availability Zones
Each region is completely independent, with Availability Zones in different regions being entirely isolated. However, the Availability Zones within the same region are connected by low-latency links.
The relationship between regions and Availability Zones is depicted in the following figure:
Currently, eSurfing Cloud has opened cloud services in multiple regions worldwide. You can choose the region and Availability Zone that suits your needs.
Relevant Operations
Migrating instances to other Availability Zones.
An instance that has already been launched cannot change its Availability Zone, but users can migrate the instance to another Availability Zone through other methods. The migration process includes creating a custom image from the raw instance, launching an instance in the new Availability Zone using the custom image, and updating the instance's configuration.
Copy the image to another region
User actions such as launching instances and viewing instances are region-specific. If a user needs to launch an instance and the image for that instance does not exist in the current region, the image must be copied to the current region.