Eric Villa

Thank you for the idea @bertini-besharp, it is very interesting! Have you already manage it without Leapp?

Hi @nick-doyle-slalom, thanks for your feedback! Is the setup you are referring to a SAML federated access to AWS from Azure AD? If so, I can confirm it works at...

Hi @egauk! I confirm what @pethron said. Basically, to avoid AWS throttling requests to AWS Identity Center APIs, we implemented a queue system that, as far as now, forces a...

Hi @egauk! With the new [v0.15.0](https://github.com/Noovolari/leapp/releases/tag/v0.15.0) release we've refactored sessions list introducing recycle of views; CPU usage and memory footprint were dramatically reduced. I'll close this issue as soon as...

Hi @deiga, I'm pretty sure your issue is related to what the [get-session-token documentation](https://docs.aws.amazon.com/cli/latest/reference/sts/get-session-token.html) says: > The temporary security credentials created by GetSessionToken can be used to make API calls...

Hi @jcogilvie, looking at the [docs](https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html), `aws eks get-token` or `aws-iam-authenticator` rely on credentials provided by default AWS credential provider chain, unless you specify AWS_PROFILE env variable in kubeconfig file....

I'm not sure, but I think that - as far as know - it should still work by manually setting the AWS_PROFILE (in the kubeconfig file) to the one associated...

Well, we solved [#108](https://github.com/Noovolari/leapp/issues/108) which is a bit different issue; the linked issue was related to the validity of the AWS SSO access token, not the AWS SSO Integration logout...

Thanks @bboure for the enhancement proposal! I think we can extract account info as described in the following link: https://docs.aws.amazon.com/cli/latest/reference/sts/get-access-key-info.html As @pethron said, this logic is easily replicable in leapp-daemon.

Hi @peteawood, thank you for your feedback! You're right, at the moment this feature is available but not usable, since we encountered a technical issue from the AWS SDK side...