InformationCompute instances should not be configured to have external IP addresses.
To reduce your attack surface, Compute instances should not have public IP addresses. Instead, instances should be configured behind load balancers, to minimize the instance's exposure to the internet.
Removing the external IP address from your Compute instance may cause some applications to stop working.
Go to the VM instances page by visiting: https://console.cloud.google.com/compute/instances.
Click on the instance name to go the the Instance detail page.
For each Network interface, ensure that External IP is set to None.
Click Done and then click Save.
From Command Line:
Describe the instance properties:
gcloud compute instances describe <INSTANCE_NAME> --zone=<ZONE>
Identify the access config name that contains the external IP address. This access config appears in the following format:
- kind: compute#accessConfig
name: External NAT
Delete the access config.
gcloud compute instances delete-access-config <INSTANCE_NAME> --zone=<ZONE> --access-config-name <ACCESS_CONFIG_NAME>
In the above example, the ACCESS_CONFIG_NAME is External NAT. The name of your access config might be different.
You can configure the Define allowed external IPs for VM instances Organization Policy to prevent VMs from being configured with public IP addresses. Learn more at: https://console.cloud.google.com/orgpolicies/compute-vmExternalIpAccess
By default, Compute instances have a public IP address.