Skip to content

(aws-elasticloadbalancingv2): Prevent using denyAllIgwTraffic for load balancers that do not use dual stack addressing #30247

@moelasmar

Description

@moelasmar

Describe the feature

Setting denyAllIgwTraffic flag for Load balancers with IPV4 addressing is not allowed, and cause this deployment error Load balancer attribute key 'ipv6.deny_all_igw_traffic' is not supported on load balancers with IP address type 'ipv4'.

Sample usecase:

new elbv2.NetworkLoadBalancer(stack, 'NLB', {
  vpc,
  crossZoneEnabled: true,
  deletionProtection: false,
  denyAllIgwTraffic: true,
  clientRoutingPolicy: elbv2.ClientRoutingPolicy.PARTIAL_AVAILABILITY_ZONE_AFFINITY,
});

Also, there are some integration test cases that could not be deployed because of this issue.

Use Case

It is better to figure out this issue during synthesize time instead of deployment time.

Proposed Solution

Prevent customers form setting denyAllIgwTraffic flag is the Load balancers do not use dual stack addressing.

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

CDK version used

v2.142.0

Environment details (OS name and version, etc.)

macos

Metadata

Metadata

Assignees

No one assigned

    Labels

    @aws-cdk/aws-elasticloadbalancingv2Related to Amazon Elastic Load Balancing V2bugThis issue is a bug.feature-requestA feature should be added or improved.p2testingRelated to tests needed to be modified or added.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions