Artifact Registry locations

When you create a repository, you must specify its location. The chosen location determines where the repository storage is created. You can create repositories in the following types of locations:

  • Region is a specific geographic place, such as Tokyo or Northern Virginia.

  • Multi-region is a large geographic area, such as Asia or the United States, that contains two or more geographic places.

Artifact Registry stores artifacts in the selected location in accordance with the Service Specific Terms.

A good location balances latency, availability, and bandwidth costs for data consumers.

  • Use a region to help optimize latency and network bandwidth for uploads and downloads by systems located in the same region.

  • Use a multi-region when you want to interact with systems that are outside of the Google network and distributed across large geographic areas, or when you want the higher availability that comes with being geo-redundant.

  • Generally, you should store your artifacts in a location that is convenient or contains the majority of the users of your data.

  • For Compute Engine

    • Storing data in the same region as your Compute Engine VM instances can provide better performance.
    • While you can't specify a Compute Engine zone repository location, all Compute Engine VM instances in zones within a given region have similar performance when accessing storage in that region.

To view a list of supported repository locations, run the command:

gcloud artifacts locations list

Location constraints

Your organization might have specific requirements for the location of stored data. If your organization policy includes resource location constraints, Artifact Registry enforces the constraints when you create a repository.

Organization policy compliance isn't enforced retroactively on existing repositories. To enforce new location constraints on existing stored artifacts, create new repositories after the organization policy is applied, and then migrate artifacts from old repositories to the new ones. You can use the gcrane tool to copy images between repositories.

Available regions

All regions are at least 100 miles apart.

Continent Region Name Region Description
North America
northamerica-northeast1 Montréal
northamerica-northeast2 Toronto
us-central1 Iowa
us-east1 South Carolina
us-east4 Northern Virginia
us-west1 Oregon
us-west2 Los Angeles
us-west3 Salt Lake City
us-west4 Las Vegas
South America
southamerica-east1 São Paulo
Europe
europe-central2 Warsaw
europe-north1 Finland
europe-west1 Belgium
europe-west2 London
europe-west3 Frankfurt
europe-west4 Netherlands
europe-west6 Zürich
Asia
asia-east1 Taiwan
asia-east2 Hong Kong
asia-northeast1 Tokyo
asia-northeast2 Osaka
asia-northeast3 Seoul
asia-south1 Mumbai
asia-south2 Delhi
asia-southeast1 Singapore
asia-southeast2 Jakarta
Australia
australia-southeast1 Sydney
australia-southeast2 Melbourne

Available multi-regions

If you create a repository in a multi-region, data is stored in at least two separate geographic locations separated by at least 100 miles.

Multi-Region Name Multi-Region Description
asia Data centers in Asia
europe Data centers in the European Union1
us Data centers in the United States

1 Object data added to a storage bucket in the europe multi-region is not stored in the europe-west2 or europe-west6 data center.

What's Next