Kontrol Layanan VPC adalah fitur yang memungkinkan Anda menyiapkan perimeter layanan dan membuat batas transfer data. Google Cloud Anda dapat menggunakan
Kontrol Layanan VPC dengan Eventarc untuk membantu melindungi layanan Anda.
Sebaiknya lindungi semua layanan saat membuat perimeter layanan.
Eventarc Advanced
Bus Eventarc Advanced di luar perimeter layanan tidak dapat menerima peristiwa dari project Google Cloud di dalam perimeter. Bus Eventarc Advanced di dalam perimeter tidak dapat merutekan peristiwa ke konsumen di luar perimeter.
Untuk memublikasikan ke bus Eventarc Advanced, sumber
peristiwa harus berada di dalam perimeter layanan yang sama dengan bus.
Untuk menggunakan pesan, konsumen peristiwa harus berada di dalam perimeter layanan yang sama dengan bus.
Anda dapat memverifikasi dukungan Kontrol Layanan VPC untuk resource Enrollment, GoogleApiSource, MessageBus, dan Pipeline dengan melihat log platform pada ingress.
Eventarc Standard
Dalam project yang dilindungi oleh perimeter layanan, Eventarc Standar
terikat oleh batasan yang sama dengan Pub/Sub:
Saat merutekan peristiwa ke tujuan Cloud Run, Anda hanya dapat
membuat langganan push Pub/Sub baru jika endpoint
push ditetapkan ke layanan Cloud Run dengan URL run.app
default. Domain kustom tidak berfungsi.
Saat merutekan peristiwa ke tujuan Workflows
yang endpoint push Pub/Sub-nya ditetapkan ke
eksekusi Workflows, Anda hanya dapat membuat
langganan push Pub/Sub baru melalui Eventarc.
Perhatikan bahwa akun layanan yang digunakan untuk autentikasi push untuk
endpoint Workflows harus disertakan dalam perimeter
layanan.
Kontrol Layanan VPC memblokir pembuatan pemicu Eventarc untuk
endpoint HTTP internal.
Perlindungan Kontrol Layanan VPC tidak berlaku saat merutekan peristiwa ke tujuan tersebut.
[[["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\u003eEventarc, in both its Advanced and Standard versions, can be used with VPC Service Controls to enhance service security by establishing a service perimeter and data transfer boundary.\u003c/p\u003e\n"],["\u003cp\u003eEventarc Advanced has limitations within service perimeters, preventing buses outside a perimeter from receiving events from inside and vice-versa, and event sources and consumers must be in the same perimeter as the bus.\u003c/p\u003e\n"],["\u003cp\u003eEventarc Advanced does not currently support the creation of pipelines inside of a service perimeter for full end-to-end event delivery.\u003c/p\u003e\n"],["\u003cp\u003eEventarc Standard shares limitations with Pub/Sub, such as only allowing new push subscriptions with default \u003ccode\u003erun.app\u003c/code\u003e URLs for Cloud Run destinations and only allowing creation of new push subscriptions through Eventarc when using Workflows destinations.\u003c/p\u003e\n"],["\u003cp\u003eVPC Service Controls will block the creation of triggers for internal http endpoints for Eventarc Standard.\u003c/p\u003e\n"]]],[],null,["# Set up a service perimeter using VPC Service Controls\n\n[Advanced](/eventarc/advanced/docs/overview) [Standard](/eventarc/standard/docs/overview)\n\nVPC Service Controls is a Google Cloud feature that lets you set up a\nservice perimeter and create a data transfer boundary. You can use\nVPC Service Controls with Eventarc to help protect your\nservices.\n| **Note:** Eventarc Standard handles event delivery using Pub/Sub topics and push subscriptions. To access the Pub/Sub API and manage event triggers, the Eventarc API must be protected within the same VPC Service Controls service perimeter as the Pub/Sub API.\n\nWe recommend that you protect all services when creating a service perimeter.\n\nEventarc Advanced\n-----------------\n\n- An Eventarc Advanced bus outside of a service perimeter can't\n receive events from Google Cloud projects inside the perimeter. An\n Eventarc Advanced bus inside of a perimeter can't route events to\n a consumer outside of the perimeter.\n\n - To publish to an Eventarc Advanced bus, the source of an event must be inside the same service perimeter as the bus.\n - To consume a message, an event consumer must be inside the same service perimeter as the bus.\n- You can verify VPC Service Controls support for the `Enrollment`,\n `GoogleApiSource`, `MessageBus`, and `Pipeline` resources by viewing platform\n logs on ingress.\n\nEventarc Standard\n-----------------\n\n- In projects protected by a service perimeter, Eventarc Standard\n is bound by the same limitations as Pub/Sub:\n\n - When routing events to Cloud Run destinations, you can only\n create new Pub/Sub push subscriptions when the push\n endpoints are set to Cloud Run services with default\n `run.app` URLs. [Custom domains](/run/docs/mapping-custom-domains) don't\n work.\n\n - When [routing events to Workflows destinations](/workflows/docs/trigger-workflow-eventarc)\n for which the Pub/Sub push endpoint is set to a\n Workflows execution, you can only create new\n Pub/Sub push subscriptions through Eventarc.\n Note that the service account used for push authentication for the\n Workflows endpoint must be included in the service\n perimeter.\n\n- VPC Service Controls blocks the creation of Eventarc\n triggers for\n [internal HTTP endpoints](/eventarc/standard/docs/vpc-endpoints/route-vpc-internal-endpoint-events).\n VPC Service Controls protection does not apply when routing events to\n such destinations.\n\nWhat's next\n-----------\n\n- To learn more about VPC Service Controls, see the\n [overview](/vpc-service-controls/docs/overview) and\n [supported products and limitations](/vpc-service-controls/docs/supported-products).\n\n- For best practices for enabling VPC Service Controls, see\n [Best practices for enabling VPC Service Controls](/vpc-service-controls/docs/enable).\n\n- For best practices for designing service perimeters, see\n [Design and architect service perimeters](/vpc-service-controls/docs/architect-perimeters).\n\n- To set up a service perimeter, see\n [Create a service perimeter](/vpc-service-controls/docs/create-service-perimeters)."]]
