I found the updated fork for aws-cli in this post: Aws-cli role can't install pip
So I now have the following changes added:
trellis/group_vars/all/vault.yml
:
trellis/requirements.yml
:
- name: aws-cli
src: https://github.com/dstil/ansible-aws-cli
version: 5c1c14d9b0e6264605bd475c86d4ea67e7d5896f
trellis/group_vars/all/vault.yml
vault_aws_access_key_id: xxxxxxx
vault_aws_secret_access_key: "xxxxxxx"
trellis/server.yml
:
- { role: aws-cli, tags: [aws-cli] }
Wondering where should I do run actual aws-cli commands from?
/trellis
vagrant ssh
in first?
I tested aws-cli
on /trellis, then also vagrant ssh -> /src/www/mydomain.co.uk -> aws-cli
both times got back: -bash: aws-cli: command not found