We've noticed that a number of you lovely humans are using Elasticsearch on AWS to do interesting and creative work. Doing so involves addressing a number of questions: Where do I start? How do I size my cluster? What types of instances should I use? What are some recommended disk configurations? As many of you know, there really isn't a one-size-fits-all solution to get up and running, and there are a number of factors to consider when configuring your ELK cluster on AWS. Given the massive interest in this area, we thought we would invite you learn from the experiences of others and see how some organizations got up and running.
The first real-world example will be from one of our own engineers, Drew Raines. At Elasticsearch, we use AWS in a few ways: for QA in advance of new releases and when we want to replicate a customer's environment and need to spin up a bunch of machines quickly. Learn from Drew how you can get an ELK cluster running on AWS in minutes and the tradeoffs to consider when configuring ELK on AWS.
Up next will be we're really excited to introduce you to Joe Kinsella, CTO and founder of CloudHealth Technologies. Joe is an Elasticsearch user and will talk about how his company uses Elasticsearch on AWS to monitor the health of cloud services and tools. Of particular interest to most of you out there, he'll talk about how they sized and configured their clusters.
- How Elasticsearch Uses ELK on AWS - Drew Raines
- Elasticsearch on AWS at CloudHealth Technologies - Joe Kinsella and Efe Yardimci