The Compute Engine PowerShell deployment script for Unified Access Gateway reads all configuration settings from a .ini configuration file. This section describes the .ini file format and shows examples of the settings that can be used for the deployment.
Most sections of the .ini file are identical to the standard .ini settings for Unified Access Gateway as supported for all the other hypervisor deployments.
For more information about the .ini file, see the Using PowerShell to Deploy the Unified Access Gateway Appliance section in the Deploying and Configuring VMware Unified Access Gateway documentation at VMware Docs.
- In the .ini file, add a new group, [GoogleCloud] and the necessary settings specific to Google Cloud Platform.
Note: For Google Cloud Platform deployments, the following settings in the General section are not used:
- All IPv4 settings
- All IPv6 settings
The following table lists the settings (Value Name) that are required for the Google Cloud Platform deployment. The table also includes examples and indicates which of these settings are mandatory and optional.
||The Google Cloud Platform project ID used for creating a new Unified Access Gateway instance.
If the project ID is not provided, the project from active configuration in the Cloud SDK is used.
||Name of the imported appliance image in the Compute Engine from which a new instance must be created.||Mandatory|
||Indicates the Compute Engine machine type.
Default value of machineType is
Note: Ensure that the machineType specified is appropriate for the number of Unified Access Gateway NICs required.
||Compute Engine zone where new a Unified Access Gateway instance is created.
If the zone value is not provided, the zone from active configuration in the Cloud SDK is used.
||Subnet on which eth0, eth1, and eth2 NICs of the Unified Access Gateway must be created.
Following are the values of the deploymentOption and the corresponding subnets used:
If a subnet value is not provided, then the PowerShell script uses the default value for the subnet. In a two NIC or three NIC deployment, only a single subnet can use the default value.
|In a two NIC or three NIC deployment, only one of the subnet values can be optional.|
||Internal IP address for the NIC
This setting can be used to attach eth0, eth1, and eth2 of the Unified Access Gateway with static internal IP addresses from Google Cloud's VPC network.
If the value of privateIPAddress is not provided, Compute Engine attaches the corresponding NIC with a dynamic internal IP address.
For example: consider a two NIC deployment
|External IP address for the NIC
This setting can be used to attach eth0, eth1, and eth2 of the Unified Access Gateway with reserved external IP addresses from Google Cloud's VPC network.
If the value of publicIPAddress is not provided, Compute Engine attaches the corresponding NIC with a dynamic external IP address.
To prevent a NIC from attaching with an external IP address, use
In the example, consider a three NIC deployment:
|labels||labels=label0=value0,label1=value1||Labels associated with a Unified Access Gateway instance.
|tags||tags=tag0,tag1||Tags associated with a Unified Access Gateway instance.
||A service account is an identity attached to the Unified Access Gateway instance.
The service account's access tokens can be accessed through the Unified Access Gateway instance metadata server and are used to authenticate applications on the instance. The account can be set using an email address corresponding to the required service account.
If the service account is not provided, the Unified Access Gateway instance uses the project's default service account.
Example 1: INI File Definition for deploying Unified Access Gateway to Google Cloud Platform
[General] name=uag1 deploymentOption=onenic sshEnabled=true [GoogleCloud] projectId=my-project imageName=euc-unified-access-gateway-21-03-0-0-42741891 zone=us-central1-a subnet0=uag-front-network [Horizon] proxyDestinationUrl=https://myhorizon.example.com
Example 2: INI File Definition for deploying Unified Access Gateway to Google Cloud Platform
[General] name=uag2 deploymentOption=twonic sshEnabled=true routes1=10.20.0.0/16 10.2.0.1 [GoogleCloud] projectId=my-project imageName=euc-unified-access-gateway-21-03-0-0-42741891 zone=us-central1-a subnet0=uag-front-network subnet1=uag-back-network [Horizon] proxyDestinationUrl=https://myhorizon.example.com