Stay organized with collections
Save and categorize content based on your preferences.
This page provides information about data residency with AML AI.
Data residency describes where your data is stored at rest. To help comply
with your internal and external data residency requirements, AML AI
gives you the ability to control where data is stored.
Each Instance
resource is created with a region specified. The artifacts created underneath
the parent are constrained to that region location.
AML AI and data residency
Customer Data is stored at rest and machine learning processing is performed in the specified region.
This includes Customer Data associated with AML AI
resources, such as datasets, engine configs, models, and includes copies of
inputs and outputs, generated ML features, model hyperparameters, model
weights, and prediction results.
See the Service Specific Terms for the definition of
Customer Data, which may not include resource identifiers, attributes, or
other data labels.
Organizational constraints
Organizational constraints (constraints/gcp.resourceLocations) can control the
region in which Google Cloud resources can be created. AML AI
obeys these regional constraints at resource creation time. For more information,
see restricting resource locations
and resource locations supported services.
Location resource
AML AI has a Location resource as a parent object of all other resources in
AML AI. All child AML AI resources are
associated with only one Location resource, which ensures data residency
within the associated Google Cloud region.
Input and output data
An AML AI instance requires all input and output data to be
specified in the same region and project. This prevents data from being
accidentally moved between Google Cloud regions.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eAML AI allows you to control where your data is stored at rest, ensuring compliance with internal and external data residency requirements.\u003c/p\u003e\n"],["\u003cp\u003eEach AML AI instance is created with a specific region, and all associated data, such as datasets, models, and prediction results, are stored within that region.\u003c/p\u003e\n"],["\u003cp\u003eAML AI respects organizational constraints, such as \u003ccode\u003econstraints/gcp.resourceLocations\u003c/code\u003e, that dictate the regions where Google Cloud resources can be created.\u003c/p\u003e\n"],["\u003cp\u003eAll input and output data for an AML AI instance must reside within the same region and project, preventing data movement between Google Cloud regions.\u003c/p\u003e\n"],["\u003cp\u003eAn AML AI location resource acts as the parent object, ensuring all child AML AI resources are associated with only one Google Cloud region, and therefor, maintaining data residency.\u003c/p\u003e\n"]]],[],null,["# Data residency\n\nThis page provides information about data residency with AML AI.\n*Data residency* describes where your data is stored at rest. To help comply\nwith your internal and external data residency requirements, AML AI\ngives you the ability to control where data is stored.\n\nEach [Instance](/financial-services/anti-money-laundering/docs/reference/rest/v1/projects.locations.instances)\nresource is created with a region specified. The artifacts created underneath\nthe parent are constrained to that region location.\n\nAML AI and data residency\n-------------------------\n\n- Customer Data is stored at rest and machine learning processing is performed in the specified region.\n- This includes Customer Data associated with AML AI resources, such as datasets, engine configs, models, and includes copies of inputs and outputs, generated ML features, model hyperparameters, model weights, and prediction results.\n- See the [Service Specific Terms](/terms/service-terms) for the definition of Customer Data, which may not include resource identifiers, attributes, or other data labels.\n\nOrganizational constraints\n--------------------------\n\nOrganizational constraints (`constraints/gcp.resourceLocations`) can control the\nregion in which Google Cloud resources can be created. AML AI\nobeys these regional constraints at resource creation time. For more information,\nsee [restricting resource locations](/resource-manager/docs/organization-policy/defining-locations)\nand [resource locations supported services](/resource-manager/docs/organization-policy/defining-locations-supported-services#aml-ai).\n\nLocation resource\n-----------------\n\nAML AI has a [Location](/financial-services/anti-money-laundering/docs/reference/rest/v1/projects.locations#Location) resource as a parent object of all other resources in\nAML AI. All child AML AI resources are\nassociated with only one Location resource, which ensures data residency\nwithin the associated Google Cloud region.\n\nInput and output data\n---------------------\n\nAn AML AI instance requires all input and output data to be\nspecified in the same region and project. This prevents data from being\naccidentally moved between Google Cloud regions.\n\nWhat's next\n-----------\n\nFor more information about Google's data residency commitment, read\n[the data residency terms](/terms/data-residency)."]]
