Aprender a usar o IAM avaliações
193391 avaliações
Santhosh P. · Revisado há about 2 months
Thoiba T. · Revisado há about 2 months
Sanjay A. · Revisado há about 2 months
Aravinda J. · Revisado há about 2 months
Keerthana R. · Revisado há about 2 months
Timouthee Z. · Revisado há about 2 months
Lucia C. · Revisado há about 2 months
Claudio V. · Revisado há about 2 months
Marshal S. · Revisado há about 2 months
Patryk J. · Revisado há about 2 months
Vinay A. · Revisado há about 2 months
Janaki N. · Revisado há about 2 months
Saran r. · Revisado há about 2 months
RUSHIKESH B. · Revisado há about 2 months
Mohanraj .. · Revisado há about 2 months
Sentamil S. · Revisado há about 2 months
SRITHARAN R U. · Revisado há about 2 months
Good
Dhinesh Kumar A. · Revisado há about 2 months
yogaselvan G. · Revisado há about 2 months
Madasani S. · Revisado há about 2 months
Flow K. · Revisado há about 2 months
Flavio L. · Revisado há about 2 months
Sonal J. · Revisado há about 2 months
Diana R. · Revisado há about 2 months
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. · Revisado há about 2 months
Não garantimos que as avaliações publicadas sejam de consumidores que compraram ou usaram os produtos. As avaliações não são verificadas pelo Google.