Region and Zone

Same with other platforms like Heroku, Pi does not run in our own datacenter. Instead, it runs on Google Cloud. Therefore, the concept of region and availability zone in Pi is the same as GCP.

  • Regions are separate geographic physical data centers, completely indepedent from one another. Resource quota are region-specific.

  • Availability Zones are isolated physical locations within a region, interconnected through low-latency links.

The current regions and availablity zones are:

Cloud

Region

Location

Zones

Google Cloud

gcp-us-central1

Iowa

gcp-us-central1-a,gcp-us-central1-c

Resource Location

In Pi, resources are either global, specific to a region, an availability zone. However, when you view your resources in the web console, you'll only see the resources tied to the region you've specified.

Resource

Type

Description

API Credential

Global

You can use the same API credential in all regions.

Pod

Availability Zone

An instance is tied to the Availability Zones in which you launched it. However, its ID is tied to the region.

Volume

Availability Zone

A volume is tied to its Availability Zone and can be attached only to pods in the same Availability Zone.

Private Network

Region

A network is tied to a region.

Service

Region

A service is tied to a region and can be associated with pods from different availability zones in the same region.

Floating IP

Region

A flooating IP is tied to a region and can be associated with services in the same region.

Secret

Region

A secret is tied to a region.

Default Availability Zone

Pi allows you to place resources in different locations. When you launch a pod or create a volume, you can choose an availability zone. Otherwise the resource will be placed in the default zone of your account. The default zone is selected upon your registration. As we allocate the default zone randomly, different accounts may have different default zones.

You can see your default zone in the web console.

API Endpoints

When you work with Pi APIs, you must specify its regional endpoint:

Cloud

Region

Location

API Endpoint

Google Cloud

gcp-us-central1

Iowa

https://gcp-us-central1.hyper.sh:443/api/v1

For more information about the API access, see our API reference.

Last updated