Introduction to AWS Identity and Access Management (IAM) recensioni
54870 recensioni
James V. · Recensione inserita quasi 9 anni fa
Mohammed K. · Recensione inserita quasi 9 anni fa
I could see into the buckets in S3 when I was logged as awsstudent, even though the lab said I would not be able to do it. But I could not see anything while logged as userone or usertwo, so I understood how it works.
Ana Claudia M. · Recensione inserita quasi 9 anni fa
Senthilvel P. · Recensione inserita quasi 9 anni fa
KUNTAL C. · Recensione inserita quasi 9 anni fa
Bojana D. · Recensione inserita quasi 9 anni fa
sam c. · Recensione inserita quasi 9 anni fa
anuj t. · Recensione inserita quasi 9 anni fa
Nick H. · Recensione inserita quasi 9 anni fa
it's not very clear about userthree login username. it's very easy to use qls-1108403-2af3590da3af2399-userthree-49BUF65GT3MW to log in and web goes wrong.
jie z. · Recensione inserita quasi 9 anni fa
Panayiotis H. · Recensione inserita quasi 9 anni fa
partially satisfied
Sandeep Kumar G. · Recensione inserita quasi 9 anni fa
Lawrence Z. · Recensione inserita quasi 9 anni fa
partially satisfied
Sandeep Kumar G. · Recensione inserita quasi 9 anni fa
Sungsoo K. · Recensione inserita quasi 9 anni fa
Wenhong L. · Recensione inserita quasi 9 anni fa
Rick V. · Recensione inserita quasi 9 anni fa
ok
Arun R. · Recensione inserita quasi 9 anni fa
Amazon did not allow me to properly test users, I executed lab twice - copying URLS as instructed, but was not unsuccessful on both attempts
joseph b. · Recensione inserita circa 9 anni fa
Kathryn C. · Recensione inserita circa 9 anni fa
Hi, Your course for IAM ‘Introduction to AWS Identity And Acces Management’ seems to have a contradiction in what it’s policy is meant to do but doesn’t. User 2 is assigned to EC2Admin Group which is meant as described to ( ‘scale up our server farm as needed to respond to service needs’). In its policy details it has: "Action": "ec2:*", "Resource": "arn:aws:ec2:*:*:instance/*", "Effect": "Allow" }, { But when you login to ‘usertwo’ I’m unable to view the suppose existing instance that userone can view. I get on the EC2 Dashboard all the *Describe actions I’m not authorized to perform (enclosed pic). It’s confusing.. How am I to scale up if I’m unable to view what I already have? Also.. Isn’t scaling up meant to be able to launch new instances? I’m unable to do that either.. Seems like I should at least inherit views with the *Describe like the EC2Support group has. Could someone help me understand the relationship between what EC2Admin group can do more supposedly than EC2Support group? So far nothing…. I’m not able to distinguish (if that’s it’s purpose). Also.. The lab under ‘Test S3 Access’ states the account you’re already logged into (in my case a federated user) that I’m not suppose to be able reveal the contents from the 3 listed buckets…. However I can. When I login with ‘userthree’ account I only show 2 buckets. (Very confusing).
Osie D. · Recensione inserita circa 9 anni fa
Hi, Your course for IAM ‘Introduction to AWS Identity And Acces Management’ seems to have a contradiction in what it’s policy is meant to do but doesn’t. User 2 is assigned to EC2Admin Group which is meant as described to ( ‘scale up our server farm as needed to respond to service needs’). In its policy details it has: "Action": "ec2:*", "Resource": "arn:aws:ec2:*:*:instance/*", "Effect": "Allow" }, { But when you login to ‘usertwo’ I’m unable to view the suppose existing instance that userone can view. I get on the EC2 Dashboard all the *Describe actions I’m not authorized to perform (enclosed pic). It’s confusing.. How am I to scale up if I’m unable to view what I already have? Also.. Isn’t scaling up meant to be able to launch new instances? I’m unable to do that either.. Seems like I should at least inherit views with the *Describe like the EC2Support group has. Could someone help me understand the relationship between what EC2Admin group can do more supposedly than EC2Support group? So far nothing…. I’m not able to distinguish (if that’s it’s purpose). Also.. The lab under ‘Test S3 Access’ states the account you’re already logged into (in my case a federated user) that I’m not suppose to be able reveal the contents from the 3 listed buckets…. However I can. When I login with ‘userthree’ account I only show 2 buckets. (Very confusing).
Osie D. · Recensione inserita circa 9 anni fa
Hi, Your course for IAM ‘Introduction to AWS Identity And Acces Management’ seems to have a contradiction in what it’s policy is meant to do but doesn’t. User 2 is assigned to EC2Admin Group which is meant as described to ( ‘scale up our server farm as needed to respond to service needs’). In its policy details it has: "Action": "ec2:*", "Resource": "arn:aws:ec2:*:*:instance/*", "Effect": "Allow" }, { But when you login to ‘usertwo’ I’m unable to view the suppose existing instance that userone can view. I get on the EC2 Dashboard all the *Describe actions I’m not authorized to perform (enclosed pic). It’s confusing.. How am I to scale up if I’m unable to view what I already have? Also.. Isn’t scaling up meant to be able to launch new instances? I’m unable to do that either.. Seems like I should at least inherit views with the *Describe like the EC2Support group has. Could someone help me understand the relationship between what EC2Admin group can do more supposedly than EC2Support group? So far nothing…. I’m not able to distinguish (if that’s it’s purpose). Also.. The lab under ‘Test S3 Access’ states the account you’re already logged into (in my case a federated user) that I’m not suppose to be able reveal the contents from the 3 listed buckets…. However I can. When I login with ‘userthree’ account I only show 2 buckets. (Very confusing).
Osie D. · Recensione inserita circa 9 anni fa
didn't get to finish..dunno yet. sorry
Osie D. · Recensione inserita circa 9 anni fa
Non garantiamo che le recensioni pubblicate provengano da consumatori che hanno acquistato o utilizzato i prodotti. Le recensioni non sono verificate da Google.