# Gather Heartbeat Monitor Data from S3 Bucket

**URL:** <https://discuss.elastic.co/t/gather-heartbeat-monitor-data-from-s3-bucket/341058>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [August 17, 2023, 9:00pm UTC](https://discuss.elastic.co/t/gather-heartbeat-monitor-data-from-s3-bucket/341058 "2023-08-17T21:00:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![szhao](https://avatars.discourse-cdn.com/v4/letter/s/e480ec/32.png) [@szhao](https://discuss.elastic.co/u/szhao)\
**Post date:** [August 17, 2023, 9:00pm UTC](https://discuss.elastic.co/t/gather-heartbeat-monitor-data-from-s3-bucket/341058/1 "2023-08-17T21:00:03Z")

</div>

Are you able to configure the `heatbeat.config.monitors:` path variable to be set to a S3 bucket? As of now, I would like to automatically generate the monitor .yaml files, store them in a S3 bucket, and then through another container access these monitors and run a heartbeat instance on this potentially dynamically changing series of monitors.

Anybody have tips for moving forward?

---

<div class="post-metadata">

**Author:** ![Alberto\_Delgado](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alberto_delgado/32/98488_2.png) [@Alberto\_Delgado](https://discuss.elastic.co/u/Alberto_Delgado)\
**Post date:** [August 18, 2023, 2:49pm UTC](https://discuss.elastic.co/t/gather-heartbeat-monitor-data-from-s3-bucket/341058/2 "2023-08-18T14:49:12Z")

</div>

Hi @szhao,

Thanks for reaching out and welcome to the community!

> Are you able to configure the `heatbeat.config.monitors:` path variable to be set to a S3 bucket?

In theory, the only available options are described here (and that doesn't include S3 bucket):

> **[Configure Heartbeat monitors | Heartbeat Reference \[8.9\] | Elastic](https://www.elastic.co/guide/en/beats/heartbeat/8.9/configuration-heartbeat-options.html)**

Despite so, I will contact colleagues with more expertise on this than me and see if there are any approaches that might be followed and we'll let you know

Thanks,  
Alberto

---

<div class="post-metadata">

**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:** [August 18, 2023, 4:19pm UTC](https://discuss.elastic.co/t/gather-heartbeat-monitor-data-from-s3-bucket/341058/3 "2023-08-18T16:19:31Z")

</div>

> [@szhao](#):
>
> Anybody have tips for moving forward?

`heartbeat.config.monitors.path` needs to be a path on the filesystem where heartbeat is running.

What you want may work if you mount the s3 bucket as a filesystem in the container using s3fs for example.

---

<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:** [September 15, 2023, 6:19pm UTC](https://discuss.elastic.co/t/gather-heartbeat-monitor-data-from-s3-bucket/341058/4 "2023-09-15T18:19:53Z")

</div>

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