[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-22。"],[],[],null,["# Set up a service perimeter using VPC Service Controls\n\nVPC Service Controls is a Google Cloud feature that allows you to set\nup a service perimeter and create a data transfer boundary. You can use\nVPC Service Controls with Workflows to help protect your\nservices.\n\nHTTP requests from a Workflows execution are supported as\nfollows:\n\n- [Authenticated requests](/workflows/docs/authenticate-from-workflow#authenticate-apis) to VPC Service Controls-compliant Google Cloud endpoints are allowed.\n- Requests to Cloud Run functions and Cloud Run service endpoints are allowed.\n- Requests to third-party endpoints are blocked.\n- Requests to non-VPC Service Controls-compliant Google Cloud endpoints are blocked.\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 the recommended process to configure and enforce\n VPC Service Controls protection in your Google Cloud organization, 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).\n\n- To invoke a private endpoint, see\n [Invoke a private endpoint using Service Directory's service registry](/workflows/docs/invoke-private-endpoint-vpc)."]]