Como saber mais sobre o IAM (AWS) avaliações

Luis Ernesto G. · Revisado há 10 months

Daniel G. · Revisado há 10 months

Khemraj S. · Revisado há 10 months

Andre Luiz P. · Revisado há 10 months

Lazarus R. · Revisado há 10 months

Andy A. · Revisado há 10 months

Varun B. · Revisado há 10 months

Adrian F. · Revisado há 10 months

Emily R. · Revisado há 10 months

Pradeep Kumar N. · Revisado há 10 months

Santosh M. · Revisado há 10 months

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. · Revisado há 10 months

Navaneeth S. · Revisado há 10 months

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

Thiago K. · Revisado há 10 months

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

Nathan W. · Revisado há 10 months

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. · Revisado há 10 months

Shripad K. · Revisado há 10 months

Henry T. · Revisado há 10 months

Nataliia R. · Revisado há 10 months

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

Yugander R. · Revisado há 10 months

Jonathan P. · Revisado há 10 months

Aleksandar H. · Revisado há 10 months

Len S. · Revisado há 10 months

Tejus T. · Revisado há 10 months

W. Jovonnie C. · Revisado há 10 months