Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Jika organisasi Anda menggunakan VPC Bersama, Anda dapat
menghubungkan layanan lingkungan standar App Engine langsung ke jaringan VPC Bersama
menggunakan Akses VPC Serverless.
Hal ini memungkinkan layanan lingkungan standar mengakses resource di
jaringan VPC Bersama Anda, seperti instance VM Compute Engine,
instance Memorystore, dan resource lain dengan alamat
IP internal.
Konektor Akses VPC Serverless dikenai biaya bulanan. Untuk mengetahui informasi selengkapnya, lihat harga
Akses VPC Serverless.
Untuk VPC Bersama, konektor Akses VPC Serverless dapat dikonfigurasi
dengan dua cara berbeda. Anda dapat menyiapkan konektor di setiap
project layanan yang memiliki resource lingkungan standar yang memerlukan akses
ke jaringan Anda, atau Anda dapat menyiapkan konektor bersama di project host. Setiap
metode memiliki kelebihan.
Project layanan
Manfaat membuat konektor di project layanan:
Isolasi: Setiap konektor memiliki bandwidth khusus dan tidak terpengaruh oleh
penggunaan bandwidth konektor pada project layanan lainnya. Ini bagus
jika Anda memiliki layanan yang mengalami lonjakan traffic, atau jika Anda perlu memastikan
bahwa setiap project layanan tidak terpengaruh oleh penggunaan konektor project
layanan lainnya.
Penagihan balik: Biaya yang ditimbulkan oleh konektor dikaitkan dengan
project layanan yang berisi konektor tersebut. Hal ini memungkinkan penagihan balik yang lebih mudah.
Keamanan: Memungkinkan Anda mengikuti "prinsip hak istimewa terendah".
Konektor harus diberi akses ke resource di jaringan VPC
Bersama yang perlu dijangkau. Dengan membuat konektor di project
layanan, Anda dapat membatasi apa saja yang dapat diakses oleh layanan dalam project
menggunakan aturan firewall.
Independensi tim: Mengurangi dependensi pada administrator project host.
Tim dapat membuat dan mengelola konektor yang terkait dengan project
layanan mereka. Pengguna dengan peran Security Admin Compute Engine atau
peran Identity and Access Management (IAM) khusus dengan izin
compute.firewalls.create
yang diaktifkan untuk project host tetap harus mengelola aturan firewall untuk
konektor.
Pengelolaan jaringan terpusat: Selaras dengan model VPC Bersama
pemusatan resource konfigurasi jaringan di project host.
Ruang alamat IP: Menghemat lebih banyak ruang alamat IP Anda. Konektor
memerlukan alamat IP untuk
setiap instance, sehingga memiliki lebih sedikit konektor (dan lebih sedikit instance di setiap
konektor) yang akan menggunakan lebih sedikit alamat IP. Ini bagus jika Anda khawatir
kehabisan alamat IP.
Pemeliharaan: Mengurangi pemeliharaan karena setiap konektor yang Anda buat dapat
digunakan oleh beberapa project layanan. Ini bagus jika Anda khawatir
tentang overhead pemeliharaan.
Biaya untuk waktu saat tidak ada aktivitas: Dapat mengurangi jumlah waktu saat tidak ada aktivitas konektor
dan biaya terkait. Konektor menimbulkan biaya meskipun tidak sedang menyajikan
traffic (lihat harga). Memiliki lebih sedikit
konektor dapat mengurangi jumlah resource yang Anda bayar saat tidak menyajikan
traffic, bergantung pada jenis konektor dan jumlah instance. Cara ini
sering kali hemat biaya jika kasus penggunaan Anda melibatkan banyak layanan, dan
layanan tersebut jarang digunakan.
[[["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-19 UTC."],[[["\u003cp\u003eApp Engine standard environment services can connect directly to a Shared VPC network using Serverless VPC Access, allowing access to resources like Compute Engine VMs and Memorystore instances with internal IP addresses.\u003c/p\u003e\n"],["\u003cp\u003eServerless VPC Access connectors are billable and can be configured either in individual service projects or centrally within the host project, each offering distinct benefits.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring connectors in service projects provides benefits like dedicated bandwidth, easier chargebacks, enhanced security, and team independence.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring connectors in the host project enables centralized network management, better IP address space preservation, reduced maintenance, and potential cost savings for idle time.\u003c/p\u003e\n"],["\u003cp\u003eThe choice of whether to create connectors in the host project or service project should be made depending on your needs such as the level of isolation between services, how big your network is and how often it is used.\u003c/p\u003e\n"]]],[],null,["# Connecting to a Shared VPC network\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nIf your organization uses [Shared VPC](/vpc/docs/shared-vpc), you can\nconnect App Engine standard environment services directly to your Shared VPC network\nby using [Serverless VPC Access](/vpc/docs/serverless-vpc-access).\nThis allows a standard environment service to access resources in your\nShared VPC network, such as Compute Engine VM instances,\nMemorystore instances, and any other resources with an internal IP\naddress.\n\nServerless VPC Access connectors incur a monthly charge. For more information, see Serverless VPC Access\n[pricing](/vpc/pricing#serverless-vpc-pricing).\n\nIf your organization does not use Shared VPC, see\n[Connect to a VPC network](/appengine/docs/standard/connecting-vpc).\n\nComparison of configuration methods\n-----------------------------------\n\nFor Shared VPC, Serverless VPC Access connectors can be\nconfigured in two different ways. You can either set up connectors in each\nservice project that has standard environment resources that need access\nto your network, or you can set up shared connectors in the host project. There\nare advantages to each method. \n\n### Service projects\n\nAdvantages of creating connectors in the service projects:\n\n- **Isolation:** Each connector has dedicated bandwidth and is unaffected by bandwidth use of connectors in other service projects. This is good if you have a service that experiences spikes in traffic, or if you need to ensure that each service project is unaffected by connector use of other service projects.\n- **Chargebacks:** Charges incurred by connectors are associated with the service project containing the connector. This enables easier chargebacks.\n- **Security:** Allows you to follow the \"principle of least privilege.\" Connectors must be granted access to the resources in your Shared VPC network that they need to reach. By creating a connector in the service project, you can limit what the services in the project can access by using firewall rules.\n- **Team independence:** Reduces dependency on the host project administrator. Teams can create and manage the connectors associated with their service project. A user with the Compute Engine [Security Admin](/compute/docs/access/iam#compute.securityAdmin) role or a custom [Identity and Access Management (IAM)](/iam) role with the [`compute.firewalls.create`](/compute/docs/reference/rest/v1/firewalls/insert#iam-permissions) permission enabled for the host project must still manage firewall rules for the connector.\n\nTo set up connectors in service projects, see\n[Configure connectors in service projects](/appengine/docs/standard/shared-vpc-service-projects).\n\n### Host project\n\nAdvantages of creating connectors in the host project:\n\n- **Centralized network management:** Aligns with the Shared VPC model of centralizing network configuration resources in the host project.\n- **IP address space:** Preserves more of your IP address space. Connectors require an IP address for each instance, so having fewer connectors (and fewer instances in each connector) uses fewer IP addresses. This is good if you are concerned about running out of IP addresses.\n- **Maintenance:** Reduces maintenance, because each connector you create may be used by multiple service projects. This is good if you are concerned about maintenance overhead.\n- **Cost for idle time:** Can reduce the amount of connector idle time and associated cost. Connectors incur costs even when they are not serving traffic (see [pricing](/vpc/pricing#serverless-vpc-pricing)). Having fewer connectors may reduce the amount of resource you pay for when not serving traffic, depending on your connector type and number of instances. This is often cost effective if your use case involves a large number of services, and the services are used infrequently.\n\nTo set up connectors in the host project, see\n[Configure connectors in the host project](/appengine/docs/standard/shared-vpc-host-project)."]]
