support STS credentials

[automaticgiant]

not handled by 999c979

[dev]
aws_access_key_id = REDACTED
aws_secret_access_key = REDACTED
aws_session_token = REDACTED
aws_security_token = REDACTED
token_expiration = REDACTED

awless --aws-profile [dev] whoami
produces

Error: Your AWS credentials seem undefined! AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY need to be exported in your CLI environment
Installation documentation is at https://github.com/wallix/awless/wiki/Installation

[fxaguessy]

Could you try rather with awless --aws-profile dev whoami -v (-v verbose flag will display the profile that is used to connect to AWS). There should not be [ and ] around the profile name.
But anyway, thanks for reporting, we will improve documentation.

[fxaguessy]

By the way @automaticgiant , as far as I know, in the ~/.aws/config file, a new profile name should be prefixed with profile, i.e. :

[profile dev]
aws_access_key_id = REDACTED
aws_secret_access_key = REDACTED
aws_session_token = REDACTED
aws_security_token = REDACTED
token_expiration = REDACTED

[fxaguessy]

@automaticgiant is this issue still valid ? did you try again with the correct ~/.aws/config file ?

[sdouche]

Hi,
I use a working STS account:

$ eval (assume-role MYACCOUNT)
$ aws ec2 describe-instances
{
    "Reservations": [
        {
            "ReservationId": "r-XXX",
...

But awless can't read something on the whoami command:

$ awless --aws-profile=MYACCOUNT whoami
Username: , Id: XXX, Account: XXX
[error]   InvalidParameter: 1 validation error(s) found.

[automaticgiant]

oh yeah i guess you're right @fxaguessy . i was doing it wrong.
now i see what @sdouche sees.
also interesting i cannot awless config set aws.profile like in #33 because awless whoamiError: Your AWS credentials seem undefined! AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY need to be exported in your CLI environment

[sdouche]

No more error messages on 0.0.24:

ResourceType: assumed-role, Resource: AdministratorAccess/XXX, Id: XXX, Account: XXX