Regions
Introduction
Region refers to the geographical area of a physical data center. For Converge Cloud, different regions are completely isolated from each other to ensure maximum stability and fault tolerance between regions. To reduce access latency and improve download speed, it is recommended to choose the region closest to your customers.
You can query the list of regions through the API to see the complete list of regions.
Related Characteristics
- Networks in different regions are completely isolated, and cloud services in different regions cannot communicate through the private network by default.
- Cloud services in different regions can access the Internet through public network IP address. Cloud services in Virtual Private Cloud (VPC) can also communicate via Peering Connection provided by Converge Cloud over the Converge Cloud NSFCNET for a more stable and faster interconnection than Internet access.
- Cloud Load Balancer (CLB) currently defaults to supporting intra-region traffic forwarding and binding with CVMs within the same local region. If the cross-region binding feature is enabled, it enables CLB to bind CVMs across regions.
Regions that comply with the regulatory requirements of the financial industry have strengths of high security and strong isolation. Currently, services such as CVM, financial database, redis for storage, and face recognition are provided for such regions. Certified financial customers who need to use such regions can submit a ticket.
AZs
Introduction
Availability Zone (AZ) refers to the Converge Cloud physical data centers within the same region but with independent power supply and network. The goal is to ensure that failures within the availability zones are isolated from each other (except for major disasters or power failures) preventing fault propagation and ensuring that users' businesses continue to provide online services. By launching instances in independent availability zones, users can protect applications from the impact of single-location failures.
You can query the list of availability zones.
Related Characteristics
Cloud services in different availability zones within the same region, but in the same VPC, can interconnect through the private network and can be accessed directly using private network IP addresses.
Intranet interconnection refers to the interconnection of resources under the same account, and the resources of different accounts are completely isolated from each other on the intranet.
How to Choose Regions and AZs?
When choosing regions and availability zones, you need to consider the following factors:
- The region where your CVM is located, and the geographical location of you and your target users.
It is recommended that you choose the region closest to your customers when purchasing CVMs, to reduce access latency and improve access speed. - Relationship between CVMs and other cloud services.
It is recommended that you choose other cloud services with the same availability zone in the same region. Then the cloud products can communicate through the private network to reduce access latency and improve access speed. - Considerations on business high availability and disaster recovery.
Even if there is only one VPC, it is recommended that you deploy services at least in different availability zones to ensure fault isolation between availability zones and enable cross-availability zone disaster recovery. - Communications between different availability zones may have network communication delays. This needs to be evaluated in combination with the actual needs of services to find the best balance between high availability and low latency.
- If you need to access hosts in other countries and districts, it is recommended that you select CVMs in other countries and districts. If you create a CVM in Converge Cloud's available regions, accessing hosts in other countries and districts will have high access latency. It is not recommended for such usage.
Resource Position Description
This document explains which Converge Cloud resources are global, which are region-specific but not distinguished by availability zones, and which are based on availability zones.
| Resources | Resource ID Format : 8-digit numbers and characters. | Type | Note |
|---|---|---|---|
| User account | Unlimited. | Unique globally. | Users can use the same account to access Converge Cloud resources around the world. |
SSH Key |
skey-xxxxxxxx | Available for all regions. | Users can use the SSH key to bind CVMs in any region under their account. |
CVM Instance |
ins-xxxxxxxx | Used only in a single availability zone of a single region. | Users can only create CVM instances in availability zones. |
| Custom Image | img-xxxxxxxx | Available for multiple availability zones in a single region. | Users can create custom images of instances and use them under different availability zones in the same region. If you need to use it in other regions, replicate the custom image to another region by using the image replication feature. |
Elastic IP |
eip-xxxxxxxx | Available for multiple availability zones in a single region. | EIP addresses are created in a certain region, and can only be associated with instances from the same region. |
Security Group |
sg-xxxxxxxx | Available for multiple availability zones in a single region. | Security groups are created in a certain region, and can only be associated with instances from the same region. Converge Cloud automatically creates three default security groups for the user. |
CBS |
disk-xxxxxxxx | Used only in a single availability zone of a single region. | Users can only create CBS under a specific availability zone and mount them on instances of the same availability zone. |
Snapshot |
snap-xxxxxxxx | Available for multiple availability zones in a single region. | After a snapshot is created for a certain CBS, users can use the snapshot to perform other operations (such as creating CBS) in this region. |
CLB |
clb-xxxxxxxx | Available for multiple availability zones in a single region. | CLB can bind CVMs in different availability zones of a single region for traffic forwarding. |
VPC |
vpc-xxxxxxxx | Available for multiple availability zones in a single region. | A VPC is created in a certain region, and resources belonging to the same VPC can be created in different availability zones. |
Subnet |
subnet-xxxxxxxx | Used only in a single availability zone of a single region. | Users cannot create subnets across availability zones. |
Route Table |
rtb-xxxxxxxx | Available for multiple availability zones in a single region. | The user needs to specify a specific VPC when creating a routing table. Thus it adheres to the position attributes of the specified VPC. |
Related Operations
Migrating Instances to Other Availability Zones
An instance that has been started cannot change its availability zone, but users can migrate the instance to another availability zone in other ways. The migration process includes creating a custom image from the original instance, starting the instance in the new availability zone using the custom image, and updating the configuration of the new instance.
- Create a custom image of the current instance.
- If the network environment of the current instance is a VPC and the current private IP address needs to be retained after migration, users can first delete the subnet in the current availability zone and then create a subnet in the new availability zone with the same IP address range as the original subnet. Only subnets that do not contain available instances can be deleted. Therefore, all instances in the current subnet should be moved to the new subnet.
- Create an instance in the new availability zone using the custom image you just created. You can select the same instance type and configuration as the original instance or select a new instance type and configuration.
- If the original instance has been associated with an EIP address, it is disassociated from the old instance and associated with the new instance.
- (Optional) If the original instance is of pay-as-you-go billing mode, you may choose to terminate it.
Replicating an Image to Other Regions
The actions, such as starting and viewing instances, are distinguished by region attribute. If the image of the instance to be started does not exist in the local region, you need to replicate the image to the local region.