# ELK as a service without beats in Kubernetes

**URL:** <https://discuss.elastic.co/t/elk-as-a-service-without-beats-in-kubernetes/298732>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [March 3, 2022, 11:34am UTC](https://discuss.elastic.co/t/elk-as-a-service-without-beats-in-kubernetes/298732 "2022-03-03T11:34:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wcpoon](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@wcpoon](https://discuss.elastic.co/u/wcpoon)\
**Post date:** [March 3, 2022, 11:34am UTC](https://discuss.elastic.co/t/elk-as-a-service-without-beats-in-kubernetes/298732/1 "2022-03-03T11:34:42Z")

</div>

I want to build ELK as a service in kubernetes.  
How to configure logstash to handle external syslog data into the ELK stack in kubernetes?  
Can I do it without using beats?  
Anyone can help?

---

<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:** [March 31, 2022, 11:34am UTC](https://discuss.elastic.co/t/elk-as-a-service-without-beats-in-kubernetes/298732/2 "2022-03-31T11:34:48Z")

</div>

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