# Locations

Within a project, you can create certificates, certificate authorities (CAs),
and CA pools in one of many [locations](https://cloud.google.com/about/locations). These locations
represent the geographical regions where a Certificate Authority Service
(CA 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](https://cloud.google.com/about/locations).

For information on how to select a location, see [Choosing the best type of location](https://docs.cloud.google.com/certificate-authority-service/docs/locations#choosing).

## Asia Pacific

The following table lists the regions in Asia Pacific where
CA Service resources can be stored.

| Region | Region description |
|---|---|
| `asia-east1` | Taiwan |
| `asia-east2` | Hong Kong |
| `asia-northeast1` | Tokyo |
| `asia-northeast2` | Osaka |
| `asia-northeast3` | Seoul |
| `asia-south1` | Mumbai |
| `asia-south2` | Delhi |
| `asia-southeast1` | Singapore |
| `asia-southeast2` | Jakarta |
| `asia-southeast3` | Bangkok |
| `australia-southeast1` | Sydney |
| `australia-southeast2` | Melbourne |

## Europe

The following table lists the regions in Europe where CA Service
resources can be stored.

| Region | Region description |
|---|---|
| `europe-central2` | Warsaw |
| `europe-north1` | Finland |
| `europe-north2` | Stockholm |
| `europe-southwest1` | Madrid |
| `europe-west1` | Belgium |
| `europe-west2` | London |
| `europe-west3` | Frankfurt |
| `europe-west4` | Netherlands |
| `europe-west6` | Zürich |
| `europe-west8` | Milan |
| `europe-west9` | Paris |
| `europe-west10` | Berlin |
| `europe-west12` | Turin |

## Middle East

The following table lists the regions in the Middle East where
CA Service resources can be stored.

| Region | Region description |
|---|---|
| `me-central1` | Doha |
| `me-central2` | Dammam |
| `me-west1` | Tel Aviv |

## Americas

The following table lists the Americas regions where
CA Service resources can be stored.

| Region | Region description |
|---|---|
| `northamerica-northeast1` | Montréal |
| `northamerica-northeast2` | Toronto |
| `northamerica-south1` | Mexico |
| `southamerica-east1` | São Paulo |
| `southamerica-west1` | Santiago |
| `us-central1` | Iowa |
| `us-east1` | South Carolina |
| `us-east4` | Northern Virginia |
| `us-east5` | Columbus |
| `us-south1` | Dallas |
| `us-west1` | Oregon |
| `us-west2` | Los Angeles |
| `us-west3` | Salt Lake City |
| `us-west4` | Las Vegas |

## Africa

The following table lists the regions in Africa where
CA Service resources can be stored.

| Region | Region description |
|---|---|
| `africa-south1` | Johannesburg |

## Determining available regions

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

- See all the [Google Cloud locations](https://cloud.google.com/about/locations).
- Learn more about [Geography and regions](https://docs.cloud.google.com/docs/geography-and-regions) in Google Cloud.