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

Alejandro L. · Revisado há about 1 year

Mubeen B. · Revisado há about 1 year

Bhaskar A. · Revisado há about 1 year

Ridho I. · Revisado há about 1 year

Luis Ernesto G. · Revisado há about 1 year

Daniel G. · Revisado há about 1 year

Khemraj S. · Revisado há about 1 year

Andre Luiz P. · Revisado há about 1 year

Lazarus R. · Revisado há about 1 year

Andy A. · Revisado há about 1 year

Varun B. · Revisado há about 1 year

Adrian F. · Revisado há about 1 year

Emily R. · Revisado há about 1 year

Pradeep Kumar N. · Revisado há about 1 year

Santosh M. · Revisado há about 1 year

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á about 1 year

Navaneeth S. · Revisado há about 1 year

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

Thiago K. · Revisado há about 1 year

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

Nathan W. · Revisado há about 1 year

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á about 1 year

Shripad K. · Revisado há about 1 year

Henry T. · Revisado há about 1 year

Nataliia R. · Revisado há about 1 year

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

Yugander R. · Revisado há about 1 year

Jonathan P. · Revisado há about 1 year