can someone think of a reason why a jar running on a docker image running in ecs would respond fine when curled
curl --request GET \
--location '<https://my.service.elb/actuator/prometheus>' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic BLABLA' \
--header 'Host: <http://ws-preprod-api.eng.mycompany.com|ws-preprod-api.eng.mycompany.com>' \
--insecure
# HELP CalculateTaxEndpoint_invoke90_count_total
# TYPE CalculateTaxEndpoint_invoke90_count_total counter
CalculateTaxEndpoint_invoke90_count_total{calc="invoke90",} 0.0
but when a sidecar running alongside it in ecs makes requests to it it doesn't work
<http://127.0.1:9001/actuator/prometheus>
Failed to establish a new connection: Connection refused
we're pretty sure the port and protocol are correct, because when i run the target docker image locally likewise I can
curl <http://127.0.0.1:9001/actuator/prometheus> //works fine