If you don't need to run discovery or visibility on a GCP system anymore, you can purge it to remove the files, data, and other resources that CDV uses to run visibility. When purging a GCP visibility system, you can use the virtual machine's (VM's) credentials (if CDV is deployed on a virtual machine), or specify credentials for CDV using a Service account file.
For more information on how purging works and how to purge a visibility system, see Purging visibility systems. The settings below apply only when purging a GCP visibility system.
Basic AWS parameters options
| Field/Option | Description |
|---|---|
| Use VM instance credentials |
(Usable only if CDV is deployed on a virtual machine (VM).) If ticked, CDV will use the VM's credentials when purging the visibility system. When you open the Purge visibility system (GCP) window, you'll see the message "Detecting VM instance deployment". This means CDV is trying to detect whether CDV is running on a VM instance. If CDV successfully detects that it is running on a VM on GCP, you can select the Use VM instance credentials checkbox that appears. CDV will now authenticate itself using the VM's credentials. |
| Service account file |
If CDV is not deployed on a VM (or you prefer to use a separate service account), on the Setup page, under GCP Service Account, drag your GCP service account key file (a JSON file) to the Service Account File area. (You can also click the upload icon and manually browse to the file.) After successfully uploading GCP service account keys, CDV will validate the service account keys with Google Cloud Platform. |