I am using ELK stack on AWS (not the AWS Manages Service ES), like Installing ELK stack on EC2 to collect all infrastructure logs and application logs. I have few questions:
1 - What is being used for Data shipping from Instances/Applications to Logstash ?
2 - How many AZ subnets/Security groups are there ?
3 - How many AZs are used ?
4 - Is a ELB used, if Yes betwwen which ELK stack instances.
5 - How are the infrastructure logs collected ?
6 - How is ELK stack monitored ?
7 - Where are the logs stored ?
8 - What is used with Curotor to clean up old indexes ?
9 - What is user for Kibana Auth. ? built in X-Pack ?
10 - How is cloudwatch/cloudtrail/S3/SNS are used in ELK stack ?
Going to try to answer but I don't think I can answer everything.
1 - What is being used for Data shipping from Instances/Applications to Logstash ?
I'd look at filebeat.
2 - How many AZ subnets/Security groups are there ?
No idea.
3 - How many AZs are used ?
No idea.
4 - Is a ELB used, if Yes betwwen which ELK stack instances.
No idea.
5 - How are the infrastructure logs collected ?
Filebeat?
6 - How is ELK stack monitored ?
Each application (Elasticsearch, Logstash, Beats, Kibana) can send its monitoring data to a ElasticStack monitoring cluster which can be the same you deployed.
7 - Where are the logs stored ?
Locally on disk.
8 - What is used with Curotor to clean up old indexes ?
Not sure I understand the question.
9 - What is user for Kibana Auth. ? built in X-Pack ?
You need to set it yourself. Security documentation says it all.
10 - How is cloudwatch/cloudtrail/S3/SNS are used in ELK stack ?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.