# Tunnel between aws ec2 instances and Elasticsearch Service

**URL:** <https://discuss.elastic.co/t/tunnel-between-aws-ec2-instances-and-elasticsearch-service/226203>\
**Category:** Elasticsearch\
**Created:** [April 2, 2020, 11:38am UTC](https://discuss.elastic.co/t/tunnel-between-aws-ec2-instances-and-elasticsearch-service/226203 "2020-04-02T11:38:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sajeeva\_Lakmal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sajeeva_lakmal/32/58400_2.png) [@Sajeeva\_Lakmal](https://discuss.elastic.co/u/Sajeeva_Lakmal)\
**Post date:** [April 2, 2020, 11:38am UTC](https://discuss.elastic.co/t/tunnel-between-aws-ec2-instances-and-elasticsearch-service/226203/1 "2020-04-02T11:38:16Z")

</div>

We have an elasticsearch service deployment at [elastic.co](http://elastic.co). During the creation of the deployment "AWS" was chosen as the cloud platform. We are given an endpoint URL that resolves to a public IP address. Also, we have an AWS account that has multiple ec2 instances running. When we access elasticsearch service from ec2 instances, the traffic goes through the internet.

Is it possible to make elasticsearch service visible to ec2 instances, as if both are in the same network?

---

<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:** [April 30, 2020, 11:38am UTC](https://discuss.elastic.co/t/tunnel-between-aws-ec2-instances-and-elasticsearch-service/226203/2 "2020-04-30T11:38:18Z")

</div>

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