1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Yes, it is possible (I've just tried it in a test account). Even though the ARN that you see as an SSO federated user ens in federated-user/role_name/user you would still use the ARN of the role used by SSO. Once you've added it in, on the Data Lake administrative is should show up as Type: SSO User.
arn:aws:iam::<account-id>:role/aws-reserved/sso.amazonaws.com/AWSReservedSSO_<permission-set-based-role-name>
beantwortet vor 3 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
wouldn't that still just be the role? I am looking to see if it is possible to have user level permissions.
Ah. I see, sorry I misunderstood the actual ask of the question. So in this situation what I would suggest as an approach would be to use the ARN of the role as the trusted principle, but then using SSO session attributes to restrict the IAM policy of the federated users. So for example, From the data lakes perspective, the role is a trusted principal, but the role only grants permissions to federated users who have a certain session attribute. (That could be a custom field, or a username depending on the level of fine grained control that you want)
You're effectively pushing the user level permissions into your IAM policy.