Eventarc locations

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.