Question

我写了一个快速的ansible playbook来启动一个简单的ec2实例，但我想我有一个关于我想如何进行身份验证的问题。

我不想做的是将我的aws访问/密钥设置为env变量，因为它们每小时到期，我需要通过脚本重新生成~/.aws/credentials文件。

现在，我的ansible剧本看起来像这样：

--- # Launch ec2
- name: Create ec2 instance
  hosts: local
  connection: local
  gather_facts: false
  vars:
    profile: profile_xxxx
    key_pair: usrxxx
    region: us-east-1
    subnet: subnet-38xxxxx
    security_groups: ['sg-e54xxxx', 'sg-bfcxxxx', 'sg-a9dxxx']
    image: ami-031xxx
    instance_type: t2.small
    num_instances: 1
    tag_name: ansibletest
    hdd_volumes:
    - device_name: /dev/sdf
      volume_size: 50
      delete_on_termination: true
    - device_name: /dev/sdh
      volume_size: 50
      delete_on_termination: true
  tasks:
    - name: launch ec2
      ec2:
        count: 1
        key_name: "{{ key_pair }}"
        profile: "{{ profile }}"
        group_id: "{{ security_groups }}"
        instance_type: "{{ instance_type }}"
        image: "{{ image }}"
        region: "{{ region }}"
        vpc_subnet_id: "{{ subnet }}"
        assign_public_ip: false
        volumes: "{{ hdd_volumes }}"
        instance_tags:
          Name: "{{ tag_name }}"
          ASV: "{{ tag_asv }}"
          CMDBEnvironment: "{{ tag_cmdbEnv }}"
          EID: "{{ tag_eid }}"
          OwnerContact: "{{ tag_eid }}"
      register: ec2
    - name: print ec2 vars
      debug: var=ec

我的主机文件是：

[local]
localhost ansible_python_interpreter=/usr/local/bin/python2.7

我像这样运行我的剧本：

ansible-playbook -i hosts launchec2.yml -vvv

然后回来：

PLAYBOOK: launchec2.yml ********************************************************
1 plays in launchec2.yml

PLAY [Create ec2 instance] *****************************************************

TASK [launch ec2] **************************************************************
task path: /Users/usrxxx/Desktop/cloud-jumper/Ansible/launchec2.yml:27
Using module file /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ansible/modules/core/cloud/amazon/ec2.py
<localhost> ESTABLISH LOCAL CONNECTION FOR USER: usrxxx
<localhost> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo ~/.ansible/tmp/ansible-tmp-1485527483.82-106272618422730 `" && echo ansible-tmp-1485527483.82-106272618422730="` echo ~/.ansible/tmp/ansible-tmp-1485527483.82-106272618422730 `" ) && sleep 0'
<localhost> PUT /var/folders/cx/_fdv7nkn6dz21798p_bn9dp9ln9sqc/T/tmpnk2rh5 TO /Users/usrxxx/.ansible/tmp/ansible-tmp-1485527483.82-106272618422730/ec2.py
<localhost> PUT /var/folders/cx/_fdv7nkn6dz21798p_bn9dp9ln9sqc/T/tmpEpwenH TO /Users/usrxxx/.ansible/tmp/ansible-tmp-1485527483.82-106272618422730/args
<localhost> EXEC /bin/sh -c 'chmod u+x /Users/usrxxx/.ansible/tmp/ansible-tmp-1485527483.82-106272618422730/ /Users/usrxxx/.ansible/tmp/ansible-tmp-1485527483.82-106272618422730/ec2.py /Users/usrxxx/.ansible/tmp/ansible-tmp-1485527483.82-106272618422730/args && sleep 0'
<localhost> EXEC /bin/sh -c '/usr/bin/env python /Users/usrxxx/.ansible/tmp/ansible-tmp-1485527483.82-106272618422730/ec2.py /Users/usrxxx/.ansible/tmp/ansible-tmp-1485527483.82-106272618422730/args; rm -rf "/Users/usrxxx/.ansible/tmp/ansible-tmp-1485527483.82-106272618422730/" > /dev/null 2>&1 && sleep 0'
fatal: [localhost]: FAILED! => {
    "changed": false, 
    "failed": true, 
    "invocation": {
        "module_name": "ec2"
    }, 
    "module_stderr": "usage: ec2.py [-h] [--list] [--host HOST] [--refresh-cache]\n              [--profile BOTO_PROFILE]\nec2.py: error: unrecognized arguments: /Users/usrxxx/.ansible/tmp/ansible-tmp-1485527483.82-106272618422730/args\n", 
    "module_stdout": "", 
    "msg": "MODULE FAILURE"
}
    to retry, use: --limit @/Users/usrxxx/Desktop/cloud-jumper/Ansible/launchec2.retry

PLAY RECAP *********************************************************************
localhost                  : ok=0    changed=0    unreachable=0    failed=1

我在ec2.py文件中注意到它说：

NOTE: This script assumes Ansible is being executed where the environment
variables needed for Boto have already been set:
    export AWS_ACCESS_KEY_ID='AK123'
    export AWS_SECRET_ACCESS_KEY='abc123'

This script also assumes there is an ec2.ini file alongside it.  To specify a
different path to ec2.ini, define the EC2_INI_PATH environment variable:

    export EC2_INI_PATH=/path/to/my_ec2.ini

If you're using eucalyptus you need to set the above variables and
you need to define:

    export EC2_URL=http://hostname_of_your_cc:port/services/Eucalyptus

If you're using boto profiles (requires boto>=2.24.0) you can choose a profile
using the --boto-profile command line argument (e.g. ec2.py --boto-profile prod) or using
the AWS_PROFILE variable:

    AWS_PROFILE=prod ansible-playbook -i ec2.py myplaybook.yml

所以我这样跑了：

AWS_PROFILE=profile_xxxx ansible-playbook -i hosts launchec2.yml -vvv

但仍然得到了相同的结果...

---- ----- EDIT

我也像这样跑：

export ANSIBLE_HOST_KEY_CHECKING=false
export AWS_ACCESS_KEY=<your aws access key here>
export AWS_SECRET_KEY=<your aws secret key here>

ansible-playbook -i hosts launchec2.yml

但仍然得到了回来......似乎仍然是凭证问题？

usrxxx$ ansible-playbook -i hosts launchec2.yml 

PLAY [Create ec2 instance] *****************************************************

TASK [launch ec2] **************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "module_stderr": "usage: ec2.py [-h] [--list] [--host HOST] [--refresh-cache]\n              [--profile BOTO_PROFILE]\nec2.py: error: unrecognized arguments: /Users/usrxxx/.ansible/tmp/ansible-tmp-1485531356.01-33528208838066/args\n", "module_stdout": "", "msg": "MODULE FAILURE"}
    to retry, use: --limit @/Users/usrxxx/Desktop/cloud-jumper/Ansible/launchec2.retry

PLAY RECAP *********************************************************************
localhost                  : ok=0    changed=0    unreachable=0    failed=1

---编辑2 ------

完全删除了ansible，然后安装了自制软件但得到了同样的错误....所以我想去了它寻找ec2.py（Using module file /usr/local/Cellar/ansible/2.2.1.0/libexec/lib/python2.7/site-packages/ansible/modules/core/cloud/amazon/ec2.py）的目录并用这个替换了ec2.py ... https://raw.githubusercontent.com/ansible/ansible/devel/contrib/inventory/ec2.py....but现在出现此错误：

Using /Users/usrxxx/ansible/ansible.cfg as config file

PLAYBOOK: launchec2.yml ********************************************************
1 plays in launchec2.yml

PLAY [Create ec2 instance] *****************************************************

TASK [aws : launch ec2] ********************************************************
task path: /Users/usrxxx/Desktop/cloud-jumper/Ansible/roles/aws/tasks/main.yml:1
Using module file /usr/local/Cellar/ansible/2.2.1.0/libexec/lib/python2.7/site-packages/ansible/modules/core/cloud/amazon/ec2.py
fatal: [localhost]: FAILED! => {
    "failed": true, 
    "msg": "module (ec2) is missing interpreter line"
}

Answer 1

似乎您已将ec2.py inventory script放入/path/to/playbook/library/文件夹中您不应该在那里放置动态库存脚本 - 这样Ansible运行库存脚本而不是ec2 module。

从项目的库文件夹（或ansible.cfg中定义的Ansible全局library）中删除ec2.py，然后重试。

如何在使用ansible ec2.py模块时使用aws配置文件

1 个答案: