Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini memberikan informasi tentang residensi data dengan AML AI.
Residensi data menjelaskan lokasi penyimpanan data Anda saat data dalam kondisi tidak aktif. Untuk membantu mematuhi
persyaratan residensi data internal dan eksternal, AML AI
memberi Anda kemampuan untuk mengontrol lokasi penyimpanan data.
Setiap resource Instance
dibuat dengan wilayah yang ditentukan. Artefak yang dibuat di bawah
induk dibatasi ke lokasi region tersebut.
AML AI dan residensi data
Data Pelanggan disimpan dalam penyimpanan dan pemrosesan machine learning dilakukan di region yang ditentukan.
Hal ini mencakup Data Pelanggan yang terkait dengan resource AI AML, seperti set data, konfigurasi mesin, model, dan menyertakan salinan input dan output, fitur ML yang dihasilkan, hyperparameter model, bobot model, dan hasil prediksi.
Lihat Persyaratan Khusus Layanan untuk mengetahui definisi
Data Pelanggan, yang mungkin tidak mencakup ID resource, atribut, atau
label data lainnya.
Batasan organisasi
Batasan organisasi (constraints/gcp.resourceLocations) dapat mengontrol wilayah tempat resource dapat dibuat. Google Cloud AI AML
mematuhi batasan regional ini pada waktu pembuatan resource. Untuk informasi selengkapnya,
lihat membatasi lokasi resource
dan layanan yang didukung lokasi resource.
Resource lokasi
AML AI memiliki resource Location sebagai objek induk dari semua resource lainnya di AML AI. Semua resource AI AML turunan hanya
dikaitkan dengan satu resource Lokasi, yang memastikan retensi data
dalam region Google Cloud terkait.
Data input dan output
Instance AI AML mengharuskan semua data input dan output ditentukan di region dan project yang sama. Hal ini mencegah data
dipindahkan secara tidak sengaja antar-region Google Cloud .
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-01 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)."]]
