Skip to main content

Network Load Balancer now supports mutual TLS authentication

Posted on: Nov 19, 2026

Amazon Network Load Balancer (NLB) now supports mutual TLS (mTLS) authentication for clients that present X.509 certificates. Until now, customers who needed mTLS with NLB built their own solutions or ran third-party proxies to authenticate clients. With this launch, NLB verifies client certificates on its TLS listeners, so only trusted clients can reach your targets. You can offload the compute-intensive processing required for mTLS authentication to NLB, without adding certificate logic to your backend applications.

Mutual TLS is commonly used to secure communication between smart devices, APIs and microservices, and wherever both sides must trust each other's identity, such as to meet regulatory requirements. To use mTLS, you create a trust store with a certificate authority (CA) certificate bundle from your own CA or Amazon Private Certificate Authority, and attach it to a new or existing NLB TLS listener. To block certificates you no longer trust, add one or more certificate revocation lists (CRLs) to the trust store. To admit only specific clients, add client certificate filters that match the Common Name, Organizational Unit, or Subject Alternative Name, including SPIFFE IDs. You can set up mTLS with the Amazon Management Console, CLI or APIs.

Mutual TLS for NLB is available in all Amazon Web Services Regions where NLB is available, including the Amazon Web Services China (Beijing) Region, operated by Sinnet, and the Amazon Web Services China (Ningxia) Region, operated by NWCD. To learn more, visit the Network Load Balancer User Guide.