Currently, if creds are specified in environment variables, which boto supports as a credential source, cfu still looks for creds in the default profile, and if the profile doesn't exist, errors.
$ env | grep AWS
AWS_SECRET_ACCESS_KEY=snip
AWS_ACCESS_KEY_ID=snip
$ cloudforensics aws ap-southeast-2a listinstances
<snip>
botocore.exceptions.ProfileNotFound: The config profile (default) could not be found
The utility should be updated to support environment variables as a credential source.
Currently, if creds are specified in environment variables, which boto supports as a credential source, cfu still looks for creds in the
defaultprofile, and if the profile doesn't exist, errors.The utility should be updated to support environment variables as a credential source.