# Filebeat for AWS Cloudwatch does not support timestamps with milliseconds

**URL:** <https://discuss.elastic.co/t/filebeat-for-aws-cloudwatch-does-not-support-timestamps-with-milliseconds/327338>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [March 9, 2023, 8:59am UTC](https://discuss.elastic.co/t/filebeat-for-aws-cloudwatch-does-not-support-timestamps-with-milliseconds/327338 "2023-03-09T08:59:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tomas\_Mocek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomas_mocek/32/118239_2.png) [@Tomas\_Mocek](https://discuss.elastic.co/u/Tomas_Mocek)\
**Post date:** [March 9, 2023, 8:59am UTC](https://discuss.elastic.co/t/filebeat-for-aws-cloudwatch-does-not-support-timestamps-with-milliseconds/327338/1 "2023-03-09T08:59:08Z")

</div>

Hi,

we are using AWS [Filebeat CloudWatch](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-aws-cloudwatch.html) input, and everything works as expected, however, the logs are fetched without milliseconds precision.

I believe this is caused because of this [code](https://github.com/elastic/beats/blob/main/x-pack/filebeat/input/awscloudwatch/processor.go#L54), which cuts milliseconds retrieved from AWS CW API.

Is my assumption correct or is there any other way to ingest logs with milliseconds?

Thanks!

---

<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 6, 2023, 10:59am UTC](https://discuss.elastic.co/t/filebeat-for-aws-cloudwatch-does-not-support-timestamps-with-milliseconds/327338/2 "2023-04-06T10:59:17Z")

</div>

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