# EC2 Kibana SSL behind AWS ELB

**URL:** <https://discuss.elastic.co/t/ec2-kibana-ssl-behind-aws-elb/160963>\
**Category:** Kibana\
**Created:** [December 14, 2018, 7:42pm UTC](https://discuss.elastic.co/t/ec2-kibana-ssl-behind-aws-elb/160963 "2018-12-14T19:42:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [December 14, 2018, 7:42pm UTC](https://discuss.elastic.co/t/ec2-kibana-ssl-behind-aws-elb/160963/1 "2018-12-14T19:42:17Z")

</div>

I know this question has been asked in different contexts - but I wanted to post this in order to get an understanding of what specifically needs to be done at the ELB end

We have 2 Kibana EC2 Instances running on ssl.enabled = true using a self-styled certificate. Our ELB is also RECEIVING requests on HTTPs and forwarding to the EC2s on the HTTPS:443 Listener configuration. I'm trying to discover the cause why the traffic isn't flowing - however, for my understanding (and limited understanding of HTTPS handshake) - is there anything I have to do to make the ELB "aware" of the Kibana self-styled certificate?

_This is my SSL config in Kibana.yml._

> server.ssl.cert: /etc/certs/certificate.crt  
> server.ssl.key: /etc/certs/private.key  
> server.ssl.enabled: true

_On the EC2 Instance - the curl is working perfectly FYI_

> curl -k [https://localhost:5601](https://localhost:5601)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 11, 2019, 7:42pm UTC](https://discuss.elastic.co/t/ec2-kibana-ssl-behind-aws-elb/160963/2 "2019-01-11T19:42:17Z")

</div>

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