Error when configuring logstash to output to an Elasticsearch cluster on AWS EC2.

0 votes

I'm facing trouble when configuring logstash to output to an Elasticsearch cluster on AWS EC2. Logstash version 1.1.5 and Elasticsearch 1.19.8.

Output configuration in logstash:

cluster.name: logstash-searcher
path.data: /usr/local/elasticsearch/data
path.work: /usr/local/elasticsearch/tmp
path.logs: /usr/local/elasticsearch/logs
path.plugins: /usr/local/elasticsearch/plugins
bootstrap.mlockall: true
cloud.aws.region: eu-west-1
cloud.aws.access_key: --
cloud.aws.secret_key: --
discovery.type: ec2
discovery.ec2.host_type: public_ip
discovery.ec2.groups: elasticsearch
gateway.type: s3
gateway.s3.bucket: es-logstash

transport.tcp.port: 9300-9400

Getting an error of sort

Failed to index an event, will retry {:exception=>org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [1m], 

So, what could be the issue?

Mar 14 in AWS by datageek
• 3,040 points
62 views

1 answer to this question.

0 votes

Ok. The issue could be that embedded elasticsearch instance of logstash was using its default discovery mode. Because the elasticsearch cluster is configured with cloud-aws the embedded elasticsearch of logstash needs to as well.

So, add an elasticsearch.yml configuration file to the working directory of logstash

answered Mar 14 by Archana
• 5,560 points

Related Questions In AWS

0 votes
1 answer
0 votes
1 answer
0 votes
1 answer

AWS Access Key error when uploading to S3

You can try getting creating a new ...READ MORE

answered Feb 6 in AWS by Priyaj
• 56,520 points
1,020 views
0 votes
1 answer
0 votes
1 answer
+1 vote
1 answer

How to make an application private on AWS Elastic Beanstalk?

Like you said by default, your application ...READ MORE

answered Oct 25, 2018 in AWS by Archana
• 5,560 points
34 views