# AWS EC2 not able to create indices in elasticsearch

**URL:** <https://discuss.elastic.co/t/aws-ec2-not-able-to-create-indices-in-elasticsearch/72123>\
**Category:** Elasticsearch\
**Created:** [January 19, 2017, 6:58am UTC](https://discuss.elastic.co/t/aws-ec2-not-able-to-create-indices-in-elasticsearch/72123 "2017-01-19T06:58:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pushkar\_Sharan](https://avatars.discourse-cdn.com/v4/letter/p/5daacb/32.png) [@Pushkar\_Sharan](https://discuss.elastic.co/u/Pushkar_Sharan)\
**Post date:** [January 19, 2017, 6:58am UTC](https://discuss.elastic.co/t/aws-ec2-not-able-to-create-indices-in-elasticsearch/72123/1 "2017-01-19T06:58:38Z")

</div>

Hello All,  
I did my first ELK setup on AWS Ec2 instance. for learning purpose i have kept it all on single instance. I have done below configurations but still not able to create indices.  
xx.xxx.xx.xx is my IP address

ElasticSearch (1.4.4): [http://xx.xxx.xx.xx:9200/\_cat/indices](http://xx.xxx.xx.xx:9200/_cat/indices)

Logstash (1.4.2): nano /etc/logstash/conf.d/logstash.conf  
input { file { path =\> "/tmp/logstash.txt" } } output { elasticsearch { host =\> "xx.xxx.xx.xx" protocol =\>"http" } }

Kibana (4.0.1): [http://xx.xxx.xx.xx:5601](http://xx.xxx.xx.xx:5601)  
nano config/kibana.yml  
elasticsearch\_url: "[http://xx.xxx.xx.xx:9200](http://xx.xxx.xx.xx:9200)"

I am adding values like this to create time stamp indices but not able to. please advise what am I missing.

echo "This is elasticsearch" \>\> /tmp/logstash.txt  
echo "This is elasticsearch" \>\> /tmp/logstash.txt  
echo "This is elasticsearch" \>\> /tmp/logstash.txt  
echo "This is elasticsearch" \>\> /tmp/logstash.txt

Thanks in advance

---

<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 19, 2017, 6:59am UTC](https://discuss.elastic.co/t/aws-ec2-not-able-to-create-indices-in-elasticsearch/72123/2 "2017-01-19T06:59:43Z")

</div>

1 - DO NOT expose ES to the internet with no security!  
2 - Why are you running 1.4.4?

---

<div class="post-metadata">

**Author:** ![Pushkar\_Sharan](https://avatars.discourse-cdn.com/v4/letter/p/5daacb/32.png) [@Pushkar\_Sharan](https://discuss.elastic.co/u/Pushkar_Sharan)\
**Post date:** [January 19, 2017, 7:10am UTC](https://discuss.elastic.co/t/aws-ec2-not-able-to-create-indices-in-elasticsearch/72123/3 "2017-01-19T07:10:40Z")

</div>

Hey Mark,

Thanks for reply.

1. Modified the post 🙂
2. Tutorial had same so installed 1.4.4 for learning,  
please advise if that's the issue will upgrade to 1.7

---

<div class="post-metadata">

**Author:** ![mainec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mainec/32/5557_2.png) [@mainec](https://discuss.elastic.co/u/mainec)\
**Post date:** [January 19, 2017, 9:27am UTC](https://discuss.elastic.co/t/aws-ec2-not-able-to-create-indices-in-elasticsearch/72123/4 "2017-01-19T09:27:46Z")

</div>

What Mark meant with not exposing ES to the internet w/o security wasn't about you posting the IP but about the fact that your ES instance is accessible publicly. Read here for more information why this is a very bad idea, in particular with old versions of Elasticsearch:

> **[Protecting Against Attacks that Hold Your Data for Ransom](https://www.elastic.co/blog/protecting-against-attacks-that-hold-your-data-for-ransom)**
>
> Recent Internet attacks are holding data for ransom. Make sure your Elasticsearch cluster does not become a victim.

[http://code972.com/blog/2017/01/107-dont-be-ransacked-securing-your-elasticsearch-cluster-properly](http://code972.com/blog/2017/01/107-dont-be-ransacked-securing-your-elasticsearch-cluster-properly)

About ES 1.4.4 - if you want to get started with Elasticsearch, my advise would be to use the latest version you can get. It contains lots of new features, performance improvements and bug fixes compared to old versions. No use learning the old API if at the end of the day you'll want to use a newer version anyway.

About your problem in particular: As this happened during playing around with Logstash and Elasticsearch, my hunch would be that you are faced with an outdated sincedb. Check here for more information on this:

[https://www.elastic.co/guide/en/logstash/current/plugins-inputs-file.html#\_tracking\_of\_current\_position\_in\_watched\_files](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-file.html#_tracking_of_current_position_in_watched_files)

What exactly (other than learning) are you trying to accomplish? Why are you looking at such an old version of Elasticsearch?

Isabel

---

<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 16, 2017, 9:27am UTC](https://discuss.elastic.co/t/aws-ec2-not-able-to-create-indices-in-elasticsearch/72123/5 "2017-02-16T09:27:49Z")

</div>

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