# Metricbeat AWS module metricsets and exported fields **URL:** \ **Category:** Beats\ **Tags:** filebeat, metricbeat\ **Created:** [November 19, 2020, 11:45am UTC](https://discuss.elastic.co/t/metricbeat-aws-module-metricsets-and-exported-fields/255976 "2020-11-19T11:45:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![nickgregz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickgregz/32/54533_2.png) [@nickgregz](https://discuss.elastic.co/u/nickgregz)\ **Post date:** [November 19, 2020, 11:45am UTC](https://discuss.elastic.co/t/metricbeat-aws-module-metricsets-and-exported-fields/255976/1 "2020-11-19T11:45:39Z")
Hello, I have a question regarding exported fields of metricsets for the AWS metricbeat module, specifically if they all include some variation of a unique identifier. For example the RDS module has an [exported field](https://www.elastic.co/guide/en/beats/metricbeat/current/exported-fields-aws.html#_rds_3) `aws.rds.db_instance.identifier ` which can uniquely identify metricbeat data to a specific RDS database thus enabling the option of filtering and possibly separating the data of each database to a different pipeline. For other modules the documentation does not seem to indicate any such field in the exported fields such as ELB, Lambda... So the question is does metricbeat data for all the grouped metricsets(RDS, ELB, EC2, Lambda...) contain a unique identifier on which the data can be filtered and separated (same question applies to grouped Filebeat filesets)? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 17, 2020, 1:45pm UTC](https://discuss.elastic.co/t/metricbeat-aws-module-metricsets-and-exported-fields/255976/2 "2020-12-17T13:45:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.