Unrestricted traffic tagged when opening all ports for same security groups about scout2 HOT 1 CLOSED

The issue is that having security groups that allow all traffic to themselves essentially creates a flat network between all instances that belong to the group. In most environments, this is an unwanted scenario (e.g. you only allow SQL traffic from your web servers to your DB servers).

As far as the level goes, the severity of this type of issues depends on additional things such as what type of instances belong to that security group, is there also a route that allows external traffic? By default, I chose to set it to danger. If this does not fit your needs, you can either disable the rule or change the level to warning.

The existing ruleset creator no longer works with version 2, but I am currently working on a new version that will provide further information for each rule and allow easier customization.

from scout2.