A possible approach that I will try today is: 1. create the VPC 2. create the security groups with their custom settings within the VPC *and a dummy one* 3. launch the WHOLE batch of EC2s at once, *in the dummy SG* *4. have some subsequent tasks moving random EC2s (as they share exactly the same specs) in different SGs.* *5. play around with the EC2s based on their SG membership*
On Tuesday, 25 November 2014 18:55:58 UTC+1, Dan Vaida wrote: > > Hello all, > > Was just curious how to accomplish this. Right now I am launching all > instances at once, so I am maximizing my chances to have all the EC2s as > close as possible. As AWS and common sense advises, it's desirable to have > it like so, any subsequent EC2 launch targeting the same placement group > would be having significantly lower chances to benefit from that smaller > physical distance between the hypervisors. > > I am managing them using the instances tags. > > Thing is, I want to go the "deny all" way and the first stop for that are > the Security Groups. > > With my current playbooks, I can't see any way of doing: > 1. create the VPC > 2. create the security groups with their custom settings within the VPC > 3. launch the WHOLE batch of EC2s at once, *each EC2 in its destined > security group*. > > The underlined part is giving me a hard time. > > Perhaps someone has tried this as well and might want to share some ideas. > > Thanks! > > > -- 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/4a8bf9b6-37dd-4eb7-a1f3-15b8fcb5c0f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
