[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-08-18 (世界標準時間)。"],[[["\u003cp\u003eVPC Service Controls can be used with Eventarc to establish a service perimeter and data transfer boundary, thereby protecting your services.\u003c/p\u003e\n"],["\u003cp\u003eEventarc Advanced has limitations within a service perimeter, including the inability for external Eventarc Advanced buses to communicate with projects inside the perimeter and no support for end-to-end event delivery within it.\u003c/p\u003e\n"],["\u003cp\u003eEventarc Standard is subject to the same constraints as Pub/Sub, particularly concerning push subscriptions to Cloud Run services with default \u003ccode\u003erun.app\u003c/code\u003e URLs and Workflows destinations.\u003c/p\u003e\n"],["\u003cp\u003eVPC Service Controls prevents the creation of Eventarc triggers for internal HTTP endpoints, and protection does not apply to events routed to these destinations.\u003c/p\u003e\n"],["\u003cp\u003eProtecting all services is recommended when creating a new service perimeter, to maintain security.\u003c/p\u003e\n"]]],[],null,[]]