Exploring IAM (AWS) Reviews

Mubeen B. · Reviewed about 1 year ago

Bhaskar A. · Reviewed about 1 year ago

Ridho I. · Reviewed about 1 year ago

Luis Ernesto G. · Reviewed about 1 year ago

Daniel G. · Reviewed about 1 year ago

Khemraj S. · Reviewed about 1 year ago

Andre Luiz P. · Reviewed about 1 year ago

Lazarus R. · Reviewed about 1 year ago

Andy A. · Reviewed about 1 year ago

Varun B. · Reviewed about 1 year ago

Adrian F. · Reviewed about 1 year ago

Emily R. · Reviewed about 1 year ago

Pradeep Kumar N. · Reviewed about 1 year ago

Santosh M. · Reviewed about 1 year ago

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. · Reviewed about 1 year ago

Navaneeth S. · Reviewed about 1 year ago

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

Thiago K. · Reviewed about 1 year ago

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

Nathan W. · Reviewed about 1 year ago

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. · Reviewed about 1 year ago

Shripad K. · Reviewed about 1 year ago

Henry T. · Reviewed about 1 year ago

Nataliia R. · Reviewed about 1 year ago

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

Yugander R. · Reviewed about 1 year ago

Jonathan P. · Reviewed about 1 year ago

Aleksandar H. · Reviewed about 1 year ago