Google Cloud (GC) Deploy Tasks

Deploying to Google Cloud involves the following tasks:

Topics

Google Cloud Deployment Tasks
Post Deployment Tasks

Google Cloud Deployment Tasks

Task	Description	Related Topic(s)
Download the latest OVA	Download current version of the Access Gateway OVA.	Download the latest OVA image
Install CLI	Install and configure the Google Cloud CLI.	Install and Configure Google Cloud command line interface
Prepare	Minor preparations need to be done before uploading the Access Gateway OVA to Google Cloud.	Prepare Image for deployment to Google Public Cloud
Create Project	Projects are containers for related artifacts. Create a project to contain the Access Gateway OVA.	Create project, region and zone
Enable Privileges	Certain privileges are required for creating buckets and uploading images.	Enable Privileges
Create Bucket	Google Cloud Buckets are used for storing content such as OVA Images.	Create a bucket
Upload	Before a VM can be created the image its based on must be uploaded to a bucket.	Upload an OVA into a Google Cloud bucket
Create VM	The final step in importing to Google Cloud is to create a VM from an imported image.	Create a VM from image uploaded to a bucket

Post Deployment Tasks

All Access Gateway deployments require a set of common tasks:

Task	Description	Related Topics
First sign in	Reset the Access Gateway Management console password. Reset the virtual appliance at the command line.	First sign in to command line console Initialize Access Gateway command line
[Optional but recommended] Specify the hostname	Access Gateway defaults to a known gateway hostname which can be changed.	Set Access Gateway instance hostname
[Optional] Specify a fixed IP address	Many installations require Access Gateway to use a fixed known IP address.	Set Access Gateway instance IP address
[Optional] Specify DNS servers	Many installations use a split DNS process where multiple DNS servers are required.	Set Access Gateway DNS Servers
[Optional] Specify proxy	Some installations require a proxy server for Access Gateway	Set Access Gateway proxy server
Determine the IP Address assigned and configure DNS	Determine Access Gateway IP address. Configure required /etc/hosts admin entry. Configure required DNS entries.	Determine Access Gateway IP address for non-AWS instances. Configure admin /etc/hosts entry Configure Access Gateway DNS
Initialize Access Gateway	Initialize the cookie domain and instance hostname.	Initialize Access Gateway console
Configure an identity provider	Configure Okta tenant as an identify provider.	Configure your Okta tenant as an identity provider
Configure SAML access to Access Gateway from your Okta tenant	Configure Okta tenant to allow access to Access Gateway using SAML.	Add an Access Gateway Admin UI console application

Important

When creating a set of Access Gateway nodes for use in a high availability cluster, ensure that nodes are named appropriately.
Also, node names must be resolvable between Access Gateway instances before configuring high availability.