No handler was ready to authenticate. 1 handlers were checked

I am able to run an ansible script that creates a Cloudformation in AWS. The script works perfectly fine if I run it via command line.

ansible-playbook uda_aws_dbs.yml --private-key=~/.ssh/myfile.pem -vvvv

I also have a python script that executes the playbook and it also works OK when I run it via command line.

But when trying to automate the execution of the ansible script using Jenkins, I receive the following error message:

**TASK [launch_cloudformation : Launch MPP CloudFormation] ***********************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "No handler was ready to authenticate. 1 handlers were checked. ['HmacAuthV4Handler'] Check your credentials"}**

I have read the documentation for AWS to configure the access keys AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY here http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#config-settings-and-precedence

I am aware of the different ways that they could be configure. As a matter of fact, I have set the keys as ENV variables and also running the aws configure (that creates the ~/.aws/credentials file), but I can't figure out why when running the script through Jenkins seems to not be able to find the credentials.

Any idea?

Start by comparing the environment available to the Jenkins job with the command-line run of uda_aws_dbs.yml, including AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and ~/.aws/credentials. Trace the Python script's playbook invocation and the Launch MPP CloudFormation task; done means Jenkins can authenticate and complete the same playbook successfully.

Written by the indexing model from the issue text.