You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Try analyze like eksup analyze -c cluster-v2 -r eu-west-1
eksup version
latest
Operating system
Linux x86_64
Error output
eksup analyze -c cluster-v2 -r eu-west-1 -v
WARN aws_config::profile::parser::normalize: profile `sso-session SESSION_NAME` ignored because `sso-session SESSION_NAME` was not a valid identifier
at /cargo/registry/src/index.crates.io-6f17d22bba15001f/aws-config-1.1.3/src/profile/parser/normalize.rs:87
WARN aws_config::meta::credentials::chain: provider failed to provide credentials, provider: Profile, error: the credentials provider was not properly configured: ProfileFile provider could not be built: profile `PROFILE_NAME` was not defined: `sso_region` was missing (InvalidConfiguration(InvalidConfiguration { source: "ProfileFile provider could not be built: profile `PROFILE_NAME` was not defined: `sso_region` was missing" }))
at /cargo/registry/src/index.crates.io-6f17d22bba15001f/aws-config-1.1.3/src/meta/credentials/chain.rs:90
The text was updated successfully, but these errors were encountered:
Hi @Flydiverny, did you find temporary solution for this?
Nah, I mean you can always assume a role and use some short lived credentials or use the old legacy SSO profile format which is the workaround our team used for terraform until they supported the sso-session format.
Expected Behaviour
Supports SSO profiles using sso-session for authentication.
Current Behaviour
Credential chain fails
Code snippet
Possible Solution
Update aws-sdk-rust 😄
Steps to Reproduce
eksup analyze -c cluster-v2 -r eu-west-1
eksup version
latest
Operating system
Linux x86_64
Error output
The text was updated successfully, but these errors were encountered: