About Regions, Endpoints, and Availability Zones

OUTSCALE Cloud services are available in several locations worldwide. The OUTSCALE infrastructure is composed of different Regions and Availability Zones isolated from one another, where you can create your Cloud resources.

Regions and Endpoints

A Region is a geographical area where you can host Cloud resources. Regions are independent from each other, and do not share resources. Resources hosted in a Region cannot be accessed from other Regions. Communication between Regions is only possible using the Internet. For more information about Regions locations, see Regions, Endpoints and Availability Zones Reference.

Data is never automatically transferred between Regions. Data stored on your resources remains in the Region where you deployed them, and is protected by local laws.

You can however copy your account or resources between different Regions. For more information, see About Your Account.

A Region consists of one or more Availability Zones. For more information, see the Regions and Availability Zones section below.

When deploying resources, you must use an endpoint to specify the Region. Endpoints are URLs that provide an entry point to a Cloud service. Every service request must contain an endpoint. To reduce latency, each service has a specific endpoint for each Region where it is available. For more information, see Regions, Endpoints and Availability Zones Reference.

Regions and Availability Zones

An Availability Zone (AZ) is a distinct location in a Region. A Region consists of one or more AZs, and each AZ belongs to a single Region.

Each AZ corresponds to a physical datacenter of the OUTSCALE infrastructure in the Region. For safety reasons, AZs are isolated from one another. However, low-latency communication between AZs in the same Region is enabled with fiber-optic links.

You can choose to deploy resources in different AZs to isolate them from one another in the physical infrastructure, and thus reduce risks.

The mapping between AZs and physical datacenters is carried out randomly. It is automatically set at account creation. It is specific to each account and cannot be changed after account creation.

Therefore, the first AZ you use in a Region can be placed on any datacenter in that Region. The second AZ is then automatically placed on another datacenter.

If a specific mapping is required, you can contact your Technical Account Manager before the creation of the account.

Regions and Availability Zones Architecture

sch General RegionAZsArchitecture

Some types of resources are placed in an Availability Zone, while others are placed in a Region. When deploying the following resources, you can either choose a specific AZ or let 3DS OUTSCALE choose a default one:

For more information about available AZs, see Regions, Endpoints and Availability Zones Reference.

Related Page