With the ability to specify a region in which to perform your Sensitive Data Protection operations, you can control where your potentially sensitive data is processed. This document explains the concept of Sensitive Data Protection processing location and shows you how to specify a region.
To see a list of supported regions and multi-regions, see Sensitive Data Protection locations.
About regions and multi-regions
A region is a specific geographic place, such as the western United States or northeast Asia. A multi-region location (or just multi-region) is a large geographic area, such as the European Union, that contains two or more geographic regions.
Location considerations
A good location balances latency, availability, and bandwidth costs.
Use a region to help optimize latency and network bandwidth.
Use a multi-region when you want to process data from outside of the Google network and distributed across large geographic areas, or when you want the higher availability that comes with being redundant across regions.
Generally, you should process your data in a location that is convenient or contains the majority of the users of your data.
If your organization is required to keep in-transit data within a specified location, then use only the regions or multi-regions that support regional endpoints. In this case, you need to use the Cloud Data Loss Prevention API, because the regional endpoints for Sensitive Data Protection aren't available for use with the Google Cloud console.
Specify a region
How you specify the processing region depends on the type of endpoint you are sending the request to—the global endpoint or a regional endpoint. The type of endpoint you choose depends on whether you're required to keep in-transit data within a specified region. For more information, see Global and regional endpoints for Sensitive Data Protection.
Specify a region in a request to the global endpoint
Console
Choose a region when setting up your Sensitive Data Protection operation.
For example, when creating a job trigger, choose a location from the Resource location menu, as shown here:
If the processing location is not a concern, use the Global region and Google chooses the location where processing should take place. Global is the default region choice.
REST
Insert region information into the request endpoint URL. If the processing location is
not a concern, use the global region and Google chooses the location where
processing should take place. Note that any resources created by a request that
specifies the global region are stored under the global region.
The following are some example requests to the global endpoint.
Using the global region
The following two requests have the same effect. Not including a region is the
same as specifying locations/global/.
POST https://www.googleapis.com/dlp/v2/projects/PROJECT_ID/locations/global/content:inspect
POST https://www.googleapis.com/dlp/v2/projects/PROJECT_ID/content:inspect
Using a specific region
To specify a region for processing, within the resource URL, insert
locations/ and then the region name.
POST https://www.googleapis.com/dlp/v2/projects/PROJECT_ID/locations/us-west2/content:inspect
Specify a region in a request to a regional endpoint
Console
For Sensitive Data Protection, regional endpoints aren't available for use with the Google Cloud console.
C#
To learn how to install and use the client library for Sensitive Data Protection, see Sensitive Data Protection client libraries.
To authenticate to Sensitive Data Protection, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Go
To learn how to install and use the client library for Sensitive Data Protection, see Sensitive Data Protection client libraries.
To authenticate to Sensitive Data Protection, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Java
To learn how to install and use the client library for Sensitive Data Protection, see Sensitive Data Protection client libraries.
To authenticate to Sensitive Data Protection, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.