Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Not seeing any HTTPCode_Backend Response on the Classic Load Balancer logs

0

Hello,
I have a classic LB with TCP 443 port forwarding to my backend instances, where I have SSL certificate configured on IIS.
IIS logging is enabled.
When deliberately hitting some URLs with wrong parameters, I get 403 errors from IIS, but I do not see any HTTPCode_Backend in teh CLoudwatch
I don't see it in the Athena when trying to analyze the ELB logs either.
elb_repsonse_code and backend_response_code in Athena are both empty.

Can anyone point me in the troubleshooting direction?>

Thanks

Topics
Networking & Content Delivery
Tags
Elastic Load Balancing
Language
English

asked 6 years ago564 views

1 Answer
0

Ok, figured it out.
Looks like my only option to have the HTTPBackend_response_2xx/3xx/4xx/5xx in the cloudwatch metrics is to switch to HTTPS listener, instead of TCP:443.

answered 6 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content