For Unified Access Gateway deployment to Google Cloud Platform, a Google Cloud project must be used and this project must be configured with VPC networks, the corresponding subnet networks, and firewall rules.
- Ensure that you are aware of the Google Cloud Platform concepts.
- Ensure that you have the necessary permissions to create or modify resources such as images, VPC network, subnet, firewall rules, and so on, in the Google Cloud project.
- Compute Engine API must be enabled.
- Use a Google Cloud project.
Option Action New project
- In the Google Cloud Console, navigate to the Project Selector page.
- Create a Google Cloud project.
Existing project If a project is already available and active, you can use the existing project.
- Create a Virtual Private Cloud (VPC) network for each NIC.
Each NIC on the Unified Access Gateway uses a unique VPC network and a subnet within that network.
If you choose not to create a VPC network, only a single NIC Unified Access Gateway can be deployed. The Unified Access Gateway appliance when deployed in the Compute Engine uses the default VPC network available in the Google Cloud Platform.For example, in the following image, two VPC networks,
uag-back-vpc, are created in the Google Cloud Console. These VPC networks have
uag-back-networkas subnets respectively. A Unified Access Gateway two NIC appliance can be deployed to use these two subnets for front-end Internet facing and a separate subnet network for back-end connections.
Note: You can also configure Unified Access Gateway with shared VPC networks. In such case, Unified Access Gateway instances deployed on the service project are attached to the shared VPC networks created and managed on the host project. Each network interface (NIC) on Unified Access Gateway can be configured independently to use either shared VPC network or local VPC network. For more information, see Configuring Shared VPC on Google Cloud documentation.
- Make a note of the subnet name created.
The subnet name within a VPC network is used in the .ini file while deploying Unified Access Gateway by using PowerShell.
- To allow TCP and UDP port access to Unified Access Gateway appliances in the Internet accessible VPC, create the required number of firewall entries.
Important: SSH remote access to Unified Access Gateway on TCP port 22 from the Internet must be carefully restricted on the firewall. If SSH access is needed, the firewall rule must allow this access from a specific source IP address only or from a jump box virtual machine in the cloud from which access can be controlled.For example, in the following Google Cloud Console image, a firewall rule named
uag-horizon-protocolsis created in the internet facing VPC network
uag-front-vpc. This firewall rule applies to all the instances connected to
uag-front-vpcnetwork and allows inbound TCP and UDP traffic on specified ports from the public internet.