Logstash on Fargate - Cannot assign requested address

  • Version: 7.4.0
  • Deployment: AWS ECS Fargate

I'm getting this error:
EADDRNOTAVAIL: Cannot assign requested address - bind - Cannot assign requested address

Since I'm deploying to Fargate, I can't in advance know (or even determine) what the host's IP address will be. It appears from a variety of topics, that people have figured this out, unfortunately, I'm not seeing a solution in any of them.


http.host: ""
http.port: 9600

xpack.monitoring.enabled: true
xpack.monitoring.elasticsearch.hosts: ["https://72298998827d49a3921c2b7060be2394.us-west-2.aws.found.io:9243" ]
xpack.monitoring.elasticsearch.username: logstash_application_user
xpack.monitoring.elasticsearch.password: ${es_password}

xpack.management.enabled: true
xpack.management.pipeline.id: ["rawlogs"]
xpack.management.elasticsearch.hosts: [ "https://72298998827d49a3921c2b7060be2394.us-west-2.aws.found.io:9243" ]
xpack.management.elasticsearch.username: logstash_admin_user
xpack.management.elasticsearch.password: ${logstash_admin}
xpack.management.logstash.poll_interval: 5s


FROM docker.elastic.co/logstash/logstash:7.4.0

RUN rm -f /usr/share/logstash/pipeline/logstash.conf
ADD pipeline/ /usr/share/logstash/pipeline/
ADD config/ /usr/share/logstash/config/

It appears that my issue was specifying the Elastic IP assigned to the network load balancer, instead of the docker default of "".

The topic's error is gone, but the application is still being shutdown, without any apparent cause.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.