Introduction to AWS Identity and Access Management (IAM) (日本語版) のレビュー

Vincent James · 約9年前にレビュー済み

Khan Mohammed · 約9年前にレビュー済み

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.

Mancusi Valeije Ana Claudia · 約9年前にレビュー済み

Palraj Senthilvel · 約9年前にレビュー済み

CHOKSI KUNTAL · 約9年前にレビュー済み

Drndarevic Bojana · 約9年前にレビュー済み

chen sam · 約9年前にレビュー済み

tyagi anuj · 約9年前にレビュー済み

Hollingshead Nick · 約9年前にレビュー済み

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.

zhang jie · 約9年前にレビュー済み

Hiripis Panayiotis · 約9年前にレビュー済み

partially satisfied

Gundu Sandeep Kumar · 約9年前にレビュー済み

Zammit Lawrence · 約9年前にレビュー済み

partially satisfied

Gundu Sandeep Kumar · 約9年前にレビュー済み

Khim Sungsoo · 約9年前にレビュー済み

Liu Wenhong · 約9年前にレビュー済み

Valdez Rick · 約9年前にレビュー済み

ok

Reddy Arun · 約9年前にレビュー済み

Amazon did not allow me to properly test users, I executed lab twice - copying URLS as instructed, but was not unsuccessful on both attempts

bourne joseph · 約9年前にレビュー済み

Connolly Kathryn · 約9年前にレビュー済み

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).

DeGoldsby Osie · 約9年前にレビュー済み

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).

DeGoldsby Osie · 約9年前にレビュー済み

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).

DeGoldsby Osie · 約9年前にレビュー済み

didn't get to finish..dunno yet. sorry

DeGoldsby Osie · 約9年前にレビュー済み