Explorer IAM (AWS) avis

Luis Ernesto G. · Examiné il y a 10 mois

Daniel G. · Examiné il y a 10 mois

Khemraj S. · Examiné il y a 10 mois

Andre Luiz P. · Examiné il y a 10 mois

Lazarus R. · Examiné il y a 10 mois

Andy A. · Examiné il y a 10 mois

Varun B. · Examiné il y a 10 mois

Adrian F. · Examiné il y a 10 mois

Emily R. · Examiné il y a 10 mois

Pradeep Kumar N. · Examiné il y a 10 mois

Santosh M. · Examiné il y a 10 mois

In the last lab changing the role did not allow the cp command to the bucket to complete. I also tried other more permissive roles and they did not work either.

Brian W. · Examiné il y a 10 mois

Navaneeth S. · Examiné il y a 10 mois

When I change de permission of service account to creator. Doesn't work to complete a upload file to bucket.

Thiago K. · Examiné il y a 10 mois

After changing `read-bucket-objects` to have Storage Object Creator, I still couldn't upload to the bucket

Nathan W. · Examiné il y a 10 mois

The lab did not mention anything about setting the access scope for the VM. The access scope defaulted to read only for Storage. I was never able to upload sample2.txt to the bucket even after changing the service account to allow writing. After reading the docs on access scope, it looks like both the service account and the access scope have to grant the proper permissions and the access scope was still read only. The lab should have specified an access scope at VM creation, or indicated the access scope needed to be changed when the service account was updated.

Ben L. · Examiné il y a 10 mois

Shripad K. · Examiné il y a 10 mois

Henry T. · Examiné il y a 10 mois

Nataliia R. · Examiné il y a 10 mois

Last step of writing the file back to Storage didn't work

Yugander R. · Examiné il y a 10 mois

Jonathan P. · Examiné il y a 10 mois

Aleksandar H. · Examiné il y a 10 mois

Len S. · Examiné il y a 10 mois

Tejus T. · Examiné il y a 10 mois

W. Jovonnie C. · Examiné il y a 10 mois