QuestionQ153

VerifiedPlanning and implementing a cloud solution

Every employee in your company has a Google account. Your operations team must manage a large number of Compute Engine instances, and each team member only needs administrative access to these servers. Your security team wants the credential deployment process to be operationally efficient, while also being able to determine who accessed any given instance. What should you do?

Explanation

OS Login is designed for exactly this use case: it lets each user register their own SSH public key on their personal Google account, and grants server access by assigning IAM roles (such as roles/compute.osAdminLogin for admin/sudo-level access) to a Google Group rather than distributing or copying keys to every instance individually. This scales efficiently to large fleets of instances since access is centrally managed through IAM/group membership and automatically updated or revoked when group membership changes, eliminating manual key deployment. Additionally, OS Login integrates with Cloud Audit Logs, recording login events tied to each user's Google identity, satisfying the requirement to determine who accessed a given instance — something plain metadata-based SSH keys (project-wide or per-instance) cannot reliably provide.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!