- Newest
- Most votes
- Most comments
I ended up switching from AWS SSO on the primary accounts IAM (and using switch role) to configuring Identity Center and applying permission sets directly to the accounts, the user just uses the AWS access portal to switch to accounts they have permissions to. This works much better (and is less confusing) than switch role (policy/role) config.
answered 2 years ago
Hello.
Are there any differences between the IAM you are using and the IAM used by other members?
For example, are there different groups or policies to which they belong?
You may also find something by checking the CloudTrail event history for "us-east-1" and checking the details of the error.
https://docs.aws.amazon.com/awscloudtrail/latest/userguide/tutorial-event-history.html
All users are in the same IAM, the root account IAM, and it is SAML connected to AzureAD. I have two separate STS AssumeRole Policies for Admin and SystemAdmin roles on the sub account. My user and another persons user are in both groups that have the policies assigned to. The difference is, my SSO Role gives my account admin rights in the root account and the SSO role for the other user gives them no rights in the root account. I can switch to either role and the other user cannot switch to any role (in the sub account). I can add administrative permissions to the other users SSO role and then they can switch to either role.
I setup a event in cloudtrail (wasnt using it before) and I'll see what that shows.
Relevant content
- AWS OFFICIALUpdated 10 months ago

A proper trust relationship and permissions policy should facilitate this. sts:AssumeRole(WithSAML/WebIdentity) is the required action in the permission policy. Have you checked CloudTrail logs for more information on what is being blocked?