[[["わかりやすい","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-04-22 UTC。"],[],[],null,["# VPC Service Controls with VMware Engine\n=======================================\n\nTo further protect your Google Cloud VMware Engine resources, you can protect them\nusing [VPC Service Controls](/vpc-service-controls/docs/overview).\n\nVPC Service Controls lets you define a security perimeter for your VMware Engine\nresources. The service perimeter limits exporting and importing of resources and\ntheir associated data to within the defined perimeter. Google recommends\ncreating your service perimeter and adding VMware Engine to the Restricted\nServices before creating your first Private Cloud.\n\nWhen you create a service perimeter, you select one or more projects to be\nprotected by the perimeter. Requests between projects within the same perimeter\nremain unaffected. All existing APIs continue to function as long as the\nresources involved are within the same service perimeter. Note the IAM\nroles and policies still apply within a service perimeter.\n\nWhen a service is protected by a perimeter, requests cannot be made by the\nservice *inside* the perimeter to any resource *outside* the perimeter. This\nincludes exporting resources from inside to outside the perimeter. For more\ninformation, see [Overview](/vpc-service-controls/docs/overview) in the\nVPC Service Controls documentation.\n\nIn order to ensure VPC Service Controls works for VMware Engine, you\nmust add the VMware Engine service to the Restricted Services within\nVPC Service Controls.\n\nLimitations\n-----------\n\n- When adding existing VMware Engine, Private Clouds, Network Policies, and VPC Peering to a VPC Service Perimeter, Google does not check previously created resources to see if they still comply with the perimeter's policies.\n\nExpected behaviors\n------------------\n\n- Creating VPC Peering to a VPC outside of the perimeter will be blocked.\n- Use of VMware Engine workload internet access service will be blocked.\n- Use of External IP address service will be blocked.\n- Only the restricted Google APIs IPs will be available - `199.36.153.4/30`.\n\nAdd VMware Engine to allowed VPC Service Controls\n-------------------------------------------------\n\nTo add the VMware Engine service to the allowed VPC Service Controls, you can\nfollow these steps in the [Google Cloud console](https://console.cloud.google.com/):\n\n1. Go to the [VPC Service Controls](/console/security/service-perimeter) page.\n2. Click the name of the perimeter that you want to modify.\n3. On the **Edit VPC Service Perimeter page** , click the **Restricted Services** tab.\n4. Click **Add Services**.\n5. In the **Specify services to restrict** section, check the field for VMware Engine. If not already selected, check the fields for **Compute Engine API** and **Cloud DNS API**.\n6. Click **Add Services**.\n7. Click **Save**.\n\nWhat's next\n-----------\n\n- Learn more about [VPC Service Controls](/vpc-service-controls/docs/overview).\n- Learn about services supported by [restricted virtual IPs](/vpc-service-controls/docs/restricted-vip-services).\n- Read more about [service perimeter configuration steps](/vpc-service-controls/docs/service-perimeters#stages)."]]
