[[["易于理解","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-09-04。"],[],[],null,["# Additional considerations\n\nWhether you choose to deploy Secure Web Proxy using the explicit proxy mode\nor as a Private Service Connect service attachment, note the following\nadditional considerations.\n\nAllocate an internal IP address for Secure Web Proxy\n----------------------------------------------------\n\nSecure Web Proxy allocates only regional virtual IP addresses. These IP\naddresses are available only in the assigned region. Secure Web Proxy\ninstances are provisioned in a region within a Virtual Private Cloud (VPC)\nnetwork.\n\nAssign an internal IP address to the Secure Web Proxy instance in one of the\nfollowing ways:\n\n- Specify the address in the **Address** field while provisioning the Secure Web Proxy instance.\n- If no address is specified, Secure Web Proxy automatically allocates one IP address from the subnet you provide while provisioning.\n- If address and subnet are not specified, Secure Web Proxy automatically allocates an address from the default network within the chosen VPC network.\n\nConfigure identity-based policy enforcement for Secure Web Proxy\n----------------------------------------------------------------\n\nSecure Web Proxy uses cloud-native identity information for policy\nenforcement when virtual machine (VM) instances within the same VPC\ninitiate connections. When you configure Secure Web Proxy as a service\nattachment across VPC networks, the following\nidentity types are supported for policy enforcement:\n\n- **Service accounts**: Non-human accounts used for service access must be authenticated and authorized to connect to Secure Web Proxy.\n- **Secure tags** : These key-value pairs, scoped to specific VPC networks, can be attached to various entities like organizations, folders, or projects. Secure Web Proxy policies can use secure tags marked with the **GCE_FIREWALL** purpose, retrieving them using their permanent ID (for example, tagValues/567890123456).\n\nConfigure Cloud NAT for Secure Web Proxy\n----------------------------------------\n\nUse Cloud NAT configurations for Secure Web Proxy deployments.\n\n### Standard configuration\n\n- Secure Web Proxy infrastructure utilizes a pool of autoscaling proxies.\n- Each proxy uses one or more public IPv4 addresses obtained from Cloud NAT.\n- Cloud NAT automatically scales and assigns additional public IP addresses as the number of proxy instances serving Secure Web Proxy traffic changes.\n\nThis dynamic solution allows seamless traffic bursts without the need for\nmanual infrastructure adjustments.\n\n### Custom IP address allocation\n\nWhile auto scaling Cloud NAT is the standard, certain scenarios can require\nassigning a specific set of public IP addresses to Secure Web Proxy.\n\nIf specific IP addresses are shared with vendors for\nfirewall allow policies, assigning a custom range helps ensure continued access.\nYou can modify the provisioned Cloud NAT gateway and specify a range of\npublic IP addresses."]]
