Open kaisecheng opened 2 years ago
IIRC, this is by design (although the design may need to be re-thought). When you start Elasticsearch on your own, it binds its HTTP API to 9200 unless you explicitly tell it to bind to a different port (whether or not you have TLS enabled, which is also on-by-default in ES 8.x). Out out-of-the-box experience is to match Elasticsearch's default behaviour.
Logstash version 8.3.3
When the
hosts
point to https url, it is expected to be in port 443 by default, however, the plugin appends 9200.Steps to reproduce
Log
Workaround
The workaround is to add :443 to the hosts hosts => ["https://YOUR_HOST.europe-west2.gcp.elastic-cloud.com:443"]