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