The redacted values are due to me wanting to limit what I publish onto here, I'd rather not have all my info on the internet.
Each endpoint I am trying to use does work when targeted with the relevant tool whether it be curl, ping, netcat, etc.
You can think of it as a series of AWS EC2 instances hosting each part of the stack, with an AWS LB providing HTTPS endpoints for them, but trying to direct Kibana to the Elasticsearch's HTTPS endpoint is just causing it to fall over. I cannot figure out why though because if I use a http connection that same Elasticsearch it has no problems connecting.
The only error messages I can find are from journalctl:
Aug 11 09:02:36 ip[...] kibana[43062]: {"type":"log","@timestamp":"2020-08-11T09:02:36Z","tags":["warning","elasticsearch","admin"],"pid":43062,"message":"Unable to revive connection: https://[elastic https endpoint]/"}
Aug 11 09:02:36 ip[...] kibana[43062]: {"type":"log","@timestamp":"2020-08-11T09:02:36Z","tags":["warning","elasticsearch","admin"],"pid":43062,"message":"No living connections"}
I could make the SSL certificate available to Kibana/etc. on the VMs but I was hoping that would not be needed since it was already uploaded to the AWS LB. I suppose my question more is whether or not this is something that can work or does it have to be configured in the way described here.
I could very well be missing something else obvious here that is preventing the connection, I am fairly new to using this so my knowledge on the Elastic stack and its security is fairly limited.