Fairly typical in case of SSL termination is that the back-end server/service will perceive that as: "the end-user is connected over a clear text protocol" , in other words over plain http.
It will then helpfully try to "resolve that security risk" by redirecting the user to HTTPS.
------ --------------- -------------------
| USER | ===> HTTP ==> | Load balancer | ==> HTTP ==> | Redirect to HTTPS |
------ --------------- -------------------
------ ----------------- -------------------
| USER | ===> HTTPS ==> | SSL termination | ==> HTTP ==> | Redirect to HTTPS |
------ ----------------- -------------------
User makes a new request (they were already using HTTPS, but a redirect is a redirect) but they will again be redirected:
------ ----------------- -------------------
| USER | ===> HTTPS ==> | SSL termination | ==> HTTP ==> | Redirect to HTTPS |
------ ----------------- -------------------
And then repeat that again and again.
The usual solution is to optionally re-configure the SSL termination point to make HTTPS requests to the back-end server, and remove the redirect to HTTPS functionality from the back-end server and move that to Load Balancer.
------ -------------------
| USER | ===> HTTP ==> | Load balancer |
------ | Redirect to HTTPS |
-------------------
------ ----------------- ---------
| USER | ===> HTTPS ==> | SSL termination | ==> HTTP(S) ==> | Respond |
------ ----------------- ---------