Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dukungan IPv6 di Google Cloud
Dokumen ini menjelaskan layanan di Google Cloud yang menyertakan dukungan untuk IPv6.
IPv6 memiliki ruang alamat yang jauh lebih besar daripada IPv4, dengan 128 bit per alamat. IPv6
memiliki lebih banyak alamat yang tersedia daripada IPv4, yang membantu mengurangi
kekurangan alamat IPv4 yang terus meningkat.
Dukungan IPv6 tersedia secara luas di Google Cloud melalui layanan komputasi dan jaringan dual-stack
(IPv4 dan IPv6) serta khusus IPv6. Anda dapat men-deploy subnet dual-stack dan khusus IPv6, yang memungkinkan Anda men-deploy beban kerja IPv6.
Anda dapat mengontrol konfigurasi IPv6 menggunakan batasan kebijakan organisasi
seperti yang dijelaskan di bagian
batasan kebijakan organisasi
pada ringkasan jaringan VPC.
Layanan komputasi dan jaringan inti
Tabel berikut merangkum dukungan untuk IPv6 di layanan komputasi dan jaringan inti di Google Cloud.
Jika layanan memiliki opsi konfigurasi jenis stack IP, tabel akan mencantumkan
jenis stack yang didukung. Jenis stack khusus IPv6 tersedia untuk beberapa layanan yang ditandai dalam tabel. Jika opsi konfigurasi jenis stack tidak tersedia untuk layanan, tabel akan mencantumkan tidak berlaku (N/A).
Untuk mengetahui informasi selengkapnya tentang layanan tertentu, lihat dokumentasi yang sesuai.
Instance khusus IPv6 hanya mendukung sistem operasi Debian dan Ubuntu.
Instance khusus IPv6 tidak mendukung DNS Internal Compute Engine.
2
Untuk MIG, endpoint pemulihan otomatis hanya mendukung IPv4.
3
Peering Jaringan VPC dan lampiran VLAN Cloud Interconnect itu sendiri hanya dapat
dikonfigurasi sebagai stack ganda, bukan hanya IPv6. Namun, jika dikonfigurasi sebagai
dual-stack, resource ini kompatibel dengan resource khusus IPv6 seperti subnet dan
instance.
4
Cloud DNS tidak mendukung IPv6 untuk penerusan masuk.
5
Untuk NAT64, NAT Publik mendukung instance VM generasi kedua atau yang lebih lama dan instance VM M3. Untuk mengetahui informasi selengkapnya, lihat
Terminologi Compute Engine.
6
Dukungan khusus IPv6 terbatas pada backend grup instance yang tidak dikelola dan penerusan
protokol dengan instance target khusus IPv6.
Layanan aplikasi
Tabel berikut merangkum dukungan untuk IPv6 di API dan layanan Google yang umum digunakan.
Untuk layanan yang mendukung akses IPv6 pribadi, akses pribadi dari klien IPv6 didukung oleh Akses Google Pribadi.
1
Beberapa produk memiliki API administratif yang berjalan di infrastruktur produksi Google dan dapat diakses oleh klien IPv6, tetapi API tersebut membuat resource yang dihosting VPC yang tidak dapat diakses oleh klien IPv6. Misalnya,
Memorystore for Memcached memiliki API administratif di memcache.googleapis.com.
Dengan API ini, Anda dapat melakukan beberapa tugas administratif untuk instance Memorystore for Memcached, tetapi Anda harus menggunakan akses layanan pribadi untuk mengakses instance Memorystore for Memcached.
Detail tambahan tentang layanan aplikasi dan IPv6
Ada dua jenis API dan layanan Google:
Layanan yang berjalan di infrastruktur produksi Google, termasuk semua
endpoint layanan *.googleapis.com.
Layanan yang berjalan di jaringan VPC yang dijalankan oleh Google
(juga dikenal sebagai layanan yang dihosting VPC), seperti Cloud SQL dan
Filestore.
Sebagian besar layanan yang berjalan di infrastruktur produksi Google mendukung akses oleh klien dengan alamat IPv6:
Akses publik dari klien IPv6 didukung.
Akses pribadi dari klien IPv6 didukung melalui metode berikut:
Akses layanan pribadi tidak mendukung akses oleh klien yang memiliki alamat IPv6. Untuk mengetahui informasi selengkapnya, lihat Layanan yang didukung
dalam dokumentasi akses layanan pribadi.
[[["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-09-05 UTC."],[],[],null,["# IPv6 support in Google Cloud\n============================\n\nThis document describes which services in Google Cloud include support for IPv6.\n\nIPv6 has a much larger address space than IPv4, with 128 bits per address. IPv6\nhas many more addresses available than IPv4 does, which helps mitigate the\ngrowing shortage of IPv4 addresses.\n\nIPv6 support is widely available in Google Cloud through dual-stack\n(IPv4 and IPv6) and IPv6-only compute and networking services. You can\ndeploy dual-stack and IPv6-only subnets, which lets you deploy IPv6 workloads.\n\nYou can control IPv6 configurations by using organization policy constraints\nas described in the\n[organization policy constraints](/vpc/docs/vpc#org-policies)\nsection of the VPC networks overview.\n| **Note:** IPv6 functionality is available only in [Premium Tier](/network-tiers/docs/overview#resources).\n\nCore compute and networking services\n------------------------------------\n\nThe following table summarizes support for IPv6 in core compute and\nnetworking services in Google Cloud.\n\nIf a service has an IP stack type configuration option, the table lists the\nsupported stack types. The IPv6-only\nstack type is available for some services where marked in the table. If a\nservice doesn't have a stack type configuration option, the table lists\nnot applicable (N/A).\n\nFor more information about a given service, see the corresponding documentation.\n\n^1^ See the following limitations:\n\n- IPv6-only instances support only Debian and Ubuntu [operating systems](/compute/docs/images/os-details).\n- IPv6-only instances don't support Compute Engine [Internal DNS](/compute/docs/internal-dns). \n^2^ For MIGs, the autohealing endpoint supports only IPv4. \n^3^ VPC Network Peering and Cloud Interconnect VLAN attachments themselves can only be configured as dual-stack and not IPv6-only. However, when configured as dual-stack they are compatible with IPv6-only resources such as subnets and instances. \n^4^ For NAT64, Public NAT supports second generation or earlier VM instances and M3 VM instances. For more information, see [Compute Engine terminology](/compute/docs/machine-resource#vm_terminology). \n^5^ Cloud DNS doesn't support IPv6 for inbound forwarding. \n^6^ IPv6-only support is limited to unmanaged instance group backends and protocol forwarding with IPv6-only target instances.\n\nApplication services\n--------------------\n\nThe following table summarizes support for IPv6 in commonly used Google\nAPIs and services.\n\nFor services that support private IPv6 access, private access from IPv6 clients\nis supported by\n[Private Google Access](/vpc/docs/configure-private-google-access).\n\nFor more information, see\n[Additional details about application services and IPv6](#additional-details).\n\n^1^ Some products have an administrative API that runs on Google's production infrastructure and can be accessed by IPv6 clients, but the API creates VPC-hosted resources that can't be accessed by IPv6 clients. For example, Memorystore for Memcached has an administrative API at `memcache.googleapis.com`. Using this API lets you perform some administrative tasks for your Memorystore for Memcached instances, but you must use [private services access](/memorystore/docs/memcached/networking#private_services_access) to access the Memorystore for Memcached instances.\n\n### Additional details about application services and IPv6\n\nThere are two varieties of Google APIs and services:\n\n- Services that run on Google's production infrastructure, including all `*.googleapis.com` service endpoints.\n- Services that run in VPC networks that are run by Google (also known as *VPC-hosted services*), such as Cloud SQL and Filestore.\n\nMost services that run on Google's production infrastructure support access by\nclients with IPv6 addresses:\n\n- Public access from IPv6 clients is supported.\n\n- Private access from IPv6 clients is supported through the following methods:\n\n - [Private Google Access](/vpc/docs/private-google-access). For more\n information, including supported services, see [Domain\n options](/vpc/docs/configure-private-google-access#domain-options).\n\n - [Private Service Connect\n endpoints](/vpc/docs/about-accessing-regional-google-apis-endpoints) for\n [regional Google APIs](/vpc/docs/regional-service-endpoints). This type\n of endpoint can be configured with either an IPv4 or IPv6\n address---you must configure an IPv6 address to let IPv6 clients use\n it.\n\n However, you can't use [Private Service Connect endpoints for\n global Google APIs](/vpc/docs/about-accessing-google-apis-endpoints)\n to access services from IPv6 clients. This type of endpoint can be\n configured with an IPv4 address only.\n\nFor more information about services that run on Google's infrastructure, see the\n[Google APIs Explorer](https://developers.google.com/apis-explorer).\n\nFor VPC-hosted services, support for access by IPv6 clients\ndepends on the [private access option](/vpc/docs/private-access-options) that\nyou use:\n\n- You can create IPv6 Private Service Connect endpoints to let clients with IPv6 addresses [access published services](/vpc/docs/about-accessing-vpc-hosted-services-endpoints).\n- Private services access doesn't support access by clients that have IPv6 addresses. For more information, see the [Supported services](/vpc/docs/private-services-access#private-services-supported-services) in the private services access documentation."]]
