ELK Architecture considerations in AWS before deployment

Hi all, we are planning to deploy ELK in AWS infra to receive feeds from around <500 linux beats ( Metricbeats feed only for now ). In terms of minimum capacity lowest cost what would you estimate we need to cover such number? Retention 1 to 2 weeks and no fault tolerance is required, out of the box monitoring (no Logstash for now ) and TLS enabled:

2 nodes of Elastic on which 1 of them running Kibana hosted in EC2 over m5d 32GB RAM 1 tb ssd would be enough?


Yes, that sounds like it'd work.

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