fix(core): Add security group property to HealthMonitor #408
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The health monitor construct creates a application load balancer. This construct creates a new security group(SG) implicitly if it is not provided in constructor properties. This means, a new SG is always created and ingress and egress rules are added automatically based on the target groups created.
Solution
Extended
HealthMonitorProps
with new optional propertysecurityGroup
.Passing this new property to
ApplicationLoadBalancer
construct.Testing
Added unit test.
Deployed fleet with defined security group and tested that:
unhealthy
unhealthy
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license