Model Armor feature availability varies by region due to dependencies on services that could process data outside the location. As a result, some regions have limited feature support when you configure Model Armor using templates in order to maintain comprehensive data residency. This page provides a breakdown of supported features across all available regions.
Full-support regions
If you create a Model Armor template in a full-support region, you have access to all of the following filters. All underlying dependency services are available or allowed in the jurisdictional boundary.
- Prompt injection and jailbreak detection
- Responsible AI
- Sensitive Data Protection
- Malicious URL detection
- Child sexual abuse material (CSAM) detection
- Multi-language detection
- Antivirus scanning
The following are the locations with full feature support:
| Region/multi-region | Jurisdiction | At rest | In use | In transit |
|---|---|---|---|---|
asia-northeast3 |
South Korea | Yes | No | No |
australia-southeast2 |
Australia | Yes | No | No |
eu |
European Union | Yes | Yes | Yes |
europe-southwest1 |
European Union | Yes | Yes | Yes |
europe-west1 |
European Union | Yes | Yes | Yes |
europe-west3 |
European Union | Yes | Yes | Yes |
europe-west4 |
European Union | Yes | Yes | Yes |
europe-west9 |
European Union | Yes | Yes | Yes |
us |
United States | Yes | Yes | Yes |
us-central1 |
United States | Yes | Yes | Yes |
us-east1 |
United States | Yes | Yes | Yes |
us-east4 |
United States | Yes | Yes | Yes |
us-west1 |
United States | Yes | Yes | Yes |
The Jurisdiction column indicates the geographical boundary (for example, a
country or a multi-region like eu or us) within which
Model Armor ensures data residency compliance for the supported
states (at rest, in use, and in transit) as indicated in the table.
The Region/multi-region column lists the specific Google Cloud region or multi-region identifier.
When data residency is enforced for a region in Model Armor, it helps ensure that data remains within a specified jurisdiction while in at least one of the following states:
At rest: Stored data remains within the specific Google Cloud region listed.
In use and In transit: Data residency enforcement for these states within the specified jurisdiction depends on the values in the In use and In transit columns:
- Yes: Data residency is enforced for the In use and In transit states within the listed jurisdiction. This means that the data remains within the boundaries of the listed jurisdiction while being processed or transmitted (not necessarily within that single region).
- No: Data residency is not enforced for the In use and In transit states within the listed jurisdiction. This means that the data might be processed or transmitted outside of the jurisdiction.
Limited-support regions
If you create a Model Armor template in a limited-support region, these Model Armor features are unavailable.
| Feature or detector | Notes |
|---|---|
| Multi-language detection | Prompt injection and jailbreak and RAI detectors support English only. You cannot enable multi-language detection when creating a template in regions with unsupported features. |
| Malicious URL detection | Relies on services that might process data outside the region. You cannot enable malicious URL detection when creating a template in regions with unsupported features. |
| Child sexual abuse material (CSAM) detection | Not available when creating a new template. Relies on services that might process data outside the region. |
| Antivirus scanning | Files can be sanitized but without antivirus scanning. |
The following are the regions with limited feature support:
| Region/multi-region | Jurisdiction | At rest | In use | In transit |
|---|---|---|---|---|
asia-northeast1 |
Japan | Yes | Yes | Yes |
asia-south1 |
India | Yes | Yes | Yes |
asia-southeast1 |
Singapore | Yes | Yes | Yes |
europe-west2 |
United Kingdom | Yes | Yes | Yes |
northamerica-northeast2 |
Canada | Yes | Yes | Yes |