# Enriching logs with AWS entity information

**URL:** <https://community.dynatrace.com/t/enriching-logs-with-aws-entity-information/49429>\
**Category:** Logs\
**Tags:** openpipeline, aws, logs\
**Created:** [December 18, 2024, 7:18pm UTC](https://community.dynatrace.com/t/enriching-logs-with-aws-entity-information/49429 "2024-12-18T19:18:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![manisundaram](https://avatars.discourse-cdn.com/v4/letter/m/ba8739/32.png) [@manisundaram](https://community.dynatrace.com/u/manisundaram)\
**Post date:** [December 18, 2024, 7:18pm UTC](https://community.dynatrace.com/t/enriching-logs-with-aws-entity-information/49429/1 "2024-12-18T19:18:05Z")

</div>

we have 2 integrations in place

1. AWS Cloudwatch integration, where we are pulling in cloudwatch metrics for various AWS Services

2. Log integration. We are pulling in AWS Database Migration service logs from cloudwatch into Dynatrace

When logs are coming in, they are not getting mapped to entities (AWS DMS Entities)

When looking through documentation for Dynatrace, entity linking is not available for DMS Services -&nbsp;[Stream logs via Amazon Data Firehose — Dynatrace Docs](https://docs.dynatrace.com/docs/shortlink/lma-stream-logs-with-firehose#view-aws-logs)

We are thinking if we can use OpenPipeline to achieve this ? Is it possible - any thoughts ?

---

<div class="post-metadata">

**Author:** ![RohitBisht](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/rohitbisht/32/38577_2.png) [@RohitBisht](https://community.dynatrace.com/u/RohitBisht)\
**Post date:** [December 19, 2024, 2:58am UTC](https://community.dynatrace.com/t/enriching-logs-with-aws-entity-information/49429/2 "2024-12-19T02:58:30Z")

</div>

Hi Mani,

It is possible you can get the “entity id” from the AWS service and manually tag the logs using classic log processing rules or openpipeline.&nbsp;  
I have done something similar in the past for cloudwatch logs and it works well.  
Best is to get details about the AWS service entity from the API and then reuse it to map the topology accordingly.

> **[Monitored entities API - GET an entity](https://docs.dynatrace.com/docs/dynatrace-api/environment-api/entity-v2/get-entity)**
>
> View parameters of a monitored entity via Dynatrace API.

---

<div class="post-metadata">

**Author:** ![Peter\_Youssef](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/peter_youssef/32/14668_2.png) [@Peter\_Youssef](https://community.dynatrace.com/u/Peter_Youssef)\
**Post date:** [December 19, 2024, 6:27am UTC](https://community.dynatrace.com/t/enriching-logs-with-aws-entity-information/49429/3 "2024-12-19T06:27:06Z")

</div>

Hi&nbsp;[@manisundaram](https://community.dynatrace.com/user/34365)

In addition to valuable inputs by&nbsp;[@RohitBisht](https://community.dynatrace.com/user/45903)

Regarding the raised concern PFA resources for actual execution as per monitoring requirements:

AWS:

- [Monitor Amazon Web Services with CloudWatch metrics — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-with-aws/cloudwatch-metrics)
- [Amazon CloudWatch Metric Streams — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-with-aws/aws-metrics-ingest/cloudwatch-metric-streams)
- [Advanced Monitoring of AWS with Dynatrace](https://video.dynatrace.com/watch/XBanorC1aSmHWhH5G6jCva)
- [https://www.youtube.com/watch?v=zX6CFj5EB94](https://www.youtube.com/watch?v=zX6CFj5EB94)

**Entities** :

- [Monitored entities API — Dynatrace Docs](https://docs.dynatrace.com/docs/discover-dynatrace/references/dynatrace-api/environment-api/entity-v2)

 ![2024-12-19_10h19_13.png](https://global.discourse-cdn.com/dynatrace/original/3X/d/c/dc76b32f411a6452bdcab40a7eca8ced502137ba.png)

**Logs** :

- [Cloud provider log forwarding — Dynatrace Docs](https://docs.dynatrace.com/docs/analyze-explore-automate/logs/lma-log-ingestion/lma-log-ingestion-via-api/lma-cloud-provider-log-forwarding#aws-log-forwarding)
- [Log Management and Analytics use cases — Dynatrace Docs](https://docs.dynatrace.com/docs/analyze-explore-automate/logs/lma-use-cases)

**Log processing with Open Pipeline:**

- [Log processing with OpenPipeline — Dynatrace Docs](https://docs.dynatrace.com/docs/analyze-explore-automate/logs/lma-openpipeline)

**Regarding the accurate mapping:**

- You can refer to the available topology relationships upon the successful integration.
- [https://docs.dynatrace.com/docs/discover-dynatrace/references/semantic-dictionary/model/dt-entities](https://docs.dynatrace.com/docs/discover-dynatrace/references/semantic-dictionary/model/dt-entities)

Hoping it helps.

BR,

Peter
