# RDS to Elasticsearch - Setting up Logstash in a highly available/redundant architecture

**URL:** https://discuss.elastic.co/t/rds-to-elasticsearch-setting-up-logstash-in-a-highly-available-redundant-architecture/210070
**Category:** Logstash
**Created:** [December 1, 2019, 4:12pm UTC](https://discuss.elastic.co/t/rds-to-elasticsearch-setting-up-logstash-in-a-highly-available-redundant-architecture/210070 "2019-12-01T16:12:40Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![dshenoy](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@dshenoy](https://discuss.elastic.co/u/dshenoy)
#### Post date: [December 1, 2019, 4:12pm UTC](https://discuss.elastic.co/t/rds-to-elasticsearch-setting-up-logstash-in-a-highly-available-redundant-architecture/210070/1 "2019-12-01T16:12:41Z")

</div>

I am looking into a highly available solution to feed in AWS RDS transactions into my Elasticsearch repository. There are some articles on this topic. For example:

> <https://stackoverflow.com/questions/43688180/simplest-way-to-get-data-from-aws-mysql-rds-to-aws-elasticsearch>

But this is not a flexible and agile in the long-term for changes. It seems that the best way to do this is through AWS DMS. The AWS documentation seems to imply using Logstash. I have seen the following article:

> **[How to keep Elasticsearch synced with a RDBMS using Logstash and JDBC](https://www.elastic.co/blog/how-to-keep-elasticsearch-synchronized-with-a-relational-database-using-logstash)**
>
> When Elasticsearch is deployed as a search solution alongside of existing relational databases (RDBMSs), it's important to keep the data synchronized between the two data stores. Learn how to easily sync your data using the Logstash JDBC input...

This article seems promising. But I have some concerns. For example, what happens if the node goes down. How can we save and keep track of the value for "tracking\_column" which is stored on disk at [.logstash\_jdbc\_last\_run.](https://www.elastic.co/guide/en/logstash/7.1/plugins-inputs-jdbc.html#plugins-inputs-jdbc-last_run_metadata_path)

Can we store this value in a database because it seems that only one instance of Logstash can be used at a time with this setup.

Thanking you in advance for any 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: [December 29, 2019, 4:12pm UTC](https://discuss.elastic.co/t/rds-to-elasticsearch-setting-up-logstash-in-a-highly-available-redundant-architecture/210070/2 "2019-12-29T16:12:54Z")

</div>

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