I Controlli di servizio VPC sono una funzionalità che consente di configurare un perimetro di servizio e creare un limite di trasferimento dei dati. Google Cloud Puoi utilizzare
i Controlli di servizio VPC con Eventarc per proteggere i tuoi
servizi.
Ti consigliamo di proteggere tutti i servizi quando crei un perimetro di servizio.
Eventarc Advanced
Un bus Eventarc Advanced al di fuori di un perimetro di servizio non può
ricevere eventi da progetti Google Cloud all'interno del perimetro. Un bus Eventarc Advanced all'interno di un perimetro non può instradare gli eventi a un consumer al di fuori del perimetro.
Per pubblicare su un bus Eventarc Advanced, l'origine di un
evento deve trovarsi all'interno dello stesso perimetro di servizio del bus.
Per utilizzare un messaggio, un consumer di eventi deve trovarsi all'interno dello stesso perimetro di servizio del bus.
Puoi verificare il supporto dei Controlli di servizio VPC per le risorse Enrollment,
GoogleApiSource, MessageBus e Pipeline visualizzando i log della piattaforma
in entrata.
Eventarc Standard
Nei progetti protetti da un perimetro di servizio, Eventarc Standard
è soggetto alle stesse limitazioni di Pub/Sub:
Quando indirizzi gli eventi alle destinazioni Cloud Run, puoi creare nuove sottoscrizioni push Pub/Sub solo quando gli endpoint push sono impostati su servizi Cloud Run con URL run.app predefiniti. I domini personalizzati non funzionano.
Quando instradi gli eventi verso destinazioni Workflows
per le quali l'endpoint push Pub/Sub è impostato su un'esecuzione
di Workflows, puoi creare nuove sottoscrizioni push Pub/Sub solo tramite Eventarc.
Tieni presente che il account di servizio utilizzato per l'autenticazione push per l'endpoint Workflows deve essere incluso nel perimetro di servizio.
Controlli di servizio VPC blocca la creazione di trigger Eventarc per endpoint HTTP interni.
La protezione di Controlli di servizio VPC non si applica quando gli eventi vengono indirizzati a
queste destinazioni.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-04 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)."]]
