Feature request: option to use preconfigured vpc versus creating a new one

[naeem-gitonga]

Hi:
I am working in an environment that requires me to avoid creating new VPCs. I would like to request a feature for allowing the user of the construct to pass the construct their own VPC for use with the Clamscan construct's resources. This would also allow the user to specify the subnets to use with the VPC. In response to this request, I have made a PR.

Thank you!

[dontirun]

Thanks for the feature request and PR! There are a few other changes that would need to be made in order for this to work. Those changes would mutate the existing VPC configuration so I have some concerns about implementing them.

[naeem-gitonga]

Thank you for responding! I will do more digging and connect soon.

[villelahdenvuo]

VPC created by this construct does not follow AWS security best practices:

[dontirun]

VPC created by this construct does not follow AWS security best practices:

I'm most cases I would agree that's a problem, but in this case the VPC doesn't have any mechanism to allow for outbound traffic besides the S3 gateway endpoint

[villelahdenvuo]

Looks like there is a workaround for this using the CDK feature flags: this.node.setContext(EC2_RESTRICT_DEFAULT_SECURITY_GROUP, true);