Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Saat membuat repositori, Anda harus menentukan lokasinya. Lokasi
yang dipilih menentukan tempat penyimpanan repositori dibuat. Anda dapat
membuat repositori di jenis lokasi berikut:
Region adalah lokasi geografis tertentu, seperti Tokyo atau Northern Virginia.
Multi-region adalah wilayah geografis yang luas, seperti Asia atau Amerika Serikat, yang berisi dua atau lebih tempat geografis.
Lokasi yang baik menyeimbangkan biaya latensi, ketersediaan, dan bandwidth untuk konsumen data.
Gunakan region untuk membantu mengoptimalkan latensi dan bandwidth jaringan untuk upload
dan download oleh sistem yang berada di region yang sama.
Gunakan multi-region jika Anda ingin berinteraksi dengan sistem yang berada di luar jaringan Google dan didistribusikan di wilayah geografis yang luas, atau jika Anda menginginkan ketersediaan yang lebih tinggi yang disertai dengan redundansi di seluruh region.
Umumnya, Anda harus menyimpan artefak di lokasi yang mudah dijangkau atau
berisi sebagian besar pengguna data Anda.
Untuk Compute Engine
Menyimpan data di region yang sama dengan instance VM Compute Engine dapat memberikan performa yang lebih baik.
Meskipun Anda tidak dapat menentukan lokasi repositori zona Compute Engine, semua instance VM Compute Engine di zona dalam region tertentu memiliki performa yang serupa saat mengakses penyimpanan di region tersebut.
Untuk melihat daftar lokasi repositori yang didukung, jalankan perintah:
gcloudartifactslocationslist
Batasan lokasi
Organisasi Anda mungkin memiliki persyaratan khusus untuk lokasi
data yang disimpan. Jika kebijakan organisasi Anda menyertakan
batasan lokasi resource,
Artifact Registry akan menerapkan batasan tersebut saat Anda membuat repositori.
Kepatuhan kebijakan organisasi tidak diterapkan secara surut pada repositori yang ada. Untuk menerapkan batasan lokasi baru pada artefak yang disimpan,
buat repositori baru setelah kebijakan organisasi diterapkan, lalu
migrasikan artefak dari repositori lama ke repositori baru. Anda dapat menggunakan alat gcrane untuk menyalin image antar-repositori.
Wilayah yang tersedia
Benua
Nama Region
Deskripsi Region
Amerika Utara
northamerica-northeast1
Montréal
northamerica-northeast2
Toronto
northamerica-south1
Queretaro
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
Amerika Selatan
southamerica-east1
Sao Paulo
southamerica-west1
Santiago
Eropa
europe-central2
Warsawa
europe-north1
Finlandia
europe-north2
Stockholm
europe-southwest1
Madrid
europe-west1
Belgia
europe-west2
London
europe-west3
Frankfurt
europe-west4
Belanda
europe-west6
Zürich
europe-west8
Milan
europe-west9
Paris
europe-west10
Berlin
europe-west12
Turin
Timur Tengah
me-central1
Doha
me-central2
Dammam
me-west1
Tel Aviv
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
Singapura
asia-southeast2
Jakarta
Australia
australia-southeast1
Sydney
australia-southeast2
Melbourne
Afrika
africa-south1
Johannesburg
Multi-region yang tersedia
Pusat data lokasi multi-regional tersebar di area geografis umum. Misalnya, resource yang dibuat di multi-region europe akan tetap ada di beberapa pusat data dalam Uni Eropa. Anda tidak dapat mengonfigurasi pusat data mana yang dipilih atau lokasinya dalam multi-region.
Jika Anda menggunakan Streaming image Google Kubernetes Engine, repositori Artifact Registry
Anda harus berada di region yang sama dengan node GKE
Anda, atau di multi-region yang sesuai dengan region tempat node Anda
berjalan. Contoh:
Jika node Anda berada di us-east1, streaming Image tersedia untuk
repositori di region us-east1 atau multi-region us karena
GKE dan Artifact Registry berjalan di lokasi pusat data di
Amerika Serikat.
Jika node Anda berada di region northamerica-northeast1, node tersebut
berjalan di Kanada. Dalam situasi ini, streaming Image hanya tersedia
untuk repositori di region yang sama.
Nama Multi-Region
Deskripsi Multi-Region
asia
Pusat data di Asia
europe
Pusat data di Uni Eropa1
us
Pusat data di Amerika Serikat
1 Data objek yang ditambahkan ke repositori di multi-region europe tidak disimpan di pusat data europe-west2 atau europe-west6.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 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)"]]
