Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AquaConsole Load Balancer is Always Internet-facing #43

Open
ericgomes56 opened this issue Dec 29, 2020 · 2 comments
Open

AquaConsole Load Balancer is Always Internet-facing #43

ericgomes56 opened this issue Dec 29, 2020 · 2 comments

Comments

@ericgomes56
Copy link

Deployed Aqua from this branch using private subnets and CIDR blocks only from private IP addressing space (10.X.X.X).

After deployment, the aquaNlb is Internal (expected), but the AquaConsole is Internet-facing, even after specifying in the CloudFormation template to use private subnets and private CIDR blocks (unexpected).

Please submit a toggle or a way to specify whether the AquaConsole can use Internal or Internet-facing scheme.

@ericgomes56
Copy link
Author

This issue can be resolved by editing the https://s3.amazonaws.com/aqua-security-public/aquaFargate.yaml#L180 from 'internet-facing' to 'internal'.

Please create a flag in the CloudFormation template to toggle this option on the load balancers.

@rshmiel
Copy link
Contributor

rshmiel commented Jan 6, 2021

@ericgomes56 a fix is on the way: see #46
Is there a chance you help us validating it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants