Mar
5th
2010
Fri
5th
2010
When using AWS Security Groups, don’t forget self
This was frustrating, and maybe I missed it in the documentation, but I didn’t see it anywhere - when you have two machines in the same AWS Security Group, the assumption would be that they can interchange network traffic freely between them (at least, that was my assumption), but they can’t. If you want them to be able to talk to each other, you have to add the security group to itself as a valid connection endpoint.