Network issues with VA deployment on GCP

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hi, I will like to check with with those who have experience deploying VA on Google Cloud Platform (GCP).

By default the nameserver when deployed in GCP is configured to 169.254.169.254.
We have configured to include our own DNS via the static.network file. However, we lost putty connection to the VA immediately after.

VA is active and source test connection is also successful when checked in ISC tenant.
Do we need to maintain 169.254.169.254 in the static.network file as well? I read somewhere that this is required for Google internal DNS purposes.

2

So for GCP you do not configure the DHCP or static IP. As this is setup in the mAchine deployment by the GCP admin.

There is also a specific GCP Va image.

3

Yes we did that by deploying the VA image directly. However all our test connections and aggregations are failing even though there is no restrictions for outbound on the firewall.

Only after fixing a DNS server on the static network file, we are able connect to target saas applications without issues. But that resulted in lost of connection to the internal systems.

4

@ipobeidi can you advise on how we can add additional DNS servers without configuring the static.network?

5

@yuyanglee try to configure secure tunnel if the standard method fails to connect to the systems

6

its on the Machine GCP configuration

7

The internal DNS is required to reach out to internal systems like IQ Server for AD.

8

Unfortunately we are not able to set the DNS on GCP console as the VM is in a shared VPC. Client doesn’t wants to expose that to other apps.