Eventarc is available in specific regions depending on whether you are using Eventarc Advanced or Eventarc Standard.
A region is a specific geographic place, such as São Paulo.
A multi-region is a large geographic area, such as the United States, that contains two or more geographic places. (Some sources support dual-regions which are a specific pair of regions, such as Tokyo and Osaka.)
For more information about regions and zones, see Geography and regions.
Eventarc Advanced
Eventarc Advanced is available in the following regions:
| Region name | Region description | |
|---|---|---|
asia-south1 |
Mumbai, India | |
asia-southeast1 |
Jurong West, Singapore | |
australia-southeast1 |
Sydney, Australia | |
europe-north1 |
Hamina, Finland |
 Low CO2
|
europe-west1 |
St. Ghislain, Belgium |
Low CO2
|
europe-west3 |
Frankfurt, Germany | |
us-central1 |
Council Bluffs, Iowa, North America |
Low CO2
|
us-east4 |
Ashburn, Virginia, North America |
Eventarc Standard
The location for an Eventarc trigger should be either global
(applicable to some events only) or one of the supported regions
depending on the event type.
For more information, see Understand Eventarc locations.
Cloud Audit Logs events
Triggers for Cloud Audit Logs events are available in single-region
locations and you can create a global Eventarc trigger;
however, triggers are not supported in dual-region and multi-region locations.
When specifying the global location for Cloud Audit Logs triggers, you will
receive events from all locations for which the event filters match. For
example, by creating a global Eventarc trigger, you can
receive events from resources in the EU and US multi-regions.
Pub/Sub messages
Triggers for Pub/Sub messages are only available in
single-region locations and you can't create a global Eventarc
trigger.
Direct events
Triggers for events that are sent directly from one of the following Google sources are available in specific locations. For all other sources, see the supported regions.
AlloyDB for PostgreSQL
Eventarc triggers for AlloyDB events are available only in the following locations:
asia-east1asia-east2asia-northeast1asia-northeast2asia-northeast3asia-south1asia-southeast1asia-southeast2australia-southeast1australia-southeast2europe-central2europe-north1europe-west1europe-west2europe-west3europe-west6us-central1us-east1us-east4us-west1us-west2us-west3us-west4
API Gateway
Eventarc triggers for API Gateway events are available only in the following locations:
asia-east1asia-northeast1australia-southeast1europe-west1europe-west2globalus-central1us-east1us-east4us-west2us-west3us-west4
Apigee API hub
Eventarc triggers for API hub events are available only in the following locations:
europe-west1us-central1
Apigee Registry
Eventarc triggers for Apigee Registry events are available only in the following locations:
asia-east1asia-east2asia-northeast1asia-northeast2asia-northeast3asia-south1asia-south2asia-southeast1asia-southeast2australia-southeast1australia-southeast2europe-central2europe-north1europe-west1europe-west2europe-west3europe-west4europe-west6northamerica-northeast1northamerica-northeast2southamerica-east1us-central1us-east1us-east4us-west1us-west2us-west3us-west4
Backup for GKE
Eventarc triggers for Backup for GKE events are available only in the following locations:
asia-east1asia-east2asia-northeast1asia-northeast2asia-northeast3asia-south1asia-south2asia-southeast1asia-southeast2australia-southeast1australia-southeast2europe-central2europe-north1europe-southwest1europe-west1europe-west2europe-west3europe-west4europe-west6europe-west8europe-west9northamerica-northeast1northamerica-northeast2southamerica-east1southamerica-west1us-central1us-east1us-east4us-west1us-west2us-west3us-west4
Batch
Eventarc triggers for Batch events are available only in the following locations:
asia-east1asia-east2asia-northeast1asia-south1asia-southeast1europe-central2europe-north1europe-west2europe-west3europe-west4europe-west6northamerica-northeast1southamerica-west1us-central1us-east1us-east4us-south1us-west1us-west2us-west3us-west4
BeyondCorp
Eventarc triggers for BeyondCorp events are available only in the following locations:
asia-east1europe-west1globalus-central1us-east1
Certificate Manager
You must create a global Eventarc trigger for
Certificate Manager events.
Cloud Data Fusion
Eventarc triggers for Cloud Data Fusion events are available only in the following locations:
asia-east1asia-east2asia-northeast1asia-northeast2asia-northeast3asia-south1asia-southeast1asia-southeast2australia-southeast1europe-north1europe-west1europe-west2europe-west3europe-west4europe-west6northamerica-northeast1southamerica-east1us-central1us-east1us-east4us-west1us-west2
Cloud Deploy
Eventarc triggers for Cloud Deploy events are available only in the following locations:
asia-east1asia-east2asia-northeast1asia-northeast2asia-northeast3asia-south1asia-south2asia-southeast1asia-southeast2australia-southeast1australia-southeast2europe-central2europe-north1europe-southwest1europe-west1europe-west2europe-west3europe-west4europe-west6europe-west8europe-west9europe-west10europe-west12northamerica-northeast1northamerica-northeast2southamerica-east1southamerica-west1us-central1us-east1us-east4us-east5us-south1us-west1us-west2us-west3us-west4
Cloud Firestore
Eventarc triggers for Cloud Firestore must be in the same location as the Cloud Firestore database. In addition to the single-region locations listed in the Supported regions section, the following locations are also supported for Cloud Firestore triggers:
eur3: EUROPE-WEST1 and EUROPE-WEST4nam5: US-CENTRAL1 and US-CENTRAL2nam7: US-CENTRAL1 and US-EAST4
Cloud Run functions (formerly Cloud Functions)
Eventarc triggers for Cloud Run functions (formerly Cloud Functions) events are available only in the following locations:
asia-east1asia-east2asia-northeast1asia-northeast2asia-northeast3asia-south1asia-south2asia-southeast1asia-southeast2australia-southeast1australia-southeast2europe-central2europe-north1europe-west1europe-west2europe-west3europe-west4europe-west6northamerica-northeast1northamerica-northeast2southamerica-east1southamerica-west1us-central1us-east1us-east4us-west1us-west2us-west3us-west4
Cloud Speech-to-Text
You must create a global Eventarc trigger for Cloud
Speech-to-Text events.
Cloud Storage
Triggers for Cloud Storage events are available in single-region,
dual-region, and multi-region locations; you can't create a global
Eventarc trigger.
Note that the Cloud Storage bucket must reside in the same Google Cloud project and region as the Eventarc trigger.
In addition to the single-region locations listed in the Supported regions section, the following locations are also supported for Cloud Storage triggers:
asia: Data centers in Asiaasia1: ASIA-NORTHEAST1 and ASIA-NORTHEAST2eu: Data centers within member states of the European Unioneur4: EUROPE-NORTH1 and EUROPE-WEST4nam4: US-CENTRAL1 and US-EAST1us: Data centers in the United States
For more information, see Bucket locations.
Database Migration
Eventarc triggers for Database Migration events are available only in the following locations:
asia-east1asia-east2asia-northeast1asia-northeast2asia-northeast3asia-south1asia-south2asia-southeast1asia-southeast2australia-southeast1australia-southeast2europe-north1europe-southwest1europe-west1europe-west2europe-west3europe-west4europe-west6europe-west8europe-west9northamerica-northeast1northamerica-northeast2southamerica-east1southamerica-west1us-central1us-east1us-east4us-east5us-south1us-west1us-west2us-west3us-west4
Dataflow
Eventarc triggers for Dataflow events are available only in the following locations: