Unable to create IAM user in AWS labs

Cloud AWS
#22

Hi Rob/team ,

Still waiting for an update .

#23

A bit of patience… I’ve gotten a partial response, but I’ll fill you once they’ve had the opportunity to actually implement a piece of what was discussed. That will be around the middle of next week, I would expect.

#24

Sure Rob .

Will be looking for your response .

#25

Hi Rob ,

Please let me know if you know if you got any update .

#26

Hi Rob ,

is there any update for the request ?

#27

The major news is that since a number of people have asked for OIDC provider support, we’ve added these to the playground. I’m not sure exactly how to use the feature, but try it out, and if it’s unclear how to do it, I’ll get more information from the engineer.

Beyond that, here are some answers to what you asked:

Issue 1 As you’ve already mentioned in the thread, IAM Users to start with the naming patter iamuser*
→ Policies attached to also follow a similar naming convention, iampolicy*
Again the kind of policies would typically be Read-Only Access Policies

Issue 3 Combined -
Registering CSI Drivers,
Attaching IAM Roles to SAs (IRSA),
Creating other users within EKS
These have broad applications, and these permissions might not be provided to the user for security reasons

Issue 4 Specifically, it appears that the user would like another user created, and attach permissions to test out varied use-cases, something we wouldn’t typically be in favour of.

#28

Ok if it can solve my problem then i’m happy to use OIDC as well . Please let me know how to use .

#29

The engineer just went out on vacation, so I can’t ask her just yet. But see if this document helps you out enough to get started.