# ECK 8.7.1 elastic agent error

**URL:** <https://discuss.elastic.co/t/eck-8-7-1-elastic-agent-error/332625>\
**Category:** Elastic Agent\
**Tags:** filebeat\
**Created:** [May 5, 2023, 8:31am UTC](https://discuss.elastic.co/t/eck-8-7-1-elastic-agent-error/332625 "2023-05-05T08:31:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![khteh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/khteh/32/147573_2.png) [@khteh](https://discuss.elastic.co/u/khteh)\
**Post date:** [May 5, 2023, 8:31am UTC](https://discuss.elastic.co/t/eck-8-7-1-elastic-agent-error/332625/1 "2023-05-05T08:31:16Z")

</div>

Following [Quickstart | Elastic Cloud on Kubernetes [2.7] | Elastic](https://www.elastic.co/guide/en/cloud-on-k8s/2.7/k8s-elastic-agent-fleet-quickstart.html) to install and run ECK fleet on my EKS but observe the following error in the agent logs:

```auto
[elastic-agent-agent-gdpzn] {"log.level":"info","@timestamp":"2023-05-05T08:21:33.175Z","message":"Connection to backoff(elasticsearch(https://kyberlife-es-http.default.svc:9200)) established","component":{"binary":"filebeat","dataset":"elastic_agent.filebeat","id":"filestream-monitoring","type":"filestream"},"log":{"source":"filestream-monitoring"},"ecs.version":"1.6.0","log.logger":"publisher_pipeline_output","log.origin":{"file.line":147,"file.name":"pipeline/client_worker.go"},"service.name":"filebeat","ecs.version":"1.6.0"}
[elastic-agent-agent-gdpzn] {"log.level":"error","@timestamp":"2023-05-05T08:21:33.198Z","message":"failed to perform any bulk index operations: 500 Internal Server Error: {\"error\":{\"root_cause\":[{\"type\":\"illegal_state_exception\",\"reason\":\"There are no ingest nodes in this cluster, unable to forward request to an ingest node.\"}],\"type\":\"illegal_state_exception\",\"reason\":\"There are no ingest nodes in this cluster, unable to forward request to an ingest node.\"},\"status\":500}","component":{"binary":"filebeat","dataset":"elastic_agent.filebeat","id":"filestream-monitoring","type":"filestream"},"log":{"source":"filestream-monitoring"},"log.logger":"elasticsearch","log.origin":{"file.line":241,"file.name":"elasticsearch/client.go"},"service.name":"filebeat","ecs.version":"1.6.0","ecs.version":"1.6.0"}

```

What am I missing?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 8, 2023, 3:11am UTC](https://discuss.elastic.co/t/eck-8-7-1-elastic-agent-error/332625/2 "2023-05-08T03:11:43Z")

</div>

Looks like you have raised this in ["There are no ingest nodes in this cluster, unable to forward request to an ingest node" errors](https://discuss.elastic.co/t/there-are-no-ingest-nodes-in-this-cluster-unable-to-forward-request-to-an-ingest-node-errors/332701)

I will close this off to minimise confusion.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 8, 2023, 3:11am UTC](https://discuss.elastic.co/t/eck-8-7-1-elastic-agent-error/332625/3 "2023-05-08T03:11:46Z")

</div>