1 Answer
- Newest
- Most votes
- Most comments
1
Resolved the problem, the SSO arn was incorrect. Not using the one of the correct organization
Relevant content
- asked 2 years ago
- asked 3 years ago
- AWS OFFICIALUpdated a month ago
Resolved the problem, the SSO arn was incorrect. Not using the one of the correct organization
In addition it needs to run in the same region as the region where the SSO was created