When you create a repository, you must specify its location. The chosen location determines where the repository storage is created. This location is called a Region, and it represents a specific geographic place such as Tokyo or London.
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.
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.