
hug0k (hug0k) asked a question.
Currently we are using 3rd party gimme-credentials for awscli where all our AWS accounts are configured in OKTA. awscli released V2 which now supports SSO. so it would be nice if we have any work around for using them for okta too.
Here are few github links - https://github.com/aws/aws-cli/issues/5060
https://github.com/aws/aws-cli/issues/4647
https://docs.aws.amazon.com/singlesignon/latest/userguide/manage-your-identity-source-idp.html
I am happy to discuss more about it. Please let me know if need more details.

Can I get any response for this?
Wasn't this shown at Oktane?
I am not sure about that , can I know if you got any blogs about addressing this in oktane
https://support.okta.com/help/s/article/Integrating-the-Amazon-Web-Services-Command-Line-Interface-Using-Okta
i still see gimme is preferred one but after that post aws released aws V2 which supports aws sso , so like to know if anything is going to implement from okta side to cover this
I wish I could upvote this more than once. The community tools are fine for some but I'd prefer to have something officially supported before rolling it out to more widely. For now it's easier just to create IAM users for CLI access and use SSO for GUI.
I've since implemented the native integration James referenced below and it's a massive improvement. Highly recommend it.
We launched an updated integration, which adds support for the native AWS CLI via AWS SSO. Addressed in the blog post here:
https://www.okta.com/blog/2020/05/how-okta-aws-sso-simplifies-admin-and-adds-cli-support/