We would like to have filebeat use SNI when connecting to our server. We reach our server via the aaa.com domain, but it only has a TLS cert for bbb.com. We would like to tell filebeat to connect to the server using aaa.com, but to expect a cert for bbb.com when performing a TLS handshake.
I was thinking this might look something like:
output: elasticsearch: tls: server_name: "bbb.com"
and then the parameter would get slotted into https://github.com/elastic/beats/blob/master/libbeat/common/transport/tlscommon/config.go#L87 somehow.
I am happy to write the patch - would it be likely to be accepted? Thanks!