# Timestamp minutes loss

**URL:** <https://discuss.elastic.co/t/timestamp-minutes-loss/125827>\
**Category:** Elasticsearch\
**Created:** [March 27, 2018, 9:22pm UTC](https://discuss.elastic.co/t/timestamp-minutes-loss/125827 "2018-03-27T21:22:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pororo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pororo/32/27711_2.png) [@Pororo](https://discuss.elastic.co/u/Pororo)\
**Post date:** [March 27, 2018, 9:22pm UTC](https://discuss.elastic.co/t/timestamp-minutes-loss/125827/1 "2018-03-27T21:22:14Z")

</div>

Hi,

I was trying to ingest the json file into ES by logstash before. And there is one field called "ts" in my json file, ES recognizes it as the timestamp. Everything worked fine when I run it on my local machine.

The problem that the timestamp does not match the actual time happens when I deploy ES on AWS.  
The result shows it lost a couple of minutes than the actual time. I am not sure if there is something needed to concern when it is in the cloud.

---

<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:** [April 24, 2018, 9:22pm UTC](https://discuss.elastic.co/t/timestamp-minutes-loss/125827/2 "2018-04-24T21:22:16Z")

</div>

Closed on April 24, 2018, 9:22pm UTC

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