ec2_group with port range?

279 views
Skip to first unread message

ghe...@gmail.com

unread,
Apr 10, 2014, 8:01:47 PM4/10/14
to ansible...@googlegroups.com
  Is there a way to define an ec2_group with port ranges, or maybe allow all ports for the security group?  There is one example with a protocol of "all" which the code seems to map to -1, but if I use it, I get the following:
...
boto.exception.EC2ResponseError: EC2ResponseError: 400 Bad Request
...
<Error><Code>InvalidPermission.Malformed</Code><Message>Unsupported IP protocol "-1"  - supported: [tcp, udp, icmp]</Message></Error>
...

  I also tried to define the ports as None (which the code seemed to be doing for that "all" protocol, but I got a 
...
<Error><Code>InvalidParameterValue</Code><Message>Invalid integer value None</Message></Error>
...

  Is there a work-around?

Michael DeHaan

unread,
Apr 15, 2014, 5:02:39 PM4/15/14
to ansible...@googlegroups.com
Saw you opened an RFE on this one:  https://github.com/ansible/ansible/issues/6903

Not sure the API supports this or not -- any users of this know?




--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/27c2e6e0-7620-4cad-b3b1-945312be4c36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ghe...@gmail.com

unread,
Apr 15, 2014, 10:03:45 PM4/15/14
to ansible...@googlegroups.com
  Not sure if it matters, but the ec2_group help page does mention an "all" setting, it just doesn't seem to be working.
Reply all
Reply to author
Forward
0 new messages