AWS auth is janky
Currently, CredMaster cannot fall through to boto3's auth. In other words, using the default AWS profile or AWS environment variables for configuration is impossible without passing flags (i.e. --profile_name default or --secret-access-key=$AWS_SECRET_ACCESS_KEY).
4cdcbc18309886531b61de9238de1c1fb236c72c cleans up reading from the config file, and allows fall-through.
Changed base, Dev branch is holding a significant amount of new features, would like to implement this there
Changed the auth checks to work with the new dev base branch, should be good for merge.
AWS Auth has been deemed no longer janky
Thanks for the PR