# Filebeat, s3access & ECS

**URL:** https://discuss.elastic.co/t/filebeat-s3access-ecs/218011
**Category:** Beats
**Created:** [February 5, 2020, 2:53pm UTC](https://discuss.elastic.co/t/filebeat-s3access-ecs/218011 "2020-02-05T14:53:22Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![cosmo](https://avatars.discourse-cdn.com/v4/letter/c/46a35a/32.png) [@cosmo](https://discuss.elastic.co/u/cosmo)
#### Post date: [February 5, 2020, 2:53pm UTC](https://discuss.elastic.co/t/filebeat-s3access-ecs/218011/1 "2020-02-05T14:53:22Z")

</div>

Hello

Looking to start migrating to ECS, for all the benefits listed on the [blog](https://www.elastic.co/blog/introducing-the-elastic-common-schema)

Got nginx running through the filebeat modules, happy days (although the blog post suggests I should have `event.original` and `message` fields, which I don't appear to have...)

I want to convert some s3 access logs, that are currently getting pulled in by logstash. I figured I could be lazy and steal the filebeat pipeline

> <https://github.com/elastic/beats/blob/master/x-pack/filebeat/module/aws/s3access/ingest/pipeline.yml>

However as I understand things, that doesn't seem to be using ECS yet?  
(EG it uses `aws.s3access.remote_ip` rather than `source.ip`)

Am I right in this belief, and I need to go off an manually map all the fields to ECS?  
Or am I looking at the wrong pipeline for filebeat?

Thanks

---

<div class="post-metadata">

### Author: ![Kaiyan\_Sheng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaiyan_sheng/32/38247_2.png) [@Kaiyan\_Sheng](https://discuss.elastic.co/u/Kaiyan_Sheng)
#### Post date: [February 11, 2020, 2:22pm UTC](https://discuss.elastic.co/t/filebeat-s3access-ecs/218011/2 "2020-02-11T14:22:03Z")

</div>

Hi @cosmo, yeah you are right, `aws.s3access.remote_ip` is not using ECS right now. The fields in s3access fileset that's using ECS are: `tls.cipher`, `tls.version` and `tls.version_protocol`. Maybe [https://github.com/elastic/beats/blob/master/x-pack/filebeat/module/aws/vpcflow/ingest/pipeline.yml](https://github.com/elastic/beats/blob/master/x-pack/filebeat/module/aws/vpcflow/ingest/pipeline.yml) for vpcflow fileset will be a better ECS example for you. I will create a github issue to track converting fields in s3access to ECS as well. 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: [March 10, 2020, 4:22pm UTC](https://discuss.elastic.co/t/filebeat-s3access-ecs/218011/3 "2020-03-10T16:22:04Z")

</div>

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