Restricting Resource Locations


This guide describes how to set an organization policy that includes the resource locations constraint.

You can limit the physical location of a new resource with the Organization Policy Service resource locations constraint. You can use the location property of a resource to identify where it is deployed and maintained by the service. For data-containing resources of some Google Cloud services, this property also reflects the location where data is stored. This constraint allows you to define the allowed Google Cloud locations where the resources for supported services in your hierarchy can be created.

After you define resource locations, this limitation will apply only to newly-created resources. Resources you created before setting the resource locations constraint will continue to exist and perform their function.

A policy that includes this constraint will not be enforced on sub-resource creation for certain services, such as Cloud Storage and Dataproc.


The resource locations Organization Policy Service constraint controls the ability to create regional resources. This will not affect where resources with the global location are created. To avoid breaking existing serving infrastructure, you should test any new policy on non-production projects and folders, then apply the policy gradually within your organization.

For data storage commitments, see the Google Cloud Terms of Service and the Service Specific Terms. Organization policies that contain the resource locations constraint aren't data storage commitments.

This constraint applies to a specific subset of products and resource types. For a list of currently supported services and details on the behavior of each service, see the Resource Locations Supported Services page.

Location types

You can deploy Google Cloud resources in location types that represent different size categories. The largest location type is the multi-region, which includes more than one region. Each region is further subdivided into zones. For more information about regions and zones, see the Regions and Zones overview.

  • Multi-region locations are backed by physical resources in more than one region and are typically only used by storage-based resources. Some examples include us, asia, europe, and global.

  • Region locations are geographically isolated from each other. Some examples include us-west1 (Oregon), asia-northeast1 (Tokyo), and europe-west1 (Belgium).

  • Zone locations are the most granular and isolated location type used for deploying resources. A zone is an independent failure domain within a region. Some examples are us-east1-a, us-west1-b, and asia-northeast1-a.

When setting up locations, you should use the in: prefix and a Value Group. Using a Value Group curated by Google Cloud allows you to choose geographic location(s), without having to specify current or future Cloud locations.

The in: prefix to a Value Group specifies that all values that exist within the value group are considered to be part of the policy. If you enter a group value or a Google Cloud region without the prefix, the in: prefix will be automatically added, per the below rules:

  • If you enter a location that uses the in: prefix, and it contains any invalid group, the policy change will fail.
  • If you enter a location that is a region, such as us-east1, it will have the in: prefix prepended, to in:us-east1-locations in this example.
  • If you enter a region or multi-region value group such as us-locations, it will have the in: prefix prepended, to in:us-locations in this example.
  • If you enter a zone or multi-region such as us-east1-a or us, the values will not be changed.

Setting the organization policy

The resource locations constraint is a type of list constraint. You can add and remove locations from the allowed_values or denied_values lists of a resource locations constraint. To prevent organization policies from unexpectedly restricting service behavior as new locations are added to the available list, use a value group, or a list of allowed_values that represents the entire geographic boundary you want to define.

To set an organization policy including a resource locations constraint:


  1. Open the Organization policies page in the Cloud Console.

    Open Organization policies page

  2. From the Project picker, select the organization for which you want to set the organization policy.

  3. Select the Google Cloud Platform - Resource Location Restriction constraint to open its Policy details page.

  4. Click Edit.

  5. On the Edit page, select Customize.

  6. Under Policy enforcement, select Replace.

  7. Click Add rule.

  8. Under Policy values, select Custom.

  9. Under Policy type, select Allow to create a list of allowed locations, or select Deny to create a list of denied locations.

  10. In the Policy value box, enter the in prefix and a value group location string, then press Enter.

    For example, in:us-locations or in:us-west1-locations. You can enter multiple location strings by clicking New policy value.

    You can also enter specific zone, region, or multi-region locations as location strings. For a list of available locations, see the Resource Locations Supported Services page.

  11. To finish and apply the organization policy, click Save.


You can set policies with the gcloud command-line tool. To create a policy that includes the resource locations constraint, first create a policy file:

etag: BwVUSr8Q7Ng=
constraint: constraints/gcp.resourceLocations
    - in:us-east1-locations
    - in:northamerica-northeast1-locations

Then, run the set-policy command:

gcloud beta resource-manager org-policies set-policy \
    --organization 'ORGANIZATION_ID' \


  • ORGANIZATION_ID is the ID of the organization node to set this policy on.
  • POLICY.YAML is the .yaml file containing the organization policy you want.

A response will be returned with the results of the new organization policy:

constraint: constraints/gcp.resourceLocations
etag: BwVUSr8Q7Ng=
  - in:us-east1-locations
  - in:northamerica-northeast1-locations
updateTime: '2018-01-01T00:00:00.000Z'

You can also enter specific zone, region, or multi-region locations as location strings. For a list of available locations, see the Resource Locations Supported Services page.


You can use the Resource Manager API to set an organization policy on a resource. You will need an OAuth 2.0 bearer token for authentication and authorization.

To set an organization policy using the resource locations constraint:

curl -X POST -H "Content-Type: application/json" -H "Authorization: \
Bearer ${bearer_token}" -d '{policy: {etag: "BwVtXec438Y=", constraint: \
"constraints/gcp.resourceLocations", list_policy: {denied_values: \
["in:europe-locations", "in:southamerica-locations"] }}}' \

A response will be returned with the results of the new organization policy:

  "constraint": "constraints/gcp.resourceLocations",
  "etag": "BwVtXec438Y=",
  "updateTime": "2018-01-01T00:00:00.000Z",
  "listPolicy": {
    "deniedValues": [

You can also enter specific zone, region, or multi-region locations as location strings. For a list of available locations, see the Resource Locations Supported Services page.

To learn about using constraints in organization policies, see Using Constraints.

Using inheritance in organization policy

You can refine your organization policy to inherit the organization policy from the resource's parent nodes. Inheritance gives you granular control over the organization policies used throughout your resource hierarchy.

To enable inheritance on a resource node, set inheritFromParent = true in the organization policy .yaml file. For example:

etag: BwVtXec438Y=
constraint: constraints/gcp.resourceLocations
  inheritFromParent: true

Example error message

Services that support the resource location constraint are prevented from creating new resources in locations that would violate the constraint. If a service attempts to create a resource in a location that violates the constraint, the attempt will fail and an error message will be generated.

This error message will have this format: LOCATION_IN_REQUEST violates constraint constraints/gcp.resourceLocations on the resource RESOURCE_TESTED.

In the following example, a Compute Engine resource fails to create a new instance due to policy enforcement:

Location ZONE:us-east1-b violates constraint constraints/gcp.resourceLocations
on the resource

Google Cloud's operations suite and Cloud Audit Logs log entry:

 insertId: "5u759gdngec"
 logName: "projects/policy-violation-test/logs/"
 protoPayload: {
  @type: ""
  authenticationInfo: {…}
  authorizationInfo: [6]
  methodName: "beta.compute.instances.insert"
  request: {…}
  requestMetadata: {…}
  resourceLocation: {…}
  resourceName: "projects/policy-violation-test/zones/us-east1-b/instances/instance-3"
  response: {
   @type: ""
   error: {
    code: 412
    errors: [
     0: {
      domain: "global"
      location: "If-Match"
      locationType: "header"
      message: "Location ZONE:us-east1-b violates constraint constraints/gcp.resourceLocations on the resource projects/policy-violation-test/zones/us-east1-b/instances/instance-3."
      reason: "conditionNotMet"
    message: "Location ZONE:us-east1-b violates constraint constraints/gcp.resourceLocations on the resource projects/policy-violation-test/zones/us-east1-b/instances/instance-3."
  serviceName: ""
  status: {
   code: 3
   message: "INVALID_ARGUMENT"
 receiveTimestamp: "2019-06-14T03:04:23.660988360Z"
 resource: {
  labels: {…}
  type: "gce_instance"
 severity: "ERROR"
 timestamp: "2019-06-14T03:04:22.783Z"

Vulnerability findings and remediation

The resource location constraint restricts the creation of resources at runtime. This feature helps to prevent location violations from occurring, but does not identify or remediate existing violations. You can use Security Health Analytics, a built-in service of Security Command Center, to discover location violations in your resource hierarchy. For more information, see Organization Policy vulnerability findings.

If there are Security Health Analytics findings of location violations, see Remediating Security Health Analytics findings for steps to remediate those findings.

Value groups

Value groups are collections of groups and locations that are curated by Google to provide a simple way to define your resource locations. Value groups include many related locations and are expanded over time by Google without needing to change your organization policy to accommodate the new locations.

To use value groups in your organization policy, prefix your entries with the string in:. For more information on using value prefixes, see Using Constraints. Group names are not validated on the call to set the organization policy. If the group name provided does not exist, no new values will be added to the effective organization policy, unless that group name is created by Google later.

The following table contains the current list of available groups:

Group Details Direct members
Asia All locations within Asia:
  • asia-east1-locations
  • asia-east2-locations
  • asia-northeast1-locations
  • asia-northeast2-locations
  • asia-northeast3-locations
  • asia-south1-locations
  • asia-south2-locations
  • asia-southeast1-locations
  • asia-southeast2-locations

  • asia
  • asia1
Taiwan All locations within Taiwan:
  • asia-east1
  • asia-east1-a
  • asia-east1-b
  • asia-east1-c
Hong Kong All locations within Hong Kong:
  • asia-east2
  • asia-east2-a
  • asia-east2-b
  • asia-east2-c
Tokyo All locations within Tokyo:
  • asia-northeast1
  • asia-northeast1-a
  • asia-northeast1-b
  • asia-northeast1-c
Osaka All locations within Osaka:
  • asia-northeast2
  • asia-northeast2-a
  • asia-northeast2-b
  • asia-northeast2-c
Seoul All locations within Seoul:
  • asia-northeast3
  • asia-northeast3-a
  • asia-northeast3-b
  • asia-northeast3-c
Mumbai All locations within Mumbai:
  • asia-south1
  • asia-south1-a
  • asia-south1-b
  • asia-south1-c
Delhi All locations within Delhi:
  • asia-south2
  • asia-south2-a
  • asia-south2-b
  • asia-south2-c
Singapore All locations within Singapore:
  • asia-southeast1
  • asia-southeast1-a
  • asia-southeast1-b
  • asia-southeast1-c
Jakarta All locations within Jakarta:
  • asia-southeast2
  • asia-southeast2-a
  • asia-southeast2-b
  • asia-southeast2-c
Australia All locations within Australia:
  • australia-southeast1-locations
  • australia-southeast2-locations
Sydney All locations within Sydney:
  • australia-southeast1
  • australia-southeast1-a
  • australia-southeast1-b
  • australia-southeast1-c
Melbourne All locations within Melbourne:
  • australia-southeast2
  • australia-southeast2-a
  • australia-southeast2-b
  • australia-southeast2-c
AWS All AWS locations:
  • aws-us-east-1
Azure All Azure locations:
  • azure-eastus2
Canada All locations within Canada.
  • northamerica-northeast1-locations
  • northamerica-northeast2-locations
Montréal All locations within Montréal:
  • northamerica-northeast1
  • northamerica-northeast1-a
  • northamerica-northeast1-b
  • northamerica-northeast1-c
Toronto All locations within Toronto:
  • northamerica-northeast2
  • northamerica-northeast2-a
  • northamerica-northeast2-b
  • northamerica-northeast2-c
European Union All locations within European Union:
  • europe-central2-locations
  • europe-north1-locations
  • europe-west1-locations
  • europe-west3-locations
  • europe-west4-locations

  • EU
  • eu
  • eur3
  • eur4
  • europe-west
Warsaw All locations within Warsaw:
  • europe-central2
  • europe-central2-a
  • europe-central2-b
  • europe-central2-c
Finland All locations within Finland:
  • europe-north1
  • europe-north1-a
  • europe-north1-b
  • europe-north1-c
Belgium All locations within Belgium:
  • europe-west1
  • europe-west1-b
  • europe-west1-c
  • europe-west1-d
Frankfurt All locations within Frankfurt:
  • europe-west3
  • europe-west3-a
  • europe-west3-b
  • europe-west3-c
Netherlands All locations within Netherlands:
  • europe-west4
  • europe-west4-a
  • europe-west4-b
  • europe-west4-c
Europe All locations within Europe:
  • europe-central2-locations
  • europe-north1-locations
  • europe-west1-locations
  • europe-west2-locations
  • europe-west3-locations
  • europe-west4-locations
  • europe-west6-locations

  • EU
  • eu
  • eur3
  • eur4
  • eur5
  • europe
  • europe-west
London All locations within London:
  • europe-west2
  • europe-west2-a
  • europe-west2-b
  • europe-west2-c
Zurich All locations within Zurich:
  • europe-west6
  • europe-west6-a
  • europe-west6-b
  • europe-west6-c
North America All locations within North America:
  • northamerica-northeast1-locations
  • northamerica-northeast2-locations
  • us-locations
United States All locations within the United States:
  • us-central1-locations
  • us-central2-locations
  • us-east1-locations
  • us-east4-locations
  • us-west1-locations
  • us-west2-locations
  • us-west3-locations
  • us-west4-locations

  • US
  • aws-us-east-1
  • azure-eastus2
  • nam10
  • nam11
  • nam12
  • nam3
  • nam4
  • nam5
  • nam6
  • nam7
  • nam8
  • nam9
  • us
  • us-central
Iowa All locations within Iowa:
  • us-central1
  • us-central1-a
  • us-central1-b
  • us-central1-c
  • us-central1-f
Oklahoma All locations within Oklahoma:
  • us-central2
  • us-central2-a
  • us-central2-b
  • us-central2-c
  • us-central2-d
South Carolina All zones within South Carolina:
  • us-east1
  • us-east1-a
  • us-east1-b
  • us-east1-c
  • us-east1-d
Northern Virginia All locations within Northern Virginia:
  • us-east4
  • us-east4-a
  • us-east4-b
  • us-east4-c
Oregon All locations within Oregon:
  • us-west1
  • us-west1-a
  • us-west1-b
  • us-west1-c
Los Angeles All locations within Los Angeles:
  • us-west2
  • us-west2-a
  • us-west2-b
  • us-west2-c
Salt Lake City All locations within Salt Lake City:
  • us-west3
  • us-west3-a
  • us-west3-b
  • us-west3-c
Las Vegas All locations within Las Vegas:
  • us-west4
  • us-west4-a
  • us-west4-b
  • us-west4-c
South America All locations within South America:
  • southamerica-east1-locations
  • southamerica-west1-locations
São Paulo All locations within São Paulo:
  • southamerica-east1
  • southamerica-east1-a
  • southamerica-east1-b
  • southamerica-east1-c
Santiago All locations within Santiago:
  • southamerica-west1
  • southamerica-west1-a
  • southamerica-west1-b
  • southamerica-west1-c


Organization Policy Service uses OAuth 2.0 for API authentication and authorization. To get an OAuth 2.0 bearer token:

  1. Go to the OAuth 2.0 Playground page.

  2. In the Step 1 list of scopes, select the Cloud Resource Manager API v2 >, and then click Authorize APIs.

  3. On the Sign in with Google page that appears, select your account and sign in.

  4. To provide access to Google Oauth 2.0 Playground, click Allow on the prompt that appears.

  5. In Step 2, click Exchange authorization code for tokens.

  6. At the bottom of the Request / Response pane on the right, your access token string is displayed:

       "access_token": "ACCESS_TOKEN",
       "token_type": "Bearer",
       "expires_in": 3600

    Where ACCESS_TOKEN is the OAuth 2.0 bearer token string that you can use for API authorization.