# AWS ELB/ALB ECE Proxy Configuration

**URL:** <https://discuss.elastic.co/t/aws-elb-alb-ece-proxy-configuration/181622>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [May 17, 2019, 4:15pm UTC](https://discuss.elastic.co/t/aws-elb-alb-ece-proxy-configuration/181622 "2019-05-17T16:15:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chadhanson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chadhanson/32/45372_2.png) [@chadhanson](https://discuss.elastic.co/u/chadhanson)\
**Post date:** [May 17, 2019, 4:15pm UTC](https://discuss.elastic.co/t/aws-elb-alb-ece-proxy-configuration/181622/1 "2019-05-17T16:15:36Z")

</div>

Looking for guidance on setting up an AWS ELB/ALB for my ECE proxy traffic routing to a kibana instance running in the cluster. I have read through the document below on setting up a Route 53 wildcard CNAME to allow for example \*.mydomain.com and forward that traffic to my AWS ELB. I also have a requirement for SSL/TLS certificate encryption. I would also like to setup a DNS record for the cluster name so that my customers do not have to remember the long cluster name of [255e2c6646db4af1996161623133cdf1.mydomain.com:9243](http://255e2c6646db4af1996161623133cdf1.mydomain.com:9243) and cloud have my customer go to an address like [kibana.mydomain.com](http://kibana.mydomain.com) instead.

Thanks for your help!

[https://www.elastic.co/guide/en/cloud-enterprise/current/ece-wildcard-dns.html](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-wildcard-dns.html)

---

<div class="post-metadata">

**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\
**Post date:** [May 17, 2019, 6:26pm UTC](https://discuss.elastic.co/t/aws-elb-alb-ece-proxy-configuration/181622/2 "2019-05-17T18:26:57Z")

</div>

Unfortunately if you use DNS you have to append the cluster id via the `X-Found-Cluster` header ... really to get "alias URLs" you have to use a reverse proxy (like nginx)

Alex

---

<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:** [May 31, 2019, 6:26pm UTC](https://discuss.elastic.co/t/aws-elb-alb-ece-proxy-configuration/181622/3 "2019-05-31T18:26:59Z")

</div>

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