使用ansible shell模块时，如何使aws命令可用于sh？

Question

I'm trying to run the following task by using aws cli, because of the aws_s3 module flats out all the bucket keys. However, I keep getting aws: not found error.
aws cli is correctly installed because running the exact same command from the host, works fine.

My task:

- name: Try list
  shell: aws s3 ls "{{ s3_bucket }}"

The full error:

fatal: [cassandra-node-1]: FAILED! => {
    "changed": true, 
    "cmd": "aws s3 ls \"cassandra-snapshotter-test2\"", 
    "delta": "0:00:00.002900", 
    "end": "2019-05-12 13:48:25.705324", 
    "invocation": {
        "module_args": {
            "_raw_params": "aws s3 ls \"cassandra-snapshotter-test2\"", 
            "_uses_shell": true, 
            "argv": null, 
            "chdir": null, 
            "creates": null, 
            "executable": null, 
            "removes": null, 
            "stdin": null, 
            "warn": true
        }
    }, 
    "msg": "non-zero return code", 
    "rc": 127, 
    "start": "2019-05-12 13:48:25.702424", 
    "stderr": "/bin/sh: 1: aws: not found", 
    "stderr_lines": [
        "/bin/sh: 1: aws: not found"
    ], 
    "stdout": "", 
    "stdout_lines": []
}

Why can't I run the aws cli from the Ansible task?

Answer 1

The AWS binary is not available to the sh interpreter on this host.

From a shell session run

$ which aws

to find where the awscli is located.

Make sure this directory is included in the PATH environment variable

$ echo $PATH

If it is not you can either configure your server to include it when a shell is opened

# bash
$ echo 'export PATH=$PATH:/path/to/awscli/dir'  >> ~/.bash_profile

# KSH/sh
$ echo 'export PATH=$PATH:/path/to/awscli/dir'  >> ~/.profile

Alternately you can use the ansible environment property to set environment variables in memory for a particular play, task, etc.

environment:
  PATH: "{{ lookup('env', 'PATH) }}:/path/to/awscli/dir"

Finally, for brevity, you can modify the shell ansible is using for the shell module in your ansible.cfg using the executable key under the [defaults] section. This would allow you to change it from the sh interpreter to something else like bash.