Incident sheet · /security
- System
- Security & Risk
- Filed
- Read
- 3 min · 571 words
- Severity
- Routine
AWS Network Load Balancer adds mutual TLS client checks
AWS Network Load Balancer now verifies X.509 client certificates on TLS listeners, supports revocation lists and identity filters, and is available across commercial and GovCloud regions.

Event log
- AWS Network Load Balancer now verifies X.509 client certificates on TLS listeners.
- Administrators can attach a trust store to a new or existing NLB TLS listener.
- One or more CRLs can block certificates operators no longer trust.
- Filters can match Common Name, Organizational Unit, DNS name or URI, including SPIFFE IDs.
- Availability covers every commercial and AWS GovCloud (US) Region where NLB is available.
AWS Network Load Balancer now verifies X.509 client certificates on TLS listeners across every AWS commercial and AWS GovCloud (US) Region where the service is available.
What changes for NLB customers?
Before this launch, AWS customers that needed mutual TLS with Network Load Balancer had two options: build their own solution or place a third-party proxy in front of the balancer to authenticate clients.
NLB now performs the client check on a TLS listener. The load balancer verifies the client's X.509 certificate, and only trusted clients can reach the targets. It also absorbs the compute-intensive processing that mTLS authentication requires.
With mTLS handled by NLB, backend applications do not need to add certificate-verification logic. That separates client identity checks from application processing while keeping NLB as the point where traffic enters the service.
In practical terms, NLB now acts as the client-certificate gatekeeper before traffic reaches targets.
How do administrators define trusted clients?\n
To activate mTLS, an administrator creates a trust store containing a certificate authority bundle from a CA of the administrator's choice or from AWS Private Certificate Authority. The administrator attaches that store to a new or existing NLB TLS listener.
For certificates an administrator no longer trusts, one or more certificate revocation lists (CRLs) go into the trust store. This lets the operator block those certificates.
For narrower admission, client certificate filters can match:
- The Common Name.
- The Organizational Unit.
- The DNS name in the Subject Alternative Name.
- The URI in the Subject Alternative Name, such as a SPIFFE ID.
Those controls combine a general trust decision with selective identity matching. Revocation rejects certificates the administrator no longer trusts, while filters admit only clients with specified attributes.
In plain terms, trust stores set accepted authorities, revocation lists reject certificates an operator no longer trusts, and filters select particular client identities.
Which workloads fit mutual TLS?
AWS identifies mutual TLS as common for securing communication between IoT devices, APIs, and microservices. Regulated environments also use it because both communicating parties must prove their identity before exchanging traffic.
Under this release, NLB handles the client-certificate decision. A client presents an X.509 certificate at the TLS listener; NLB checks it against the configured trust and access controls before forwarding traffic to a target.
That arrangement keeps the client-certificate check out of backend code. It retains the mutual identity requirement, but AWS now places that control inside the load-balancing service.
For these workloads, identity enforcement shifts into the load balancer without requiring a separate proxy.
How do administrators deploy it?
Administrators can configure mTLS through the AWS Management Console, AWS Command Line Interface (AWS CLI), or APIs. The interface choice does not change the configuration model: establish a trust store, attach it to a new or existing TLS listener, then add certificate revocation lists or client certificate filters as required.
AWS offers the feature in every AWS commercial Region and AWS GovCloud (US) Region where NLB operates. The launch covers every location in those two categories, rather than a limited set of regions.
AWS publishes the implementation in its launch post and the Network Load Balancer User Guide. Teams can add mTLS to an existing NLB TLS listener, while new listeners can use the same trust-store attachment.
Client-certificate enforcement now runs inside NLB across its available commercial and GovCloud regions, without adding certificate logic to backend applications.
via aws.amazon.com (Source)
More from Amara Osei
Show full bio
Correspondent covering regulation, policy and their impact on enterprise information technology and the leaders who run at CIO Monitor.
203 articles
The newsroom digest
One email a day with the stories that matter. No noise.