Beberapa atau semua informasi di halaman ini mungkin tidak berlaku untuk Trusted Cloud oleh S3NS.
Kuota dan batas
Dokumen ini mencantumkan kuota dan batas sistem yang berlaku untuk Cloud NAT.
- Kuota menentukan jumlah resource bersama yang dapat dihitung dan dapat Anda
gunakan. Kuota ditentukan oleh Trusted Cloud by S3NS layanan seperti
NAT Cloud.
- Batas sistem adalah nilai tetap yang tidak dapat diubah.
Kuota atau batas tertentu dihitung per resource. Kuota dan batas dapat berupa per project, per network, per region, atau per resource lain. Alamat IP NAT tidak dapat dibagikan antar-gateway NAT.
Trusted Cloud by S3NS menggunakan kuota untuk membantu memastikan keadilan dan mengurangi
lonjakan penggunaan dan ketersediaan resource. Kuota membatasi jumlah
Trusted Cloud resource yang dapat digunakan Trusted Cloud project Anda. Kuota
berlaku untuk berbagai jenis resource, termasuk komponen hardware, software, dan jaringan. Misalnya, kuota dapat membatasi jumlah panggilan API ke
layanan, jumlah load balancer yang digunakan secara bersamaan oleh project Anda, atau
jumlah project yang dapat Anda buat. Kuota melindungi komunitas penggunaTrusted Cloud dengan mencegah kelebihan beban layanan. Kuota juga
membantu Anda mengelola resource Trusted Cloud Anda sendiri.
Sistem Kuota Cloud melakukan hal berikut:
Pada umumnya, saat Anda mencoba menggunakan resource lebih dari kuota yang diizinkan, sistem akan memblokir akses ke resource, dan tugas yang Anda coba lakukan akan gagal.
Kuota umumnya berlaku di Trusted Cloud level project. Penggunaan resource di satu project tidak memengaruhi
kuota yang tersedia di project lain. Dalam project Trusted Cloud , kuota
dibagikan di semua aplikasi dan alamat IP.
Ada juga batas sistem pada resource Cloud NAT.
Batas sistem tidak dapat diubah.
Kuota
Untuk kuota yang memengaruhi Cloud NAT, lihat halaman kuota Cloud Router.
Batas
| Item |
Batas |
Catatan |
| Gateway NAT |
50 per Cloud Router |
Setiap jaringan mendukung hingga 5 instance Cloud Router per
region, sehingga Anda dapat memiliki hingga 250 gateway Cloud NAT per
region per jaringan Virtual Private Cloud (VPC). Untuk kuota Cloud Router,
lihat dokumentasi Cloud Router. |
| Alamat IP NAT per gateway |
300 alamat manual
2.500 alamat yang dialokasikan secara otomatis |
Jumlah maksimum alamat IP eksternal yang dapat Anda miliki di gateway NAT. Namun, nilai ini bergantung pada kuota alamat IP statis
dan alamat IP yang digunakan
VPC per project. |
| Rentang subnet |
50 per gateway |
Jumlah maksimum subnet yang dapat Anda kaitkan dengan gateway saat mengonfigurasi daftar rentang subnet kustom. Jumlah rentang subnet
mungkin lebih dari batas karena setiap subnet dapat memiliki rentang IPv4 primer
dan satu atau beberapa rentang sekunder.
Jika Anda telah mengonfigurasi NAT untuk rentang primer untuk semua subnet atau rentang primer
dan sekunder untuk semua subnet, batas ini tidak berlaku. |
| Aturan NAT |
50 per gateway |
Jika batas ini terlampaui, API akan menampilkan error. |
| Alamat IP aktif per aturan NAT |
300 |
|
| Karakter dalam ekspresi CEL per aturan |
2.048 |
|
| Karakter dalam ekspresi CEL per instance Cloud Router |
500.000 |
|
Batasan
Beberapa server seperti server DNS lama memerlukan pengacakan port UDP di antara
64.000 port untuk meningkatkan keamanan. Karena Cloud NAT memilih port secara random
dari salah satu dari 64 port atau jumlah port yang dikonfigurasi pengguna, sebaiknya tetapkan
alamat IP eksternal ke server ini, bukan menggunakan Cloud NAT.
Karena Cloud NAT tidak mengizinkan koneksi yang dimulai dari luar,
sebagian besar server ini tetap harus menggunakan alamat IP eksternal.
Cloud NAT tidak tersedia untuk jaringan lama.
Cloud NAT tidak menyediakan kemampuan gateway level aplikasi (ALG)—Cloud NAT tidak memperbarui alamat IP dan informasi port dalam data paket untuk protokol lapisan aplikasi seperti FTP dan SIP.
Gateway Cloud NAT menerapkan tabel pelacakan koneksi NAT untuk setiap antarmuka jaringan VM tempat layanan NAT disediakan. Entri di setiap
tabel pelacakan koneksi adalah hash 5-tuple untuk protokol gateway
yang didukung.
Entri di setiap tabel pelacakan koneksi akan tetap ada selama waktu tunggu NAT yang relevan. Untuk mengetahui informasi selengkapnya tentang waktu tunggu NAT, lihat
Waktu tunggu NAT.
Jumlah maksimum entri tabel pelacakan koneksi untuk semua koneksi
NAT yang terkait dengan VM adalah 65.535. Nilai maksimum ini mencakup koneksi,
secara agregat, untuk semua protokol yang didukung gateway, di semua antarmuka
jaringan VM.
Waktu tunggu koneksi tidak ada aktivitas yang kecil mungkin tidak berfungsi.
Pemetaan NAT diperiksa setiap 30 detik untuk mengetahui masa berlaku dan perubahan
konfigurasi. Meskipun nilai waktu tunggu koneksi 5 detik digunakan, koneksi mungkin tidak tersedia hingga 30 detik dalam kasus terburuk, dan 15 detik dalam kasus rata-rata.
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-08-19 UTC.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 UTC."],[],[],null,["# Quotas and limits\n=================\n\nThis document lists the quotas and system limits that apply to\nCloud NAT.\n\n- *Quotas* specify the amount of a countable, shared resource that you can use. Quotas are defined by Google Cloud services such as Cloud NAT.\n- *System limits* are fixed values that cannot be changed.\n\nA given quota or limit is calculated per resource. Quotas and limits may be\n*per project* , *per network* , *per region* , or per another resource. NAT IP\naddresses can't be shared between NAT gateways. To change a quota, see\n[requesting additional quota](#requesting-additional-quota).\n\nGoogle Cloud uses quotas to help ensure fairness and reduce\nspikes in resource use and availability. A quota restricts how much of a\nGoogle Cloud resource your Google Cloud project can use. Quotas\napply to a range of resource types, including hardware, software, and network\ncomponents. For example, quotas can restrict the number of API calls to a\nservice, the number of load balancers used concurrently by your project, or the\nnumber of projects that you can create. Quotas protect the community of\nGoogle Cloud users by preventing the overloading of services. Quotas also\nhelp you to manage your own Google Cloud resources.\n\nThe Cloud Quotas system does the following:\n\n- Monitors your consumption of Google Cloud products and services\n- Restricts your consumption of those resources\n- Provides a way to [request changes to the quota value](/docs/quotas/help/request_increase) and [automate quota adjustments](/docs/quotas/quota-adjuster)\n\nIn most cases, when you attempt to consume more of a resource than its quota\nallows, the system blocks access to the resource, and the task that\nyou're trying to perform fails.\n\nQuotas generally apply at the Google Cloud project\nlevel. Your use of a resource in one project doesn't affect\nyour available quota in another project. Within a Google Cloud project, quotas\nare shared across all applications and IP addresses.\n\n\nThere are also *system limits* on Cloud NAT resources.\nSystem limits can't be changed.\n\nQuotas\n------\n\nFor quotas that affect Cloud NAT, see the Cloud Router\n[quotas](/network-connectivity/docs/router/quotas) page.\n\nLimits\n------\n\nLimitations\n-----------\n\n- Some servers such as legacy DNS servers require UDP port randomization among\n 64,000 ports for enhanced security. Because Cloud NAT selects a random\n port from one of 64 or a user-configured number of ports, it is best to assign\n an external IP address to these servers instead of using Cloud NAT.\n Because Cloud NAT doesn't allow connections initiated from outside,\n most of these servers are required to use an external IP address anyway.\n\n- Cloud NAT isn't available for legacy networks.\n\n- Cloud NAT doesn't provide application-level gateway (ALG)\n capabilities---Cloud NAT doesn't update the IP address and port\n information in the packet data for application layer protocols such as\n FTP and SIP.\n\n- Cloud NAT gateways implement NAT connection tracking tables for each\n VM network interface on which it provides NAT services. Entries in each\n connection tracking table are 5-tuple hashes for the gateway's supported\n protocols.\n\n Entries in each connection tracking table persist for about as long as the\n relevant NAT timeout. For more information about NAT timeouts, see\n [NAT timeouts](/nat/docs/tune-nat-configuration#nat-timeouts).\n\n The maximum number of connection tracking table entries for all NAT\n connections associated with a VM is 65,535. This maximum covers connections,\n in aggregate, for all protocols that the gateway supports, across all network\n interfaces of the VM.\n- Small idle connection timeouts might not work.\n\n NAT mappings are checked every 30 seconds for expiration and configuration\n change. Even if a connection timeout value of 5 seconds is used, the\n connection may not be available for up to 30 seconds in the worst case, and\n 15 seconds in the average case.\n\nManage quotas\n-------------\n\nCloud NAT enforces quotas on resource usage for various reasons.\nFor example, quotas protect the community of Google Cloud users by\npreventing unforeseen spikes in usage. Quotas also help users who are exploring\nGoogle Cloud with the\n[free tier](/free/docs/gcp-free-tier)\nto stay within their trial.\n\nAll projects start with the same quotas, which you can change by\n[requesting additional quota](#requesting-additional-quota). Some quotas might increase\nautomatically based on your use of a product.\n\n### Permissions\n\nTo view quotas or request quota increases, Identity and Access Management (IAM) principals need one of the\nfollowing roles.\n\n### Check your quota\n\n### Console\n\n1. In the Google Cloud console, go to the **Quotas** page.\n\n [Go to Quotas](https://console.cloud.google.com/iam-admin/quotas)\n2. To search for the quota that you want to update, use the **Filter table**. If you don't know the name of the quota, use the links on this page instead.\n\n### gcloud\n\nUsing the Google Cloud CLI, run the following command to\ncheck your quotas. Replace \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e with your own project ID. \n\n```\n gcloud compute project-info describe --project PROJECT_ID\n```\n\nTo check your used quota in a region, run the following command: \n\n```\n gcloud compute regions describe example-region\n \n```\n\n### Errors when exceeding your quota\n\nIf you exceed a quota with a `gcloud` command,\n`gcloud` outputs a `quota exceeded` error\nmessage and returns with the exit code `1`.\n\nIf you exceed a quota with an API request, Google Cloud returns the\nfollowing HTTP status code: `413 Request Entity Too Large`.\n\n### Request additional quota\n\nTo adjust most quotas, use the Google Cloud console.\nFor more information, see\n[Request a quota adjustment](/docs/quotas/help/request_increase).\n\n### Resource availability\n\nEach quota represents a maximum number for a particular type of resource that you can create,\nif that resource is available. It's important to note that quotas *don't*\nguarantee resource availability. Even if you have available quota, you can't create\na new resource if it is not available.\n\nFor example, you might have sufficient quota to create a new regional, external IP address\nin a given region. However, that is not possible if there are no\navailable external IP addresses in that region. Zonal resource\navailability can also affect your ability to create a new resource.\n\nSituations where resources are unavailable in an entire region are rare. However, resources\nwithin a zone can be depleted from time to time, typically without impact to the service level\nagreement (SLA) for the type of resource. For more information, review the relevant SLA for the\nresource."]]
