# ECE + AWS load balancer: port configuration?

**URL:** <https://discuss.elastic.co/t/ece-aws-load-balancer-port-configuration/207129>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [November 8, 2019, 2:31pm UTC](https://discuss.elastic.co/t/ece-aws-load-balancer-port-configuration/207129 "2019-11-08T14:31:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mesiasc](https://avatars.discourse-cdn.com/v4/letter/m/b38774/32.png) [@mesiasc](https://discuss.elastic.co/u/mesiasc)\
**Post date:** [November 8, 2019, 2:31pm UTC](https://discuss.elastic.co/t/ece-aws-load-balancer-port-configuration/207129/1 "2019-11-08T14:31:33Z")

</div>

I have a load balancer in front of ECE to front the cluster URLs for kibana and elasticsearch. These all use port 9243 and the config in the ECE UI allows me to set a CNAME to be used instead of the [ip.es.io](http://ip.es.io) service... This works and I can use the CloudID to configure beats etc.

So far so good. But I would like to present the services not only on the domain of my choosing but move the port to a standard one - eg. 443, which would allow me to use the service through a corporate web proxy.

I configure the load balancer to listen on 443 and target 9243.

I can add the port assignment to the endpoint configuration / CNAME and it is accepted and the resulting CloudID seems right. But none of the links in the ECE UI work then. I suspect this is a bug. (I can manually make a CloudID including the port 443 using base64 that works with beats.)

So far the least broken approach is to configure the endpoint without port, the links in ECE point to xxx:9243 which doesn't get through the proxy, but removing the :9243 then makes the link work. The manually modified CloudID also works to get beats to access elasticsearch over port 443.

Is there any way to configure ECE to build URLs and CloudID with a specific port in addition to the specific endpoint?

---

<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:** [November 11, 2019, 7:30pm UTC](https://discuss.elastic.co/t/ece-aws-load-balancer-port-configuration/207129/2 "2019-11-11T19:30:59Z")

</div>

I believe this API call will work:

```auto
curl -k -X POST -u admin:xxxxxxxxx https://{ADMIN_SERVER}:12443/api/v1/platform/configuration/store/https_port -H 'Content-Type: application/json' -d '
{
   "value" : "443"
}

```

---

<div class="post-metadata">

**Author:** ![mesiasc](https://avatars.discourse-cdn.com/v4/letter/m/b38774/32.png) [@mesiasc](https://discuss.elastic.co/u/mesiasc)\
**Post date:** [November 12, 2019, 10:04am UTC](https://discuss.elastic.co/t/ece-aws-load-balancer-port-configuration/207129/3 "2019-11-12T10:04:48Z")

</div>

Alex,

thanks for the hint - that's an awesome fix.

I had to change POST to PUT because "Config option [https\_port] already exists" but it seems to work nicely.

---

<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:** [November 26, 2019, 10:04am UTC](https://discuss.elastic.co/t/ece-aws-load-balancer-port-configuration/207129/4 "2019-11-26T10:04:55Z")

</div>

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