// Module included in the following assemblies:
//
// * networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc

:_mod-docs-content-type: CONCEPT
[id="nw-aws-ingress-nlb-dual-stack_{context}"]
= Dual-stack networking for the Ingress Controller load balancer on AWS

[role="_abstract"]
On {aws-full}, an Ingress Controller must use a publishing `Service` type Network Load Balancer (NLB) to enable publishing over IPv4 and IPv6 when the cluster runs {aws-short} dual-stack networking. A Classic Load Balancer (CLB) does not support the dual-stack publishing path.

:FeatureName: Dual-stack networking for {product-title} on {aws-full}
include::snippets/technology-preview.adoc[]
:!FeatureName:

If your Ingress Controller uses an NLB and the cluster-scoped `Infrastructure` resource named `cluster` contains `DualStackIPv4Primary` or `DualStackIPv6Primary` in the `status.platformStatus.aws.ipFamily` field, the Ingress Operator sets the Ingress Controller load balancer `Service` to dual-stack IP families.

The `Service` lists IPv4 first for `DualStackIPv4Primary` and IPv6 first for `DualStackIPv6Primary`.

If the Ingress Controller uses a CLB and the cluster runs {aws-short} dual-stack networking, the publishing load balancer stays IPv4-only. To expose the Ingress Controller over IPv4 and IPv6, you must configure the Ingress Controller to use an NLB.
