1 Answers
0
If you are using Active Directory as a choice of user directory and using Okta as an IdP, you don't need to leverage AWS SSO service. The example you referenced in that link is when you want to pull users from Okta Universal Directory or Azure AD. In your case, you have your users stored in AD. What you can do is follow the second option in the link of using AWS IAM to manage federated fine-grained access to AWS accounts. You can use Okta as an IdP to do an IdP-initiated SSO (SAML). When users sign into your AD through Okta, you can access AWS console by assuming an IAM role. This will not create persistent IAM users in AWS. There is a documentation from Okta to do the setup.
answered 20 days ago
Relevant questions
AWS SSO Access for Linux?
asked 6 months agoPolicy Condition for federated users
asked a month agoSSO passing Group via Assertion
asked 3 months agoAWS SSO + Azure AD, no way to access AWS Console?
Accepted Answerasked 7 months agoAWS Client VPN unable to set Authorization Route with Group ID using Okta
Accepted Answerasked 6 months agoAccess Control in Secrets Manager for Federated Users
asked 6 months agoAWS Service Catalog. Grant SSO Users to the Portfolio
asked 3 months agoAWS SFTP with Okta
asked a year agoAWS SSO ERROR 403 with AD connector
asked 2 months agoAWS Federated Identities
asked 21 days ago