Within a project, you can create certificates, certificate authorities (CAs), and CA pools in one of many locations. These locations represent the geographical regions where a Certificate Authority Service resource is stored and can be accessed. The location of a CA pool impacts the latency of applications that use that resource.

You can create CA Service resources in several different locations in Google Cloud, depending on your availability requirements. For specific information about each location, see Locations.

For information on how to select a location, see Choosing the best type of location.

List of regional locations

A regional location's data centers exist in a specific geographical place. For example, a resource created in the us-central1 region is located in the central United States.

CA Service resources can be created in the regional locations given below.

Region name Region description
asia-east1 Taiwan
asia-east2 Hong Kong
asia-northeast1 Tokyo
asia-northeast2 Osaka
asia-northeast3 Seoul
asia-south1 Mumbai
asia-southeast1 Singapore
asia-southeast2 Jakarta
australia-southeast1 Sydney
europe-north1 Finland
europe-west1 Belgium
europe-west2 London
europe-west3 Frankfurt
europe-west4 Netherlands
europe-west6 Zürich
northamerica-northeast1 Montréal
us-central1 Iowa
us-east1 South Carolina
us-east4 Northern Virginia
us-west1 Oregon
us-west2 Los Angeles
us-west3 Salt Lake City
us-west4 Las Vegas
southamerica-east1 São Paulo

You can also check the list of supported locations by running the following gcloud command.

gcloud privateca locations list

Choosing the best type of location

The location of your CA pools is an important aspect of your application's design. As a rule, design your application so that all of its components are geographically near each other and near your application's clients. You cannot move or export a CA pool after it has been created.

What's next