On 2013/01/31 17:01:29, rog wrote:
> The default is created by automatically, can't be removed, and has
> default permissions set up for tcp and udp (which means that it
> gets selected by some of the filters)
None of that seems relevant for filtering.
> if you try to create another group called "default", you get a
> "The security group 'default' is reserved" error.
I have two groups named "default" in my account, and that's breaking the
test case. One of them comes from VPC. Amazon created it.
> That seems fairly special to me - I *think* we're always guaranteed
> a single group named default... but maybe that's only true of us-east.
On 2013/01/31 17:01:29, rog wrote:
> The default is created by automatically, can't be removed, and has
> default permissions set up for tcp and udp (which means that it
> gets selected by some of the filters)
None of that seems relevant for filtering.
> if you try to create another group called "default", you get a
> "The security group 'default' is reserved" error.
I have two groups named "default" in my account, and that's breaking the
test case. One of them comes from VPC. Amazon created it.
> That seems fairly special to me - I *think* we're always guaranteed
> a single group named default... but maybe that's only true of us-east.
I'm not lying, promise.
https:/ /codereview. appspot. com/7232065/