
Identity-Aware Proxy, or Cloud IAP, acts as a gatekeeper for your web applications and VMs. It ensures that only authorized users can reach your resources by verifying the identity of each user before granting access. That adds a layer of protection beyond network-level firewalls, because IAP focuses on who is making the request and whether that person is allowed to access the resource in question. You can enforce granular access control policies based on user identity, even for resources that have no public IP address. For the Professional Cloud Architect exam, IAP is the service to recognize when a design needs identity-based access to private resources, including SSH access to VMs without public IPs.
Take an application deployed on Cloud Run. Normally, a user sends a request directly to the service. With IAP set up to protect the Cloud Run service, IAP acts as a security checkpoint and intercepts the request before it reaches the service.
IAP checks whether the user is authenticated and authorized to access the service. A user who is not authenticated is redirected to verify their identity, using Google or Microsoft sign-in or industry standards such as OAuth 2.0 and JSON Web Tokens. If the user's identity checks out and they have the necessary permissions, IAP grants access and the request proceeds to the Cloud Run service. In this way IAP ensures that only authorized users reach your applications, even when those applications are not exposed to the public internet.
Cloud Run is not the only resource IAP can protect natively. It can also protect App Engine apps, HTTPS load balancers, and Compute Engine VMs.
IAP also plays a part in Chrome Enterprise access flows. There, a request is evaluated against signals such as the user's posture information, location, or network data, and checked against the policy required for the sensitivity level of the app or resource being reached. If the request meets that policy, the traffic passes through IAP and the user is connected to internal apps and databases. Users reach internal tools as easily as a public website, while the organization keeps granular control based on real-time security status.
IAP helps eliminate the need for public IP addresses on backend resources. Exposing a service to the internet typically means assigning it a public IP, which makes it directly reachable from anywhere and creates a potential entry point for attackers. With IAP acting as the gatekeeper, you can keep resources private while still providing controlled access.
With IAP in front of your services, you can also allow traffic selectively based on user identity and authorization rather than relying only on ports. That means you can close off common ports, such as those used for HTTPS, SSH, or other TCP services, which reduces the number of potential attack vectors. Port scanning becomes less effective because fewer ports are open, and brute-force attacks are easier to stop because access is controlled by user identity rather than by IP address. The overall effect is that your resources become less visible and less accessible to potential attackers.
In some environments, public IPs are restricted or prohibited for security reasons, which makes it challenging to connect directly to a VM. IAP can be enabled to allow secure SSH access to those instances without exposing them to the public internet. It works as a secure proxy, routing SSH connections through Google Cloud's infrastructure. Rather than allowing direct network access to the VM, IAP verifies the user's identity and permissions before forwarding the request.
The flow is straightforward. A user initiates an SSH request, and IAP intercepts it instead of letting it go directly to the VM. IAP verifies the user and forwards the request through a secure tunnel to the VM inside a private subnet. The VM remains inaccessible from the public internet, but the authorized user can still connect when needed.
To use IAP for SSH, a user or service account needs the IAM permission iap.tunnelInstances.accessViaIAP. Without this permission, the connection request is blocked, even if the user has SSH access to the VM itself.
The connection is established with gcloud, and the key part is the --tunnel-through-iap flag, which tells Google Cloud to route the SSH session through IAP rather than attempting a direct connection.
gcloud compute ssh INSTANCE_NAME --zone=ZONE --tunnel-through-iap
For the Professional Cloud Architect exam, it helps to place IAP next to network-level controls. Firewalls decide which traffic can reach a resource. IAP adds a check on who the user is and what they are authorized to do, so access can depend on identity rather than on an open port or a public IP. A requirement to give authorized users access to internal applications or VMs while keeping those resources off the public internet is the kind of requirement IAP is designed for.
Our Professional Cloud Architect course covers Identity-Aware Proxy alongside Cloud Firewall rules and connecting to Compute Engine VMs, with practice questions that drill these distinctions.