Memilih lokasi Anda

Catatan: Halaman ini berisi petunjuk tentang produk AWS. Google tidak menjamin bahwa panduan ini adalah yang terbaru atau bahwa contoh pilihan konfigurasi tersebut ideal untuk kasus penggunaan Anda. Untuk mengetahui informasi terbaru, lihat dokumentasi AWS .

Saat Anda menggunakan Cross-Cloud Interconnect, Google menyediakan koneksi fisik atas nama Anda antara jaringan Google Cloud dan jaringan Amazon Web Services (AWS).

Sebelum Google dapat membuat koneksi ini, Anda harus memesan port dari Google dan AWS. Sebagai persiapan untuk proses tersebut, identifikasi lokasi Google Cloud dan lokasi AWS terkait yang ingin Anda gunakan untuk koneksi.

Praktik terbaik untuk memilih lokasi

Ketika memutuskan di mana Anda akan menempatkan koneksi, pertimbangkan pertanyaan seperti berikut:

• Di mana sebagian besar resource Google Cloud Anda?
• Di mana sebagian besar resource AWS Anda?

Jika resource Anda dari kedua cloud ada di tempat yang sama, maka pilihannya menjadi sederhana. Namun, jika tidak, pertimbangkan apakah Anda ingin koneksi Anda lebih dekat dengan resource Google Cloud atau lebih dekat dengan resource AWS Anda. Jika koneksinya lebih dekat dengan resource AWS Anda, traffic Anda akan menghabiskan lebih banyak waktu untuk menjelajahi jaringan Google, yang pada umum diinginkan. Namun, Anda juga harus mempertimbangkan biaya transfer data keluar yang kemungkinan akan Anda kenai dari kedua cloud.

Faktor yang dipengaruhi oleh lokasi

Bagian ini menjelaskan faktor-faktor yang dipengaruhi oleh pilihan lokasi Anda.

Lampiran VLAN

Setelah koneksi Cross-Cloud Interconnect dibuat, Anda harus mengonfigurasi lampiran VLAN di Google Cloud. Lampiran VLAN adalah koneksi logis antara jaringan cloud jarak jauh dan satu region dalam jaringan Virtual Private Cloud Anda.

Saat memilih lokasi port, Anda membatasi jumlah region tempat Anda dapat menempatkan lampiran VLAN. Karena alasan ini, tabel lokasi yang didukung menyertakan kolom untuk region Google Cloud yang disalurkan oleh setiap lokasi port.

Catatan: Di Google Cloud, lokasi lampiran VLAN tidak harus membatasi region Google Cloud mana yang menerima rute AWS Anda. Untuk mengiklankan rute AWS ke semua region Google Cloud Anda, konfigurasikan perutean dinamis global.

Domain ketersediaan Edge

Setiap area metropolitan memiliki dua domain ketersediaan Google Cloud edge. Dua domain di area metropolitan yang sama tidak dijadwalkan untuk dihentikan sementara guna pemeliharaan pada waktu yang sama. Oleh karena itu, saat Anda memilih lokasi untuk port utama dan redundan, setiap port harus menggunakan domain ketersediaan edge yang berbeda dalam area metropolitan yang sama. Hal ini berlaku terlepas dari cara Anda mengurutkan port. Namun, saat menggunakan Google Cloud CLI, Anda harus menentukan setiap domain ketersediaan edge secara eksplisit. Saat menggunakan Google Cloud Console, cukup pilih lokasi dan Google Cloud akan mencadangkan port untuk Anda di setiap domain.

Dalam versi gcloud CLI dari nama lokasi, domain ketersediaan edge adalah informasi bagian kedua. Misalnya, jika nama lokasi adalah iad-zone1-1, domain ketersediaan edge adalah zone1. Jika nama lokasinya adalah iad-zone2-1, zona ketersediaan edge adalah zone2.

Fasilitas kolokasi

Google biasanya menyediakan setiap koneksi dalam satu fasilitas kolokasi. Namun, terkadang koneksi dibuat di antara fasilitas yang bersebelahan yang dioperasikan oleh penyedia yang sama. Dalam kedua kasus tersebut, umumnya Anda tidak perlu mengetahui nama fasilitasnya. Oleh karena itu, tabel lokasi yang didukung tidak mengidentifikasi fasilitas tertentu.

Daftar lokasi yang didukung

Tabel berikut berisi lokasi AWS yang didukung dan lokasi Google Cloud yang sesuai.

Anda harus menentukan lokasi Google Cloud dari port Cross-Cloud Interconnect Anda, dan tentukan pula lokasi penyedia cloud lain untuk menyambungkannya. Lokasi AWS yang terakhir disebut sebagai lokasi jarak jauh dalam set dokumentasi ini dan di dalam Google Cloud. Pastikan untuk menggunakan nama lokasi jarak jauh saat Anda memesan Cross-Cloud Interconnect. Penyedia cloud jarak jauh memiliki nama yang berbeda, meskipun mirip, nama lokasi, yang Anda gunakan saat memesan port dengan penyedia cloud tersebut.

Ada beberapa variasi sintaksis untuk setiap nama lokasi. Contoh:

• Nama lokasi jarak jauh bervariasi bergantung pada apakah Anda berinteraksi dengan AWS atau Google Cloud.
• Saat berinteraksi dengan Google Cloud, Google Cloud Console menampilkan description lokasi jarak jauh di samping nama lokasi untuk membantu Anda memilih lokasi yang benar.
• Di Google Cloud, lokasi Cloud Interconnect dari konsol Google Cloud (bukan lokasi jarak jauh) menampilkan informasi fasilitas, bukan nama lokasi Cloud Interconnect yang sebenarnya.

Catatan: Anda juga dapat menggunakan gcloud CLI untuk mencantumkan lokasi. Untuk informasi selengkapnya, lihat halaman referensi untuk gcloud compute interconnects remote-locations list perintah.

Region Google Cloud	Region Amazon Web Services	Daerah metropolitan	Lokasi jarak jauh		Lokasi Google Cloud
			Google Cloud	Amazon Web Services
asia-east1 asia-east2 asia-northeast1 asia-northeast2 asia-northeast3 asia-southeast1 asia-southeast2	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Hong Kong	aws-eqhk1	EQHK1	hkg-zone1-1118 hkg-zone2-1118
asia-east1 asia-east2 asia-northeast1 asia-northeast2 asia-northeast3 asia-southeast1 asia-southeast2	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Jakarta	aws-dcij3	DCIJ3	cgk-zone1-8168 cgk-zone2-8168
asia-east1 asia-east2 asia-northeast1 asia-northeast2 asia-northeast3 asia-southeast1 asia-southeast2	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Osaka	aws-eqos1	EqOS1	kix-zone1-1791 kix-zone2-1791
asia-east1 asia-east2 asia-northeast1 asia-northeast2 asia-northeast3 asia-southeast1 asia-southeast2	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Seoul	aws-lgu57	LGU57	icn-zone1-7573 icn-zone2-7573
			aws-lgknx	LGKNX	icn-zone1-7674 icn-zone2-7674
asia-east1 asia-east2 asia-northeast1 asia-northeast2 asia-northeast3 asia-southeast1 asia-southeast2	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Singapura	aws-gss52	GSS52	sin-zone1-388 sin-zone2-388
asia-east1 asia-east2 asia-northeast1 asia-northeast2 asia-northeast3 asia-southeast1 asia-southeast2	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Tokyo	aws-eqty2	EqTY2	nrt-zone1-452 nrt-zone2-452
australia-southeast1 australia-southeast2	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Sydney	aws-eqsy3	EqSY3	syd-zone1-1605 syd-zone2-1605
me-central1 me-central2 me-west1 europe-central2 europe-north1 europe-southwest1 europe-west1 europe-west2 europe-west3 europe-west4 europe-west5 europe-west6 europe-west8 europe-west9 europe-west10 europe-west12	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Frankfurt	aws-inx6	INX6	fra-zone1-58 fra-zone2-58
			aws-eqfa5	EqFA5	fra-zone1-683 fra-zone2-683
me-central1 me-central2 me-west1 europe-central2 europe-north1 europe-southwest1 europe-west1 europe-west2 europe-west3 europe-west4 europe-west5 europe-west6 europe-west8 europe-west9 europe-west10 europe-west12	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	London	aws-eqld5	EqLD5	lhr-zone1-832 lhr-zone2-832
me-central1 me-central2 me-west1 europe-central2 europe-north1 europe-southwest1 europe-west1 europe-west2 europe-west3 europe-west4 europe-west5 europe-west6 europe-west8 europe-west9 europe-west10 europe-west12	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Madrid	aws-itcm2	ITCM2	mad-zone1-127 mad-zone2-127
me-central1 me-central2 me-west1 europe-central2 europe-north1 europe-southwest1 europe-west1 europe-west2 europe-west3 europe-west4 europe-west5 europe-west6 europe-west8 europe-west9 europe-west10 europe-west12	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Paris	aws-itxp7	ITXP7	cdg-zone1-1536 cdg-zone2-1536
			aws-thv52	THV52	cdg-zone1-53 cdg-zone2-53
me-central1 me-central2 me-west1 europe-central2 europe-north1 europe-southwest1 europe-west1 europe-west2 europe-west3 europe-west4 europe-west5 europe-west6 europe-west8 europe-west9 europe-west10 europe-west12	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Stockholm	aws-eqsk1	EQSK1	arn-zone1-156 arn-zone2-156
asia-southeast1 asia-south1 asia-south2	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Mumbai	aws-gpx51	GPX51	bom-zone1-2310 bom-zone2-2310
northamerica-northeast1 northamerica-northeast2 us-central1 us-east1 us-east4 us-east5 us-south1 us-west1 us-west2 us-west3 us-west4	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Washington D.C.	aws-eqdc2	EqDC2	iad-zone1-1 iad-zone2-1
			aws-csva1	CSVA1	iad-zone1-5467 iad-zone2-5467
northamerica-northeast1 northamerica-northeast2 us-central1 us-east1 us-east4 us-east5 us-south1 us-west1 us-west2 us-west3 us-west4	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Ohio	aws-col67	COL67	cmh-zone1-2377 cmh-zone2-2377
northamerica-northeast1 northamerica-northeast2 us-central1 us-east1 us-east4 us-east5 us-south1 us-west1 us-west2 us-west3 us-west4	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Dallas, Texas	aws-eqda2	Equinix EqDA2	dfw-zone1-4 dfw-zone2-4
northamerica-northeast1 northamerica-northeast2 us-central1 us-east1 us-east4 us-east5 us-south1 us-west1 us-west2 us-west3 us-west4	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Montréal	aws-cgm60	CGM60	yul-zone1-1944 yul-zone2-1944
northamerica-northeast1 northamerica-northeast2 us-central1 us-east1 us-east4 us-east5 us-south1 us-west1 us-west2 us-west3 us-west4	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Portland, Oregon	aws-ecpo1	ECPO1	pdx-zone1-1922 pdx-zone2-1922
northamerica-northeast1 northamerica-northeast2 us-central1 us-east1 us-east4 us-east5 us-south1 us-west1 us-west2 us-west3 us-west4	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	San Francisco	aws-eqsv5	EqSV5	sjc-zone1-6 sjc-zone2-6
northamerica-northeast1 northamerica-northeast2 us-central1 us-east1 us-east4 us-east5 us-south1 us-west1 us-west2 us-west3 us-west4	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Seattle	aws-eqse2-eq	EqSe2-EQ, sublokasi Equinix SE2	sea-zone1-86 sea-zone2-86
southamerica-east1 southamerica-west1 us-east1	af-south-1 ap-east-1 ap-northeast-1 ap-northeast-2 ap-northeast-3 ap-south-1 ap-south-2 ap-southeast-1 ap-southeast-2 ap-southeast-3 ca-central-1 eu-central-2 eu-north-1 eu-south-1 eu-south-2 eu-west-1 eu-west-2 eu-west-3 me-central-1 me-south-1 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2	Sao Paulo	aws-tndb	TNDB	gru-zone1-165 gru-zone2-165

Memverifikasi ketersediaan

Setelah Anda mengidentifikasi lokasi yang ingin digunakan, periksa kembali apakah lokasi tersebut memiliki port Direct Connect 10-Gbps atau 100-Gbps yang tersedia. Langkah ini berguna karena ketersediaan port dapat berubah tanpa adanya pemberitahuan.

Jika bekerja di konsol AWS, Anda dapat memverifikasi ketersediaan saat memesan koneksi. Untuk memverifikasi ketersediaan di awal, gunakan AWS CLI.

CLI AWS

Gunakan describe-locations perintah untuk mendapatkan informasi tentang koneksi yang tersedia di lokasi AWS. Contoh:

aws directconnect describe-locations --region REGION | jq -r '.locations[] | select(.locationCode | test("REMOTE_LOCATION"; "i")) | .availablePortSpeeds'

Ganti kode berikut:

• REGION: nama region AWS—misalnya, us-east-2
• REMOTE_LOCATION: nama AWS dari lokasi jarak jauh—misalnya, CSVA1

Output perintah menunjukkan kecepatan port yang tersedia.

      [
        "100 Gbps",
        "10 Gbps",
        "1 Gbps"
      ]

Perhatikan lokasi dan region

Setelah Anda meninjau bagian sebelumnya, catat nilai berikut:

• Lokasi jarak jauh, seperti yang dikenal di Google Cloud, dan lokasi Google Cloud. Nilai-nilai ini diperlukan saat Anda memesan koneksi Cross-Cloud Interconnect.
• Lokasi jarak jauh, seperti yang dikenal di AWS, dan region tempat Anda ingin menempatkan resource koneksi. Anda memerlukan nilai ini saat memesan port AWS dan mengonfigurasi resource AWS.
• Region Google Cloud tempat Anda ingin menempatkan lampiran VLAN. Anda memerlukan nilai ini saat membuat lampiran, seperti yang dijelaskan dalam Mengonfigurasi resource Google Cloud.