# ECE Fully Private Installation on AWS - no public endpoints

**URL:** <https://discuss.elastic.co/t/ece-fully-private-installation-on-aws-no-public-endpoints/303263>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [April 26, 2022, 10:41am UTC](https://discuss.elastic.co/t/ece-fully-private-installation-on-aws-no-public-endpoints/303263 "2022-04-26T10:41:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![morariu](https://avatars.discourse-cdn.com/v4/letter/m/0ea827/32.png) [@morariu](https://discuss.elastic.co/u/morariu)\
**Post date:** [April 26, 2022, 10:41am UTC](https://discuss.elastic.co/t/ece-fully-private-installation-on-aws-no-public-endpoints/303263/1 "2022-04-26T10:41:19Z")

</div>

I have installed ECE on AWS EC2 and while the (latest) installation docs are pretty straightforward it stops there. There are no specifics as to what is required after the installation.

I hope someone can help as I can't find any answers to the following:

- The documentation insists that the AWS endpoint must be a public IP. Is that the only way? This would break our security requirements which won't allow any access to the public internet either via a NAT or Internet Gateway.
- Is Kibana installed at the same time? There is no documentation on this.
- Is the only to access the ECE APIs via the GUI?
- I get a connection refused when I curl the nodes (except the initial controller which returns the html page). Is this normal behaviour?

Thank you

---

<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 10, 2022, 10:41am UTC](https://discuss.elastic.co/t/ece-fully-private-installation-on-aws-no-public-endpoints/303263/2 "2022-05-10T10:41:30Z")

</div>

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