Es posible que parte de la información de esta página (o toda) no se aplique a Trusted Cloud de S3NS.
Ubicaciones de Artifact Registry
Cuando creas un repositorio, debes especificar su ubicación. La ubicación elegida determina dónde se crea el almacenamiento del repositorio. Esta ubicación se denomina región y representa un lugar geográfico específico, como Tokio o Londres.
Artifact Registry almacena artefactos en la ubicación seleccionada en función de los Términos específicos del servicio.
Una buena ubicación balancea los costos de latencia, disponibilidad y ancho de banda para los consumidores de datos.
- Usa una región que ayude a optimizar la latencia y el ancho de banda de la red para las cargas y descargas que realizan los sistemas ubicados en la misma región.
En general, debes almacenar tus artefactos en una ubicación que sea conveniente o que contenga a la mayoría de los usuarios de tus datos.
Para Compute Engine, haz lo siguiente:
- Almacenar datos en la misma región que tus instancias de VM de Compute Engine puede proporcionar un mejor rendimiento.
- Si bien no puedes especificar una ubicación del repositorio de las zonas de Compute Engine, todas las instancias de VM de Compute Engine en las zonas dentro de una región determinada tienen un rendimiento similar cuando se accede al almacenamiento de esa región.
Para ver una lista de las ubicaciones de los repositorios compatibles, ejecuta el siguiente comando:
gcloud artifacts locations list
Restricciones de ubicación
Es posible que tu organización tenga requisitos específicos para la ubicación de los datos almacenados. Si la política de tu organización incluye
restricciones de ubicación de recursos,
Artifact Registry aplica las restricciones cuando creas un repositorio.
El cumplimiento de las políticas de la organización no se aplica forzosamente de forma retroactiva a los repositorios existentes. Para aplicar nuevas restricciones de ubicación en artefactos almacenados existentes, crea repositorios nuevos después de aplicar la política de la organización y, luego, migra los artefactos de los repositorios antiguos a los nuevos. Puedes usar la herramienta gcrane para copiar imágenes entre repositorios.
¿Qué sigue?
Salvo que se indique lo contrario, el contenido de esta página está sujeto a la licencia Atribución 4.0 de Creative Commons, y los ejemplos de código están sujetos a la licencia Apache 2.0. Para obtener más información, consulta las políticas del sitio de Google Developers. Java es una marca registrada de Oracle o sus afiliados.
Última actualización: 2025-08-18 (UTC)
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Falta la información que necesito","missingTheInformationINeed","thumb-down"],["Muy complicado o demasiados pasos","tooComplicatedTooManySteps","thumb-down"],["Desactualizado","outOfDate","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Problema con las muestras o los códigos","samplesCodeIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-08-18 (UTC)"],[[["\u003cp\u003eRepositories in Artifact Registry must be assigned a location, which can be either a specific region, like Tokyo, or a multi-region, such as Asia.\u003c/p\u003e\n"],["\u003cp\u003eChoosing a region helps optimize latency and network bandwidth for systems located in that same region, while multi-regions are better for interactions with systems outside the Google network or requiring high availability.\u003c/p\u003e\n"],["\u003cp\u003eStoring artifacts in the same region as Compute Engine VM instances can enhance performance, and while a specific zone cannot be selected for a repository, VMs within the same region will experience similar performance.\u003c/p\u003e\n"],["\u003cp\u003eOrganization policies may enforce location constraints on repositories, and if existing repositories need to adhere to these new constraints, new repositories must be created and artifacts migrated to them.\u003c/p\u003e\n"],["\u003cp\u003eMulti-regions include the geographic areas of \u003ccode\u003easia\u003c/code\u003e, \u003ccode\u003eeurope\u003c/code\u003e, and \u003ccode\u003eus\u003c/code\u003e, and when using Image streaming with Google Kubernetes Engine, the repository must be in the same region as the GKE nodes, or a multi-region corresponding to the nodes' region.\u003c/p\u003e\n"]]],[],null,["# Artifact Registry locations\n\nWhen you create a repository, you must specify its location. The\nchosen location determines where the repository storage is created. You can\ncreate repositories in the following types of locations:\n\n- *Region* is a specific geographic place, such as Tokyo or Northern Virginia.\n\n- *Multi-region* is a large geographic area, such as Asia or the\n United States, that contains two or more geographic places.\n\nArtifact Registry stores artifacts in the selected location in\naccordance with the [Service Specific Terms](/terms/service-terms).\n\nA good location balances latency, availability, and bandwidth costs for data\nconsumers.\n\n- Use a region to help optimize latency and network bandwidth for uploads and downloads by systems located in the same region.\n\n\u003c!-- --\u003e\n\n- 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](/storage/docs/availability-durability#cross-region-redundancy).\n\n\u003c!-- --\u003e\n\n- Generally, you should store your artifacts in a location that is convenient or\n contains the majority of the users of your data.\n\n- For Compute Engine\n\n - Storing data in the same region as your [Compute Engine VM instances](/compute/docs/instances) can provide better performance.\n - 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.\n\nTo view a list of supported repository locations, run the command: \n\n gcloud artifacts locations list\n\nLocation constraints\n--------------------\n\nYour organization might have specific requirements for the location of\nstored data. If your organization policy includes\n[resource location constraints](/resource-manager/docs/organization-policy/defining-locations),\nArtifact Registry enforces the constraints when you create a repository.\n\nOrganization policy compliance isn't enforced retroactively on existing\nrepositories. To enforce new location constraints on existing stored artifacts,\ncreate new repositories after the organization policy is applied, and then\nmigrate artifacts from old repositories to the new ones. You can use the [gcrane](https://github.com/google/go-containerregistry/tree/main/cmd/gcrane)\ntool to copy images between repositories.\n\nAvailable regions\n-----------------\n\nAvailable multi-regions\n-----------------------\n\nA multi-regional location's data centers are spread across a general\ngeographical area. For example, a resource created in the `europe` multi-region\npersists in multiple data centers within the European Union. It is not possible\nto configure which data centers are selected or where they are located within\nthe multi-region.\n\nIf you use Google Kubernetes Engine [Image streaming](/kubernetes-engine/docs/how-to/image-streaming), your Artifact Registry\nrepository must be in the same [region](#location-r) as your GKE\nnodes, or in a multi-region that corresponds with the region where your nodes\nare running. For example:\n\n- 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.\n- 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.\n\n^1^ Object data added to a repository in the `europe` multi-region\nis not stored in the `europe-west2` or `europe-west6` data center.\n\nWhat's next\n-----------\n\n- [Create repositories](/artifact-registry/docs/repositories/create-repos)\n- [Learn more about location concepts](/docs/geography-and-regions)"]]
