NoCredentialsError about certbot-s3front HOT 3 CLOSED

@WalshStephen you have to set the environment variables for AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY in order to get the plugin to connect to AWS.

from certbot-s3front.

I found out that I had to re-install awscli to get rid of this "NoCredentialsError". I had a corrupted, misconfigured or misinstalled version of it that the certbot was reading first instead of the exported variables that I set up even in my bash_profile.

from certbot-s3front.

I'm getting this error even if I made sure I set the environment variables correctly (AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY). Normally, I'm using AWS_DEFAULT_PROFILE, but I also got rid of that for testing purposes. In the same console, if I do aws s3 ls, it correctly prints the list of s3 buckets I own.

Just for the record, I also tried installing certbot in two different ways, via pip and then homebrew.

aws-cli/1.15.76 Python/3.6.0 Darwin/18.2.0 botocore/1.10.75
certbot 0.29.1

Update: Setting the global variables still didn't work, but changing one of my profile names in ~/.aws/credential to default made the trick. Apparently, other situations lead to the same workaround: thumbor-community/aws#48

from certbot-s3front.