Study guide

6.3 OS Login and VM Manager for Fleet Configuration

Google Cloud Associate Cloud Engineer ACE

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Exam Overview

1.1 About the GCP Associate Cloud Engineer Exam 1.2 How to Use This Study Guide & Build a Study Plan

2 Chapter 2: Resource Hierarchy, IAM Basics & Cloud Identity

2.1 The GCP Resource Hierarchy: Organizations, Folders & Projects 2.2 Organization Policies & Granting IAM Roles 2.3 Cloud Identity: Managing Users and Groups

3 Chapter 3: APIs, Quotas & Billing Configuration

3.1 Enabling APIs and Provisioning Cloud Operations Suite 3.2 Assessing and Requesting Quota Increases 3.3 Billing Accounts, Project Linking & Billing Exports 3.4 Billing Budgets and Alerts

4 Chapter 4: Planning Compute & Storage Resources

4.1 Choosing the Right Compute Option: GCE vs. GKE vs. Cloud Run vs. Cloud Functions 4.2 Spot VMs, Custom Machine Types & Cost-Optimized Compute Planning 4.3 Choosing a Data Storage Product: Cloud SQL, BigQuery, Firestore, Spanner & Bigtable 4.4 Cloud Storage Classes & Persistent Disk Types

5 Chapter 5: Planning Network Resources

5.1 Load Balancing Options and Use Cases 5.2 Regional Resource Placement & High Availability Planning 5.3 Network Service Tiers: Premium vs. Standard

6 Chapter 6: Deploying Compute Engine Workloads

6.1 Launching Compute Engine Instances: Disks, SSH Keys & Availability Policies 6.2 Managed Instance Groups, Instance Templates & Autoscaling 6.3 OS Login and VM Manager for Fleet Configuration

7 Chapter 7: Deploying Google Kubernetes Engine Workloads

7.1 Installing and Configuring kubectl 7.2 Deploying GKE Clusters: Autopilot, Regional, Private & GKE Enterprise 7.3 Deploying Containerized Applications to GKE

8 Chapter 8: Deploying Serverless & Event-Driven Applications

8.1 Deploying Applications to Cloud Run and Cloud Functions 8.2 Event-Driven Architectures: Pub/Sub, Cloud Storage Triggers & Eventarc

9 Chapter 9: Deploying Data Solutions

9.1 Deploying Data Products: Cloud SQL, Firestore, Spanner, BigQuery & AlloyDB 9.2 Deploying Pub/Sub, Dataflow & Loading Data into Google Cloud

10 Chapter 10: Deploying Networking Resources & Infrastructure as Code

10.1 Creating VPCs, Subnets & Shared VPC 10.2 Firewall Rules, Cloud VPN & VPC Network Peering 10.3 Infrastructure as Code: Terraform, Config Connector, Cloud Foundation Toolkit & Helm

11 Chapter 11: Managing Compute Engine & GKE in Production

11.1 Connecting to and Managing Running Compute Engine Instances 11.2 Working with Snapshots and Custom Images 11.3 Managing GKE Clusters: Node Pools, Workloads & Artifact Registry Access 11.4 Horizontal and Vertical Pod Autoscaling in GKE

12 Chapter 12: Managing Cloud Run, Storage & Database Operations

12.1 Managing Cloud Run Revisions, Traffic Splitting & Scaling 12.2 Managing and Securing Cloud Storage Objects & Lifecycle Policies 12.3 Querying, Estimating Costs, Backup & Job Monitoring for Databases (Cloud SQL, BigQuery, Spanner, Dataflow)

13 Chapter 13: Networking Operations, Monitoring & Logging

13.1 Networking Operations: Subnets, Static IPs, Cloud DNS & Cloud NAT 13.2 Cloud Monitoring: Alerts, Custom Metrics & Dashboards 13.3 Cloud Logging: Buckets, Log Analytics, Routers & Filtering 13.4 Diagnostics, Ops Agent, Managed Service for Prometheus & Audit Logs

14 Chapter 14: IAM Policies & Role Types

14.1 IAM Policies: Structure, Bindings & Policy Hierarchy 14.2 IAM Role Types: Basic, Predefined & Custom Roles

15 Chapter 15: Service Accounts & Security Configuration

15.1 Creating Service Accounts & Assigning Least-Privilege Permissions 15.2 Assigning Service Accounts to Resources & Managing SA IAM Policies 15.3 Service Account Impersonation & Short-Lived Credentials

16 Chapter 16: Exam Readiness — Scenarios & Test-Day Strategy

16.1 Common ACE Exam Scenarios & Decision Frameworks 16.2 Test-Day Logistics, Time Management & Final Review Checklist

6.3 OS Login and VM Manager for Fleet Configuration

Key Takeaways Explain This Topic AI

OS Login ties SSH access to IAM identities via roles/compute.osLogin (standard) or roles/compute.osAdminLogin (sudo), replacing raw metadata keys

Instance-level enable-oslogin metadata overrides project-level metadata; constraints/compute.requireOsLogin enforces it org-wide with no opt-out

VM Manager has three distinct components: OS patch management (applies patches), OS inventory management (reports only, scans every ~10 minutes), and OS configuration management (enforces or dry-run-reports desired state)

OS configuration management (OS policies) supports dry-run mode for compliance-only reporting and an enforcement mode that actively corrects drift

VM Manager requires the Compute Engine and OS Config APIs plus a running guest environment and OS Config agent on each VM

Last updated: July 2026

Why This Topic Matters

The exam guide's remaining two Compute Engine deployment bullets -- "Configuring OS Login" and "Configuring VM Manager" -- are compact but frequently tested because they sit at the intersection of deployment and day-two operations: once you have launched instances and grouped them into MIGs, how do you securely access them and keep their operating systems patched and compliant at fleet scale?

OS Login: IAM-Tied SSH Access

OS Login replaces per-instance or per-project metadata SSH keys with SSH access controlled directly through Cloud Identity and Access Management (IAM) . Instead of managing raw public keys, you grant a user or group one of two IAM roles:

  • Role Access Level
  • roles/compute.osLogin Standard (non-administrator) SSH access
  • roles/compute.osAdminLogin SSH access with sudo/administrator privileges

roles/compute.osLoginExternalUser Grants OS Login access to identities outside the organization (external users)

You enable OS Login by setting the enable-oslogin metadata key to TRUE at the project level (applies to every instance) or at the instance level (applies to just that VM). Metadata precedence works the same way it does for SSH keys generally: instance-level metadata overrides project-level metadata . This means a project can enforce OS Login broadly while a specific instance sets enable-oslogin=FALSE to opt back out to legacy metadata keys -- or vice versa, enabling it on one sensitive instance in an otherwise unmanaged project.

To make OS Login mandatory across an entire organization or folder (so no project can opt out), administrators use the organization policy constraint constraints/compute.requireOsLogin . This is the exam's usual answer whenever a scenario says "enforce fleet-wide, centrally, with no per-project exceptions."

Two additional details worth knowing:

POSIX accounts : OS Login derives Linux POSIX user/group IDs from the caller's Cloud Identity profile by default, but you can set custom POSIX UIDs/GIDs to keep them consistent across many VMs (important for shared file permissions).

Auditability : because access maps to IAM identities, every login is tied to a real principal and can be centrally revoked by removing the IAM binding -- the reason OS Login, not metadata keys, is the enterprise-recommended default.

VM Manager: Fleet-Wide OS Operations

VM Manager is a suite of tools for managing the operating systems running across a fleet of Compute Engine VMs without connecting to each one individually. It has three components, and distinguishing what each one actually does is a common exam trap because their names sound similar:

Component What It Does Key Detail

OS patch management Applies OS patches to VMs Patch jobs can run on demand, be scheduled once, or run on a recurring schedule; instance filters target VMs by zone, label, group, or all instances; a patch compliance dashboard shows fleet-wide status

OS inventory management Reports on installed software and OS state -- does not change anything The OS Config agent runs an inventory scan roughly every 10 minutes and reports installed packages, available updates, and known vulnerabilities to the metadata server, the OS Config API, and log/BigQuery exports

OS configuration management (OS policies) Enforces a declarative desired configuration state Policies can run in dry-run (compliance reporting only, no changes applied) or enforcement mode, and can exclude or include VMs by label (for example, excluding GKE nodes from a policy meant only for standalone VMs)

The trap to watch for: inventory management only reports -- it never applies a fix. If a scenario says "list which packages are outdated across my fleet" without asking for a fix, the answer is inventory management. If it says "keep my fleet patched to the latest security updates automatically every month," the answer is patch management. If it says "make sure every VM has a specific config file or package installed, and I want a compliance report if any drift," the answer is OS configuration management (OS policies).

Prerequisites

VM Manager requires the Compute Engine API and OS Config API to be enabled on the project, and each VM must be running the guest environment plus the OS Config agent -- pre-installed on most Google-provided public images, but something you must install manually on custom or third-party images. IAM roles such as roles/osconfig.patchDeploymentAdmin and roles/osconfig.inventoryDisplayViewer control who can create patch jobs or view inventory data.

Worked Scenario

A platform team manages 500 Compute Engine VMs labeled by environment ( env=prod , env=staging ) and needs three things: (1) monthly security patches applied automatically to production without manual intervention, (2) a live inventory of installed packages for a security audit, and (3) confirmation that a required monitoring agent is present on every VM with no unauthorized removal. The solution: a recurring patch job filtered to env=prod , scheduled monthly, checked against the patch compliance dashboard ; OS inventory management enabled fleet-wide so the security team can query installed packages and known CVEs; and an OS configuration management policy in enforcement mode that reinstalls the monitoring agent if it is ever found missing, reported through the compliance UI. All SSH access to any of these 500 VMs for manual troubleshooting is controlled through OS Login with roles/compute.osAdminLogin granted only to on-call engineers -- auditable and centrally revocable the moment someone rotates off the on-call rotation.