AWS ELB

AWS ELB Status Codes

Showing 3 status codes

AWS Elastic Load Balancer (ELB) specific status codes are proprietary responses used by AWS Application Load Balancers (ALB) and Classic Load Balancers to indicate issues with client connections, request processing, or authentication.

The primary AWS ELB codes are 460 (client closed connection before the load balancer could respond), 463 (request's X-Forwarded-For header exceeded 30 IP addresses), and 561 (error during authentication with an identity provider when using OIDC authentication).

These codes appear in ELB access logs and help diagnose issues with client connections and load balancer configuration. Understanding them is essential for troubleshooting AWS-based applications and ensuring proper load balancer health.

📴460awsClient Closed ConnectionYou hung up too soon! Like calling tech support and then getting impatient and hanging up before they could help. The load balancer had your answer ready, but you'd already left the building!
🔗463awsToo Many IPs in X-Forwarded-ForYour forwarding chain is way too long! It's like a game of telephone that went through 30+ people - we're cutting you off before this gets ridiculous. How many proxies are you going through?!
🚷561awsUnauthorizedThe bouncer said no! Your request made it to AWS's VIP entrance, but the Lambda security guard checked your credentials and decided you're not on the list. Access denied at the door!

AWS ELB Status Codes FAQ

What does AWS ELB Error 460 mean?

AWS ELB 460 indicates the client closed the connection with the load balancer before the response was completed. This often happens due to client timeouts, impatient users, or network issues. Check if your backend response times are too slow.

How do I fix AWS ELB Error 561?

AWS ELB 561 occurs during OIDC authentication when the load balancer cannot authenticate with the identity provider. Verify your identity provider configuration, check the client ID and secret, ensure the authorization endpoint is accessible, and review CloudWatch logs for details.

What causes AWS ELB Error 463?

AWS ELB 463 occurs when the X-Forwarded-For header contains more than 30 IP addresses, exceeding AWS limits. This can happen with deeply nested proxy chains. Review your proxy configuration and consider truncating the header or using alternative approaches for client IP tracking.