sorry, yes, I assumed EC2 classic which was much more restrictive with security groups.
On Mon, Jun 1, 2015 at 1:06 PM, Ivan S. Freitas <[email protected]> wrote: > If you only want to change the security group's rules you don't need > to delete and recreate it, that can be changed on the fly with > ansible, just change the rules configuration. As far as I know you > would only need to destroy and recreate it to change the description. > > As for Brian's suggestion, you can only reassign security groups on > instances inside a VPC (the provided sample seems to be for EC2 > Classic). If you really need to recreate a security group in EC2 > Classic, then new instances will need to be created as well. > > -- > Ivan Sichmann Freitas > > -- > 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 post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CAG2tFJwf77p4GEUSGUO1Bo%3D1pA1pwqPHZU4UOxAhNnfgTRSUYQ%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- Brian Coca -- 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 post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAJ5XC8n%2Bdh9Pb7F0OaX1-OjFV-Z30TOivSY3J242Lg4yYaSRxQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
