OK!
Unless you passed in --s3-profile
then opt.Profile
will be empty.
Can you try
- your patch with
Profile: ""
- this should pick upAWS_PROFILE
- and can you try the original code with
--s3-profile my-sso-profile-name
// Overrides the config profile the Session should be created from. If not
// set the value of the environment variable will be loaded (AWS_PROFILE,
// or AWS_DEFAULT_PROFILE if the Shared Config is enabled).
//
// If not set and environment variables are not set the "default"
// (DefaultSharedConfigProfile) will be used as the profile to load the
// session config from.
Profile string
// Instructs how the Session will be created based on the AWS_SDK_LOAD_CONFIG
// environment variable. By default a Session will be created using the
// value provided by the AWS_SDK_LOAD_CONFIG environment variable.
//
// Setting this value to SharedConfigEnable or SharedConfigDisable
// will allow you to override the AWS_SDK_LOAD_CONFIG environment variable
// and enable or disable the shared config functionality.
SharedConfigState SharedConfigState
So either there is a bug in the SDK not picking up AWS_PROFILE or there is a bug with the configuration chain loader...