瞭解 Google Cloud IAM Reviews

Santhosh P. · Reviewed about 2 months ago

Thoiba T. · Reviewed about 2 months ago

Sanjay A. · Reviewed about 2 months ago

Aravinda J. · Reviewed about 2 months ago

Keerthana R. · Reviewed about 2 months ago

Timouthee Z. · Reviewed about 2 months ago

Lucia C. · Reviewed about 2 months ago

Claudio V. · Reviewed about 2 months ago

Marshal S. · Reviewed about 2 months ago

Patryk J. · Reviewed about 2 months ago

Vinay A. · Reviewed about 2 months ago

Janaki N. · Reviewed about 2 months ago

Saran r. · Reviewed about 2 months ago

RUSHIKESH B. · Reviewed about 2 months ago

Mohanraj .. · Reviewed about 2 months ago

Sentamil S. · Reviewed about 2 months ago

SRITHARAN R U. · Reviewed about 2 months ago

Good

Dhinesh Kumar A. · Reviewed about 2 months ago

yogaselvan G. · Reviewed about 2 months ago

Madasani S. · Reviewed about 2 months ago

Flow K. · Reviewed about 2 months ago

Flavio L. · Reviewed about 2 months ago

Sonal J. · Reviewed about 2 months ago

Diana R. · Reviewed about 2 months ago

During the lab, I was unable to SSH into the VM instance "demoiam" — the connection kept failing with Permission denied (publickey) and exit code 255. Despite having the roles/owner role, OS Login (enable-oslogin=TRUE) was enabled on the instance, which requires additional roles (roles/compute.osAdminLogin and roles/iam.serviceAccountUser) that were not pre-configured for the student account. Even after manually adding those roles and registering my SSH key via gcloud compute os-login ssh-keys add, the OS Login NSS cache on the VM never picked up the changes. I had to disable OS Login (enable-oslogin=FALSE) on the instance metadata to fall back to traditional metadata-based SSH key authentication in order to connect and complete the lab. This seems like a misconfiguration in the lab setup.

Pablo L. · Reviewed about 2 months ago