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 redundant across regions.

• 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

Available multi-regions

A multi-regional location's data centers are spread across a general geographical area. For example, a resource created in the europe multi-region persists in multiple data centers within the European Union. It is not possible to configure which data centers are selected or where they are located within the multi-region.

If you use Google Kubernetes Engine Image streaming, your Artifact Registry repository must be in the same region as your GKE nodes, or in a multi-region that corresponds with the region where your nodes are running. For example:

• If your nodes are in us-east1, Image streaming is available for repositories in the us-east1 region or the us multi-region since both GKE and Artifact Registry are running in data center locations within the United States.
• If your nodes are in the northamerica-northeast1 region, the nodes are running in Canada. In this situation, Image streaming is only available for repositories in the same region.

¹ Object data added to a repository in the europe multi-region is not stored in the europe-west2 or europe-west6 data center.

What's next

• Create repositories
• Learn more about location concepts