# Billing Insane ECU for learning Elastic Serverless instance **URL:** \ **Category:** Elastic Search\ **Tags:** serverless\ **Created:** [December 11, 2025, 7:17am UTC](https://discuss.elastic.co/t/billing-insane-ecu-for-learning-elastic-serverless-instance/383973 "2025-12-11T07:17:38Z")\ **Posts on this page:** 2\ **Page:** 2
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [December 12, 2025, 12:59pm UTC](https://discuss.elastic.co/t/billing-insane-ecu-for-learning-elastic-serverless-instance/383973/22 "2025-12-12T12:59:08Z")
> [@Bhaskar\_Reddy](#): > > Can I still use my localhost Kibana to connect to serverless Elasticsearch (need steps to do so), or is the same bug present on localhost as well? As far as I know it is not possible to connect a local Kibana to any cloud cluster, even if it was possible this would also generate costs related to data eggress. Since you are just starting, wouldn't be easier to start with the normal Elastic Cloud hosted offering where you have more controlled costs? ---
**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\ **Post date:** [December 12, 2025, 4:21pm UTC](https://discuss.elastic.co/t/billing-insane-ecu-for-learning-elastic-serverless-instance/383973/23 "2025-12-12T16:21:10Z")
It looks more like the requests that Kibana is triggering. (If this even works with a local Kibana installation — I haven’t tested it,) I don’t think this would solve the underlying issue. Don’t let any Kibana windows running in the background if you don’t need them (not the best fix for now), but I hope we get that fix deployed soon and then we can double check if it works for you or there’s something else (still) up. [Previous page](https://discuss.elastic.co/t/billing-insane-ecu-for-learning-elastic-serverless-instance/383973.md?page=1)