# Old clients can't connect to the AWS load balancer: security policy disables TLS 1.0/1.1 (or requires it)

**Code:** `security policy` · **Category:** SSL / TLS · **Seen on:** AWS, SSL

The ELB/ALB/NLB SSL negotiation policy doesn't allow the protocol/ciphers the client uses.

## Meaning

Choose a policy that matches your audience: `ELBSecurityPolicy-TLS13-1-2-2021-06` for modern clients, a `-Res-` or older policy for legacy ones. Compliance may require TLS 1.2+. Check access logs for `tls_version`/`cipher`, and upgrade clients rather than weakening the policy.

## Common causes

- Policy removed TLS 1.0/1.1
- Client only supports legacy ciphers
- ECDSA vs RSA certificate suites mismatch
- FIPS/PCI policy
- Policy updated automatically (predefined default)

## Quick fix

1. Check client TLS versions from access logs
2. Pick the appropriate predefined security policy
3. Upgrade legacy clients

## Detailed fix by platform

### Shell

1. `aws elbv2 modify-listener --listener-arn LISTENER_ARN --ssl-policy ELBSecurityPolicy-TLS13-1-2-2021-06`

## How to diagnose

1. **Policy** — Which?
2. **Client TLS** — Supported?
3. **Logs** — tls_version?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/ssl/elb-security-policy-tls-1-0-clients-fail)
