Chile Data Boundary

This page describes the set of controls that are applied on Chile Data Boundary workloads in Assured Workloads. It provides detailed information about data residency , supported Google Cloud products and their API endpoints, and any applicable restrictions or limitations on those products. The following additional information applies to Chile Data Boundary:

  • Data residency: The Chile Data Boundary control package sets data location controls to support Chile-only regions . See the Google Cloud-wide organization policy constraints section for more information.
  • Support: Technical support services for Chile Data Boundary workloads are available with Standard, Enhanced, or Premium Cloud Customer Care subscriptions. Chile Data Boundary workloads support cases are routed to global support personnel.
  • Pricing: The Chile Data Boundary control package is included in Assured Workloads' Free tier , which incurs no additional charges. See Assured Workloads pricing for more information.

Supported products and API endpoints

Unless otherwise noted, users can access all supported products through the Google Cloud console. Restrictions or limitations that affect the features of a supported product, including those that are enforced through organization policy constraint settings , are listed in the following table.

If a product is not listed, that product is unsupported and has not met the control requirements for Chile Data Boundary. Unsupported products are not recommended for use without due diligence and a thorough understanding of your responsibilities in the shared responsibility model . Before using an unsupported product, ensure that you are aware of and are willing to accept any associated risks involved, such as negative impacts to data residency or data sovereignty.

Supported product API endpoints Restrictions or limitations
accessapproval.googleapis.com
None
accesscontextmanager.googleapis.com
None
accessapproval.googleapis.com
None
alloydb.googleapis.com
None
mesh.googleapis.com
meshca.googleapis.com
meshconfig.googleapis.com
None
artifactregistry.googleapis.com
None
gkebackup.googleapis.com
None
bigquery.googleapis.com
bigqueryconnection.googleapis.com
bigquerydatapolicy.googleapis.com
bigquerydatatransfer.googleapis.com
bigquerymigration.googleapis.com
bigqueryreservation.googleapis.com
bigquerystorage.googleapis.com
Affected features
bigtable.googleapis.com
bigtableadmin.googleapis.com
None
binaryauthorization.googleapis.com
None
privateca.googleapis.com
None
cloudasset.googleapis.com
None
cloudbuild.googleapis.com
None
composer.googleapis.com
None
dns.googleapis.com
None
datafusion.googleapis.com
None
cloudkms.googleapis.com
None
cloudkms.googleapis.com
None
compute.googleapis.com
None
cloudkms.googleapis.com
None
compute.googleapis.com
None
logging.googleapis.com
Affected features
monitoring.googleapis.com
None
compute.googleapis.com
None
oslogin.googleapis.com
None
compute.googleapis.com
None
run.googleapis.com
Affected features
run.googleapis.com
None
sqladmin.googleapis.com
None
sqladmin.googleapis.com
None
storage.googleapis.com
None
cloudtasks.googleapis.com
None
compute.googleapis.com
None
vision.googleapis.com
None
workstations.googleapis.com
None
compute.googleapis.com
Affected features and organization policy constraints
anthosconfigmanagement.googleapis.com
None
gkeconnect.googleapis.com
None
dlp.googleapis.com
None
Not applicable
None
dataflow.googleapis.com
datapipelines.googleapis.com
None
dataform.googleapis.com
None
dataplex.googleapis.com
datalineage.googleapis.com
None
dataproc-control.googleapis.com
dataproc.googleapis.com
None
documentai.googleapis.com
None
essentialcontacts.googleapis.com
None
eventarc.googleapis.com
None
file.googleapis.com
None
firebaserules.googleapis.com
None
firestore.googleapis.com
None
gkehub.googleapis.com
None
anthosidentityservice.googleapis.com
None
aiplatform.googleapis.com
None
compute.googleapis.com
networksecurity.googleapis.com
Affected features
netapp.googleapis.com
Affected features
container.googleapis.com
containersecurity.googleapis.com
None
chronicle.googleapis.com
chronicleservicemanager.googleapis.com
None
Not applicable
None
iam.googleapis.com
None
iap.googleapis.com
None
config.googleapis.com
None
looker.googleapis.com
None
redis.googleapis.com
None
networkconnectivity.googleapis.com
None
orgpolicy.googleapis.com
None
compute.googleapis.com
None
servicehealth.googleapis.com
None
pubsub.googleapis.com
None
cloudresourcemanager.googleapis.com
None
securesourcemanager.googleapis.com
None
vpcaccess.googleapis.com
None
speech.googleapis.com
None
storagetransfer.googleapis.com
None
texttospeech.googleapis.com
None
trafficdirector.googleapis.com
None
accesscontextmanager.googleapis.com
None
aiplatform.googleapis.com
None
aiplatform.googleapis.com
None
aiplatform.googleapis.com
None
aiplatform.googleapis.com
None
aiplatform.googleapis.com
None
discoveryengine.googleapis.com
None
aiplatform.googleapis.com
None
compute.googleapis.com
None
webrisk.googleapis.com
None

Restrictions and limitations

The following sections describe Google Cloud-wide or product-specific restrictions or limitations for features, including any organization policy constraints that are set by default on Chile Data Boundary folders. Other applicable organization policy constraints —even if not set by default— can provide additional defense-in-depth to further protect your organization's Google Cloud resources.

Google Cloud-wide

Google Cloud-wide organization policy constraints

The following organization policy constraints apply across Google Cloud.

Organization policy constraint
Description
Set to the following locations in the allowedValues list:
  • southamerica-west1
This value restricts creation of new resources to the selected values. When set, no resources can be created in any other regions, multi-regions, or locations outside of the selection. See Resource locations supported services for a list of resources that can restricted by the Resource Locations organization policy constraint, as some resources may be out of scope and unrestrictable.

Changing this value by making it less restrictive potentially undermines data residency by allowing data to be created or stored outside of a compliant data boundary.
Set to allow all supported products and API endpoints .

Determines which services can be used by restricting runtime access to their resources. For more information, see Restricting resource usage .
gcp.restrictTLSVersion
Set to deny the following TLS versions:
  • TLS_1_0
  • TLS_1_1
See the Restrict TLS versions page for more information.

BigQuery

Affected BigQuery features

Feature
Description
Enabling BigQuery on a new folder
BigQuery is supported, but it isn't automatically enabled when you create a new Assured Workloads folder due to an internal configuration process. This process normally finishes in ten minutes, but can take much longer in some circumstances. To check whether the process is finished and to enable BigQuery, complete following steps:
  1. In the Google Cloud console, go to the Assured Workloads page.

    Go to Assured Workloads

  2. Select your new Assured Workloads folder from the list.
  3. On the Folder Details page in the Allowed services section, click Review Available Updates .
  4. In the Allowed services pane, review the services to be added to the Resource Usage Restriction organization policy for the folder. If BigQuery services are listed, click Allow Services to add them.

    If BigQuery services are not listed, wait for the internal process to complete. If the services are not listed within 12 hours of folder creation, contact Cloud Customer Care .

After the enablement process is completed, you can use BigQuery in your Assured Workloads folder.

Gemini in BigQuery is not supported by Assured Workloads.

Unsupported features
The following BigQuery features are not supported and should not be used in the BigQuery CLI. It is your responsibility not to use them in BigQuery for Assured Workloads.
The BigQuery CLI is supported.

Google Cloud SDK
You must use Google Cloud SDK version 403.0.0 or newer to maintain data regionalization guarantees for technical data. To verify your current Google Cloud SDK version, run gcloud --version and then gcloud components update to update to the newest version.
Administrator controls
BigQuery will disable unsupported APIs but administrators with sufficient permissions to create an Assured Workloads folder can enable an unsupported API. If this occurs, you will be notified of potential non-compliance through the Assured Workloads monitoring dashboard .
Loading data
BigQuery Data Transfer Service connectors for Google Software as a Service (SaaS) apps, external cloud storage providers, and data warehouses are not supported. It is your responsibility not to use BigQuery Data Transfer Service connectors for Chile Data Boundary workloads.
BigQuery does not verify support for third-party transfers for the BigQuery Data Transfer Service. It is your responsibility to verify support when using any third-party transfer for the BigQuery Data Transfer Service.
Non-compliant BQML models
Externally-trained BQML models are not supported.
Query jobs
Query jobs should only be created within Assured Workloads folders.
Queries on datasets in other projects
BigQuery does not prevent Assured Workloads datasets from being queried from non-Assured Workloads projects. You should ensure that any query that has a read or a join on Assured Workloads data be placed in an Assured Workloads folder. You can specify a fully-qualified table name for their query result using projectname.dataset.table in the BigQuery CLI.
Cloud Logging
BigQuery utilizes Cloud Logging for some of your log data. You should disable your _default logging buckets or restrict _default buckets to in-scope regions to maintain compliance using the following command:

gcloud alpha logging settings update --organization=ORGANIZATION_ID --disable-default-sink

See Regionalize your logs for more information.

Compute Engine

Affected Compute Engine features

Feature Description
Guest environment It is possible for scripts, daemons, and binaries that are included with the guest environment to access unencrypted at-rest and in-use data. Depending on your VM configuration, updates to this software may be installed by default. See Guest environment for specific information about each package's contents, source code, and more.

These components help you meet data sovereignty through internal security controls and processes. However, if you want additional control, you can also curate your own images or agents and optionally use the compute.trustedImageProjects organization policy constraint.

See the Building a custom image page for more information.
OS policies in VM Manager Inline scripts and binary output files within the OS policy files are not encrypted using customer-managed encryption keys (CMEK). Therefore, don't include any sensitive information in these files. Alternatively, consider storing these scripts and output files in Cloud Storage buckets. For more information, see Example OS policies .

If you want to restrict the creation or modification of OS policy resources that use inline scripts or binary output files, enable the constraints/osconfig.restrictInlineScriptAndOutputFileUsage organization policy constraint.

For more information, see Constraints for OS Config .

Compute Engine organization policy constraints

Organization policy constraint Description
compute.disableGlobalCloudArmorPolicy Set to True .

Disables the creation of new global Google Cloud Armor security policies , and the addition or modification of rules to existing global Google Cloud Armor security policies. This constraint doesn't restrict the removal of rules or the ability to remove or change the description and listing of global Google Cloud Armor security policies. Regional Google Cloud Armor security policies are unaffected by this constraint. All global and regional security policies that exist prior to the enforcement of this constraint remain in effect.

compute.restrictNonConfidentialComputing

(Optional) Value is not set. Set this value to provide additional defense-in-depth. See the Confidential VM documentation for more information.

compute.trustedImageProjects

(Optional) Value is not set. Set this value to provide additional defense-in-depth.

Setting this value constrains image storage and disk instantiation to the specified list of projects. This value affects data sovereignty by preventing use of any unauthorized images or agents.

Cloud Logging

Affected Cloud Logging features

Feature Description
Log sinks Filters shouldn't contain Customer Data.

Log sinks include filters which are stored as configuration. Don't create filters that contain Customer Data.
Live tailing log entries Filters shouldn't contain Customer Data.

A live tailing session includes a filter which is stored as configuration. Tailing logs doesn't store any log entry data itself, but can query and transmit data across regions. Don't create filters that contain Customer Data.

Google Cloud NetApp Volumes

Affected Google Cloud NetApp Volumes features

Feature Description
Flex service level The Flex service level is not available in the Chile Data Boundary control package.

What's next

Create a Mobile Website
View Site in Mobile | Classic
Share by: