# Problems connecting an ec2 instances with logstash on to the elastic cloud

**URL:** <https://discuss.elastic.co/t/problems-connecting-an-ec2-instances-with-logstash-on-to-the-elastic-cloud/220865>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [February 25, 2020, 1:47pm UTC](https://discuss.elastic.co/t/problems-connecting-an-ec2-instances-with-logstash-on-to-the-elastic-cloud/220865 "2020-02-25T13:47:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [February 25, 2020, 2:45pm UTC](https://discuss.elastic.co/t/problems-connecting-an-ec2-instances-with-logstash-on-to-the-elastic-cloud/220865/2 "2020-02-25T14:45:14Z")

</div>

As you point out, the port in the `cloud.id` defaults to 443. It can be changed - see this thread: "[ECE + AWS load balancer: port configuration? - #2 by Alex\_Piggott](https://discuss.elastic.co/t/ece-aws-load-balancer-port-configuration/207129/2)"

> LogStash::LicenseChecker::LicenseError: Failed to fetch X-Pack information from Elasticsearch. This is likely due to failure to reach live Elasticsearch cluster

This is almost always nothing to do with xpack/licenses! It just means that whatever comms configuration you have is failing to hit an alive Elasticsearch service

If it's still failing once you've fixed the port and switched back to `cloud.id` then post snippets of your logstash config and we'll take a look

Alex

---

_[View the full topic](https://discuss.elastic.co/t/problems-connecting-an-ec2-instances-with-logstash-on-to-the-elastic-cloud/220865)._