I now see that the error you’re getting isn’t from the aws_s3 taks that you posted. Instead it’s from an ec2 task - that you did NOT provide. This is quite frustrating - next time provide ALL the information and not leave people in the dark please...
Thx On Mon, 17 Feb 2020 at 06:56, David Rivera <[email protected]> wrote: > > > So I wondering if ansible supports s3, from what I see it does but I just > might not understand how to do it. Im a novice at Ansible, esp in the realm > of using it in conjunction with AWS. > > So I *think* I have to create a role and call it in my playbook? > > my role for learning is: s3-create.yml > - name: Create S3 Bucket > aws_s3: > bucket: my-bucket > mode: create > permission: private-read > region: us-east-1 > > > my playbook: > key_name: my-key > vpc_subnet_id: subnet-02439 > roles: > - s3-create > assign_public_ip: yes > group: my-group > > > when I run it, I get this: > > EntePLAY [Test creating ec2 instance with Ansible] > *********************************************************************************** > > TASK [Gathering Facts] > *********************************************************************************************************** > ok: [localhost] > > TASK [Start New ec2 Instance] > **************************************************************************************************** > fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unsupported > parameters for (ec2) module: roles Supported parameters include: > assign_public_ip, aws_access_key, aws_secret_key, count, count_tag, > debug_botocore_endpoint_logs, ebs_optimized, ec2_url, exact_count, group, > group_id, id, image, instance_ids, instance_initiated_shutdown_behavior, > instance_profile_name, instance_tags, instance_type, kernel, key_name, > monitoring, network_interfaces, placement_group, private_ip, profile, > ramdisk, region, security_token, source_dest_check, spot_launch_group, > spot_price, spot_type, spot_wait_timeout, state, tenancy, > termination_protection, user_data, validate_certs, volumes, vpc_subnet_id, > wait, wait_timeout, zone"} > > PLAY RECAP > *********************************************************************************************************************** > localhost : ok=1 changed=0 unreachable=0 > failed=1 skipped=0 rescued=0 ignored=0 > r code here... > > > From what I read, you cant do it, but that contradicts ansible's docs so I > think I just dont know what I am doing.. > > > any help would be appreciated.. > > > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/6dff2045-5d8a-4239-ba88-f2a588401c56%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/6dff2045-5d8a-4239-ba88-f2a588401c56%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Sent from a mobile device - please excuse the brevity, spelling and punctuation. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAL8fbwPvWLWj3_EzwLfF8QFcPphy9NEOD%3Dg2v7udEFyOSArDFw%40mail.gmail.com.
