Reference Issues or PRs

closes #2882

What does this implement/fix?

This alert is because the security group has an egress rule that allows egress to 0.0.0.0/0. Reference for the finding is at https://avd.aquasec.com/misconfig/aws/ec2/avd-aws-0104/

However, the nature of the type of work done in Nebari means that we need this rule, and since it is an egress rule we choose to accept this risk.

This PR causes trivy to ignore this finding for this resource. It is as narrowly scoped as possible so that if this rule finds other instances we can address them if needed.

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

How to test this PR?

Merge and check the security table.

Any other comments?