How to Setup Okta as an Identity Provider in AWS IAM Identity Center 

5 seconds in and I have subscribed.

very detailed and easy to understand thank you so much John!

Excellent video. Very helpful.

Thanks bro! Super useful content

Maaan, you saved my day, honestly. Bless you God, bro.

Hey bro, just want to thank you. Save a lot of my time again.

Great video, it helped me a lot!

Yooooooooooo, I remember you from Sounds and Gear! It's dope to see you're an IT guy too. Thanks for the information, I'm transitioning to some cloud knowledge and your SC-900 video is helpful. Peace and Blessings.

Thanks, great video!!!

Great video. Explained well! 👑

good one.. learnt from this.. thanks for posting this..

@JKSTechLab I have a question about the prices for example if I have 1000 users in okta and I want to do a synchronization to take them to aws with "Assign Users to App" would have a high value or where I could see more of these prices of aws?

nice work

How do provide access to okta user after the integration?

Thank you for the great and simple explanation. Have a query here. If we are setting this up in an existing environment, is there any way by which we can import the SSO users (that have been manually in SSO ) into okta? Or do we need to remove them and assign the AWS sso app on their okta profile?

🔥🔥🔥

Great video! can i use aws cli to list those users/groups etc.. ? Thanks!

What if I want to connect multiple aws instances? Like prod, demo, and dev? Would this work by following the same instructions?

I had a question, post integration when I need to assign AWS service permissions/policies to the user, where can I do that?

When you enable IAM Identity Center integration, do the IAM local users still work?

excellent content. Where did u get the file okta.cert?

Folks, probably it will help you also, (but probably not). I got the same error as JK Swopes after full setup, looks like we are getting 400HTTP response from AWS. I spent a week with AWS support to break through, but without success. As the last hope, I updated this current identity provider with the same SAML XML and Okta certificate (just how I did before) and for some reason it got working. Don't forget to update provisioning token in Okta, the old one is getting deprecated after updating IdP.

I am facing the same error as you are at the end. any idea what could be causing it?

are you paying for the okta account or it is free trial for this video?

Is that really something on their end?? at 12:44 seconds, thats driving me nuts, and no useful help from support!

Subbed!