> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/4.3/planning-and-installation/weka-installation-on-gcp/required-services-and-supported-regions.md).

# Required services and supported regions

The region must support the services used in WEKA on GCP. The following sections list these services and the regions that support them.

## Required services used in WEKA on GCP

* Cloud Build API
* Cloud Deployment Manager V2 API
* Cloud DNS API
* Cloud Functions API
* Cloud Logging API
* Cloud Resource Manager API
* Cloud Scheduler API
* Compute Engine API
* Secret Manager API
* Serverless VPC Access API
* Service Usage API
* Workflow Executions API
* Workflows API

Other services used or enabled:

* App Engine
* IAM
* Google Cloud Storage

## Supported regions

To ensure support for a specific region, it must meet the requirements listed [above](#required-services-used-in-weka-on-gcp).

{% hint style="info" %}
If the region you want to deploy in is not on the supported list, verify the availability of these services in that region. If they are available and your region is not listed, contact the WEKA [Customer Success Team](/4.3/support/getting-support-for-your-weka-system.md#contact-customer-success-team) for validation.
{% endhint %}

### Americas

| Region Name             | Region Description            |
| ----------------------- | ----------------------------- |
| northamerica-northeast1 | Montréal, Canada              |
| southamerica-east1      | São Paulo, Brazil             |
| southamerica-west1      | Santiago, Chile               |
| us-central1             | Iowa, United States           |
| us-east1                | South Carolina, United States |
| us-east4                | Virginia, United States       |
| us-east5                | Columbus, United States       |
| us-west1                | Oregon, United States         |
| us-west2                | Los Angeles, United States    |
| us-west3                | Salt Lake City, United States |
| us-west4                | Las Vegas, United States      |

### Asia Pacific

| Region name          | Region Description      |
| -------------------- | ----------------------- |
| asia-east1           | Changhua County, Taiwan |
| asia-east2           | Hong Kong               |
| asia-northeast1      | Tokyo, Japan            |
| asia-northeast2      | Osaka, Japan            |
| asia-northeast3      | Seoul, South Korea      |
| asia-south1          | Mumbai, India           |
| asia-south2          | Delhi, India            |
| asia-southeast1      | Jurong West, Singapore  |
| asia-southeast2      | Jakarta, Indonesia      |
| australia-southeast1 | Sydney, Australia       |

### Europe

| Region Name     | Region Description     |
| --------------- | ---------------------- |
| europe-north1   | Hamina, Finland        |
| europe-west1    | St. Ghislain, Belgium  |
| europe-west2    | London, England        |
| europe-west3    | Frankfurt, Germany     |
| europe-west4    | Eemshaven, Netherlands |
| europe-west6    | Zurich, Switzerland    |
| europe-central2 | Warsaw, Poland         |

**Related information**

[Regions and zones](https://cloud.google.com/compute/docs/regions-zones)

[Cloud locations](https://cloud.google.com/about/locations)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.weka.io/4.3/planning-and-installation/weka-installation-on-gcp/required-services-and-supported-regions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.