# How to solve AWS elasticsearch CircuitBreakingException error without elasticsearch.yml file?

**URL:** <https://discuss.elastic.co/t/how-to-solve-aws-elasticsearch-circuitbreakingexception-error-without-elasticsearch-yml-file/257226>\
**Category:** Elasticsearch\
**Created:** [December 1, 2020, 3:23pm UTC](https://discuss.elastic.co/t/how-to-solve-aws-elasticsearch-circuitbreakingexception-error-without-elasticsearch-yml-file/257226 "2020-12-01T15:23:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![I\_Hathout](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/i_hathout/32/76915_2.png) [@I\_Hathout](https://discuss.elastic.co/u/I_Hathout)\
**Post date:** [December 1, 2020, 3:23pm UTC](https://discuss.elastic.co/t/how-to-solve-aws-elasticsearch-circuitbreakingexception-error-without-elasticsearch-yml-file/257226/1 "2020-12-01T15:23:26Z")

</div>

I have the CircuitBreakingException issue and I found a solution in another topic, by setting the elasticsearch.yml real memory breaker variable to false, but in my case AWS Elasticsearch has no .yml file. so how to solve it?

Error: TransportError: TransportError(429, 'circuit\_breaking\_exception', '[parent] Data too large, data for [\<http\_request\>] would be [8360164871/7.7gb], which is larger than the limit of [8143876915/7.5gb], real usage: [8360020792/7.7gb], new bytes reserved: [144079/140.7kb]')

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [December 1, 2020, 3:31pm UTC](https://discuss.elastic.co/t/how-to-solve-aws-elasticsearch-circuitbreakingexception-error-without-elasticsearch-yml-file/257226/2 "2020-12-01T15:31:18Z")

</div>

We don't support this service here so I guess you need to ask their support.

But may be this way to solve the problem is only hidding a more important problem.  
When this error is happening? What are the elasticsearch logs...?

BTW did you look at [Cloud by Elastic](https://www.elastic.co/cloud), also available if needed from [AWS Marketplace](https://aws.amazon.com/marketplace/pp/B01N6YCISK) ?

Cloud by elastic is one way to have access to **all features** , all managed by us. Think about what is there yet like Security, Monitoring, Reporting, SQL, Canvas, Maps UI, Alerting and built-in solutions named [Observability](https://www.elastic.co/observability), [Security](https://www.elastic.co/security), [Enterprise Search](https://www.elastic.co/enterprise-search) and what is coming next 🙂 ...

---

<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:** [December 29, 2020, 3:31pm UTC](https://discuss.elastic.co/t/how-to-solve-aws-elasticsearch-circuitbreakingexception-error-without-elasticsearch-yml-file/257226/3 "2020-12-29T15:31:19Z")

</div>

Closed on December 29, 2020, 3:31pm UTC

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