# Unable to access elasticsearch on a particular network

**URL:** <https://discuss.elastic.co/t/unable-to-access-elasticsearch-on-a-particular-network/322878>\
**Category:** Elasticsearch\
**Created:** [January 11, 2023, 6:52am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-on-a-particular-network/322878 "2023-01-11T06:52:33Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jay\_Ostwal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_ostwal/32/99821_2.png) [@Jay\_Ostwal](https://discuss.elastic.co/u/Jay_Ostwal)\
**Post date:** [January 11, 2023, 6:52am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-on-a-particular-network/322878/1 "2023-01-11T06:52:33Z")

</div>

I am using elasticsearch since more than one year on a particular wifi network. Suddenly since 2 days I am unable to access the data from elasticsearch on this particular network and I am getting error as ConnectionError: getaddrinfo EAI\_AGAIN. The strange thing is that I am able to access elasticsearch data if I change the network.  
Elasticsearch is configured on aws. Let me know if you want more information

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 11, 2023, 11:40pm UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-on-a-particular-network/322878/2 "2023-01-11T23:40:34Z")

</div>

Welcome to our community! 😃

What does your elasticsearch.yml look like?  
Can you curl your Elasticsearch host from your networks and share the response?

---

<div class="post-metadata">

**Author:** ![Jay\_Ostwal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_ostwal/32/99821_2.png) [@Jay\_Ostwal](https://discuss.elastic.co/u/Jay_Ostwal)\
**Post date:** [January 12, 2023, 4:47am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-on-a-particular-network/322878/3 "2023-01-12T04:47:06Z")

</div>

I don't think elasticsearch.yml file is available when configured on aws. I can share the access policy which is configured on aws.

```auto
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "*"
      },
      "Action": "es:*",
      "Resource": "arn:aws:es::<arn domain>/<domain_name>/*"
    }
  ]
} 

```

Can you please tell me how to curl my Elasticsearch host from my networks?? Actually I dont have idea about it. Please help

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 12, 2023, 6:24am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-on-a-particular-network/322878/4 "2023-01-12T06:24:16Z")

</div>

Is this the aws service?

---

<div class="post-metadata">

**Author:** ![Jay\_Ostwal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_ostwal/32/99821_2.png) [@Jay\_Ostwal](https://discuss.elastic.co/u/Jay_Ostwal)\
**Post date:** [January 12, 2023, 6:26am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-on-a-particular-network/322878/5 "2023-01-12T06:26:46Z")

</div>

Elasticsearch is configured on aws and the JSON which I shared above is the access policy for same

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 12, 2023, 6:28am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-on-a-particular-network/322878/6 "2023-01-12T06:28:18Z")

</div>

You mean ec2?

I can't help with accecss policies, I don't know anything about them sorry. You might need to ask aws.

---

<div class="post-metadata">

**Author:** ![Jay\_Ostwal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_ostwal/32/99821_2.png) [@Jay\_Ostwal](https://discuss.elastic.co/u/Jay_Ostwal)\
**Post date:** [January 12, 2023, 6:39am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-on-a-particular-network/322878/7 "2023-01-12T06:39:12Z")

</div>

not ec2, opensearch service aws

---

<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:** [January 12, 2023, 6:39am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-on-a-particular-network/322878/8 "2023-01-12T06:39:12Z")

</div>

OpenSearch/OpenDistro are AWS run products and differ from the original Elasticsearch and Kibana products that Elastic builds and maintains. You may need to contact them directly for further assistance.

(This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: )

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 12, 2023, 6:40am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-on-a-particular-network/322878/9 "2023-01-12T06:40:48Z")

</div>

Ok, then we aren't able to help you there as this is an aws product and you will need to ask their support.

---

<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:** [February 9, 2023, 6:41am UTC](https://discuss.elastic.co/t/unable-to-access-elasticsearch-on-a-particular-network/322878/10 "2023-02-09T06:41:39Z")

</div>

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