write out credentials about aws-okta

[dfuentes]

We are unlikely to add this, since we don't want to encourage our developers to keep plaintext credentials. You may be able to work around this for your use case by doing:

$ aws-okta exec <your-profile> -- env

Then pulling the appropriate key/secret/security token from that output.

[JustinPlute]

I stand by entirely what @dfuentes wrote, but just to extend his answer a little bit, I ended up doing this:

$ eval $(aws-okta exec dev-okta -- env | grep AWS - | sed 's/^/export /')
$ aws s3 ls

2018-07-09 10:54:16 sample-bucket
2018-06-22 16:12:37 random-bucket

You could even take this one step further and add that to your .bash_profile, etc.:

function expose_aws_creds() {
    eval $(aws-okta exec $1 -- env | grep AWS - | sed 's/^/export /')
}

Then just do:

$ expose_aws_creds dev-okta
$ aws s3 ls

That way you can easily swap between different profiles.

[sstarcher]

Ya, to make it easier I moved to a different tool that supports this workflow.