+1. This sounds like a bug. FYI there are some issues related to adding source
group rules that specify ports that need to be fixed. We have also discussed
whether or not the same group should be allow all by default. In ec2 it does.
I personally like having it explicit like this, but I don't
I would like to be able to create a security group rule which allows
communication between VMs within the group. Using the EC2 API this can be done
as follows:
rjh@cloud1:~$ euca-describe-groups
GROUP rjhproject default default
PERMISSION rjhproject default ALLOWS tcp 2222
2 matches
Mail list logo
