Stay organized with collections
Save and categorize content based on your preferences.
This page outlines the locations where Artifact Analysis vulnerability
metadata is stored, as well as the metadata API endpoints. Platform
administrators and security managers can use this information to understand
regionalized service support within Artifact Analysis.
When you push container images to Artifact Registry and perform on-push vulnerability
scans, Artifact Analysis automatically stores the scan results for you.
A single global endpoint is used for metadata retrieval:
https://containeranalysis.googleapis.com.
Upcoming changes
Starting September 30, 2024, Artifact Analysis is gradually rolling out
regionalized data storage and endpoints to help support compliance with data
residency requirements. The Container Analysis API stores metadata in the same
region or multi-region as the Artifact Registry repository where your image is
being scanned.
Regions and multi-regions
Metadata can be stored in the following types of locations:
A region is a specific geographic place, such as Tokyo or Northern
Virginia.
A multi-region is a large geographic area, such as Asia or the United
States, that contains two or more geographic places.
Data storage regions with regional endpoints
Artifact Analysis can store data in the following regions, which
have both global and regional endpoints.
The format for each endpoint is
https://containeranalysis.REGION.rep.googleapis.com.
Region
Region description
asia-east1
Taiwan
asia-east2
Hong Kong
asia-northeast1
Tokyo
asia-northeast3
Seoul
asia-south1
Mumbai
asia-south2
Delhi
asia-southeast1
Singapore
asia-southeast2
Jakarta
australia-southeast1
Sydney
europe-central2
Warsaw
europe-north1
Finland
europe-southwest1
Madrid
europe-west1
Belgium
europe-west2
London
europe-west3
Frankfurt
europe-west4
Netherlands
europe-west6
Zürich
europe-west8
Milan
europe-west9
Paris
me-central1
Doha
me-central2
Dammam
me-west1
Tel Aviv
northamerica-northeast1
Montréal
northamerica-northeast2
Toronto
southamerica-east1
São Paulo
southamerica-west1
Santiago
us-central1
Iowa
us-east1
South Carolina
us-east4
Northern Virginia
us-east5
Columbus
us-south1
Dallas
us-west1
Oregon
us-west2
Los Angeles
us-west3
Salt Lake City
us-west4
Las Vegas
Data storage regions using the global endpoint
Artifact Analysis can store data in the following regions. You must
retrieve metadata through the global endpoint,
https://containeranalysis.googleapis.com.
Region
Region description
africa-south1
Johannesburg
asia-northeast2
Osaka
australia-southeast2
Melbourne
europe-west10
Berlin
europe-west12
Turin
Data storage in multi-regions
Artifact Analysis can store data in the following regions, which only have
a global endpoint. You must retrieve metadata through the global endpoint,
https://containeranalysis.googleapis.com.
Multi-region name
Multi-region description
asia
Data centers in Asia
eu
Data centers in the European Union
us
Data centers in the United States
Restrict global API endpoint usage
To help enforce the use of regional endpoints, use the
constraints/gcp.restrictEndpointUsage organization policy constraint to block
requests to the global API endpoint. For more information, see
Restricting endpoint usage.
[[["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-25 UTC."],[[["\u003cp\u003eStarting September 30th, 2024, Artifact Analysis will begin transitioning to regionalized metadata storage and providing corresponding API endpoints to support data residency requirements.\u003c/p\u003e\n"],["\u003cp\u003eArtifact Analysis stores vulnerability scan results when container images are pushed to Artifact Registry, with metadata previously being retrieved via a single global endpoint.\u003c/p\u003e\n"],["\u003cp\u003eMetadata will now be stored in either a specific geographic region or a larger multi-region, aligning with the location of the scanned image's Artifact Registry repository.\u003c/p\u003e\n"],["\u003cp\u003eSome regions will have both global and regional endpoints for metadata retrieval, with regional endpoints following the format \u003ccode\u003ehttps://containeranalysis.\u003c/code\u003e\u003cvar\u003eREGION\u003c/var\u003e\u003ccode\u003e.rep.googleapis.com\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eSome regions and multi-regions will still use the global endpoint \u003ccode\u003ehttps://containeranalysis.googleapis.com\u003c/code\u003e, meaning that metadata retrieval will still be done through this endpoint.\u003c/p\u003e\n"]]],[],null,["# Metadata storage locations\n\n| **Note:** Starting September 30th, 2024, Artifact Analysis is gradually transitioning to regionalized metadata storage, and providing additional API endpoints in corresponding locations.\n\nThis page outlines the locations where Artifact Analysis vulnerability\nmetadata is stored, as well as the metadata API endpoints. Platform\nadministrators and security managers can use this information to understand\nregionalized service support within Artifact Analysis.\n\nWhen you push container images to Artifact Registry and perform on-push vulnerability\nscans, Artifact Analysis automatically stores the scan results for you.\nA single global endpoint is used for metadata retrieval:\n`https://containeranalysis.googleapis.com`.\n\nUpcoming changes\n----------------\n\nStarting September 30, 2024, Artifact Analysis is gradually rolling out\nregionalized data storage and endpoints to help support compliance with data\nresidency requirements. The Container Analysis API stores metadata in the same\nregion or multi-region as the Artifact Registry repository where your image is\nbeing scanned.\n\nRegions and multi-regions\n-------------------------\n\nMetadata can be stored in the following types of locations:\n\n- A *region* is a specific geographic place, such as Tokyo or Northern\n Virginia.\n\n- A *multi-region* is a large geographic area, such as Asia or the United\n States, that contains two or more geographic places.\n\nData storage regions with regional endpoints\n--------------------------------------------\n\nArtifact Analysis can store data in the following regions, which\nhave both global and regional endpoints.\n\nThe format for each endpoint is\n`https://containeranalysis.`\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e`.rep.googleapis.com`.\n\nData storage regions using the global endpoint\n----------------------------------------------\n\nArtifact Analysis can store data in the following regions. You must\nretrieve metadata through the global endpoint,\n`https://containeranalysis.googleapis.com`.\n\nData storage in multi-regions\n-----------------------------\n\nArtifact Analysis can store data in the following regions, which only have\na global endpoint. You must retrieve metadata through the global endpoint,\n`https://containeranalysis.googleapis.com`.\n\nRestrict global API endpoint usage\n----------------------------------\n\nTo help enforce the use of regional endpoints, use the\n`constraints/gcp.restrictEndpointUsage` organization policy constraint to block\nrequests to the global API endpoint. For more information, see\n[Restricting endpoint usage](/assured-workloads/docs/restrict-endpoint-usage)."]]
