Stay organized with collections
Save and categorize content based on your preferences.
Linux
This document provides an overview of the methods that you can use to connect to
a Compute Engine virtual machine (VM) instance through its internal IP
address. Connecting to a VM using its internal IP address is useful if you
isolate VMs from external networks by removing their external IP addresses or
restricting inbound traffic to their external IP addresses.
You don't want any external IP address access to any VMs in your
project. You can use IAP on all Linux VMs, including
bastion host VMs and VMs within projects that use Cloud VPN or
Cloud Interconnect.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["This document outlines how to connect to Compute Engine virtual machines (VMs) using their internal IP addresses, particularly useful when VMs are isolated from external networks."],["Connecting via internal IP is an alternative to using an external IP address, for which separate instructions are available."],["SSH tunneling with Identity-Aware Proxy (IAP) is recommended when external IP access to VMs is restricted and is compatible with bastion hosts and VMs within projects using Cloud VPN or Cloud Interconnect."],["Bastion host VMs are an option for specific cases, such as session recording, where IAP is not suitable."],["Cloud VPN or Cloud Interconnect can be used for SSH access if they are already set up within the organization, noting these are separate products from Compute Engine."]]],[]]