# Backfeeding Data into a central Ignition gateway

**URL:** <https://forum.inductiveautomation.com/t/backfeeding-data-into-a-central-ignition-gateway/27202>\
**Category:** Ignition\
**Created:** [August 6, 2019, 5:01pm UTC](https://forum.inductiveautomation.com/t/backfeeding-data-into-a-central-ignition-gateway/27202 "2019-08-06T17:01:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Harikrishna\_Patadiya](https://avatars.discourse-cdn.com/v4/letter/h/b487fb/32.png) [@Harikrishna\_Patadiya](https://forum.inductiveautomation.com/u/Harikrishna_Patadiya)\
**Post date:** [August 6, 2019, 5:01pm UTC](https://forum.inductiveautomation.com/t/backfeeding-data-into-a-central-ignition-gateway/27202/1 "2019-08-06T17:01:28Z")

</div>

Hi,

Here’s an interesting thought.

The remote site has data from the past 2 years. We’re trying to spin up a central gateway (hosted on AWS or elsewhere) which will connect to the site gateway through the “Gateway Network”.  
I can see the realtime tags of the ‘remote’ site from the ‘central’ gateway through the use of Remote Tag Provider.

Question is: how can I work with historizing the future data to a central db (AWS RDS) and, more importantly, backfeeding the last 2 years of data into AWS?

I think the issue might exist in the way tags are referenced by the gateway.

Any ideas?