AWS SSO is badly broken in SOPS

[devonjones]

I'm using the aws client 2 for logging into aws sso. The config that aws sso uses where you declare an sso-session isn't respected, but further, even if you move the keys like sso_region and sso_start_url into the config for a specific profile, it then breaks on the cache.

[kruczjak]

Seems like sso-session is supported in aws-sdk-go-v2 aws/aws-sdk-go-v2#1903

Sops uses old "v1" version.

Probably migration to v2 would solve this problem, see also #1194 and #614

[kruczjak]

There is also draft PR with upgrade: #1179

[dzavalkin-scayle]

@hiddeco Please add this issue to 3.8.0 milestone, since migration to AWS SDK v2 is done. Currently version of SOPS is not usable if one uses AWS SSO and has AWS CLI config set up per current AWS documentation...

[hiddeco]

The milestone tracks pull requests, and not issues. #1065 is on the list however.

[dzavalkin-scayle]

Thanks! I found a workaround to get sops working via converting AWS CLI config to legacy format (i.e. without named SSO session but with sso_start_url and sso_account_id keys in each AWS CLI profile).

[hiddeco]

This should have been addressed in https://github.com/getsops/sops/releases/tag/v3.8.0-rc.1. I would like to invite anyone to try this out, potential issues can be discussed in #1270.

[devonjones]

confirmed, thanks!

[muhamedkapoevolt]

I had same issue, update resolved that. Thanks!!!