# Custom metadata for AWS Lambda on Dynatrace

**URL:** <https://community.dynatrace.com/t/custom-metadata-for-aws-lambda-on-dynatrace/39310>\
**Category:** Cloud platforms\
**Tags:** aws, tagging, lambda\
**Created:** [April 14, 2023, 3:08pm UTC](https://community.dynatrace.com/t/custom-metadata-for-aws-lambda-on-dynatrace/39310 "2023-04-14T15:08:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vinnu\_arige\_moe](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/vinnu_arige_moe/32/8903_2.png) [@vinnu\_arige\_moe](https://community.dynatrace.com/u/vinnu_arige_moe)\
**Post date:** [April 14, 2023, 3:08pm UTC](https://community.dynatrace.com/t/custom-metadata-for-aws-lambda-on-dynatrace/39310/1 "2023-04-14T15:08:01Z")

</div>

Hello folks,

we are implementing Dynatrae on AWS services and trying to figure out on how to get custom metadata on Lambda functions.

I tried adding custom prop into Lambda environment variables

DT\_CUSTOM\_PROP= AWS\_ACCOUNT=\<Aws-acocunt-name\>

We were not able to see this in the Lambda properties and also tried adding same through AWS tags and could see it. I did not see any correlation on how to use aws tags into dt auto tagging.

We are mainly want to do this for our management zones.

thanks

Vinnu

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [June 8, 2023, 4:37pm UTC](https://community.dynatrace.com/t/custom-metadata-for-aws-lambda-on-dynatrace/39310/2 "2023-06-08T16:37:03Z")

</div>

Dynatrace can and will ingest tags as they exist on the AWS instances. You can also make internal Dynatrace tags via Auto tag rules or manual tag rules. For the auto tagging, you’ll need to use the entity selector.

---

<div class="post-metadata">

**Author:** ![anildondapati](https://avatars.discourse-cdn.com/v4/letter/a/35a633/32.png) [@anildondapati](https://community.dynatrace.com/u/anildondapati)\
**Post date:** [July 25, 2023, 6:49am UTC](https://community.dynatrace.com/t/custom-metadata-for-aws-lambda-on-dynatrace/39310/3 "2023-07-25T06:49:41Z")

</div>

Hi&nbsp;[@ChadTurner](https://community.dynatrace.com/user/14877)&nbsp;,

Does this mean, we have to set&nbsp;DT\_CUSTOM\_PROP as tags for lambda function&nbsp;instead of environment variables.

Thanks in advance

---

<div class="post-metadata">

**Author:** ![patrick\_thurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/patrick_thurner/32/34782_2.png) [@patrick\_thurner](https://community.dynatrace.com/u/patrick_thurner)\
**Post date:** [March 18, 2025, 11:47am UTC](https://community.dynatrace.com/t/custom-metadata-for-aws-lambda-on-dynatrace/39310/4 "2025-03-18T11:47:11Z")

</div>

Hi,  
you can use entity selectors to resolve relationship for the lambda services traced with our agent integration towards the AWS cloud-integration generated entity and it’s metadata. Please also see:&nbsp;[Tags and management zones for AWS integration — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-with-aws/cloudwatch-metrics/tags-and-management-zones-aws#tabgroup--auto--2--lambda).

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [March 18, 2025, 12:17pm UTC](https://community.dynatrace.com/t/custom-metadata-for-aws-lambda-on-dynatrace/39310/5 "2025-03-18T12:17:00Z")

</div>

Just as&nbsp;[@patrick\_thurner](https://community.dynatrace.com/user/6138)&nbsp;provided, you’ll want to leverage this support document:&nbsp;[Link](https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-with-aws/cloudwatch-metrics/tags-and-management-zones-aws?_gl=1*tmceb9*_gcl_aw*R0NMLjE3MzkzNjUyOTQuQ2p3S0NBaUFxckc5QmhBVkVpd0FhUHU1enBYVURZXzQ3amhMWEdtMWhsenhTc0ZTSW43NHNvX095S2xlUHIwRXN5cEt1bjgxRktYMFFCb0NYNndRQXZEX0J3RQ..*_gcl_dc*R0NMLjE3MzkzNjUyOTQuQ2p3S0NBaUFxckc5QmhBVkVpd0FhUHU1enBYVURZXzQ3amhMWEdtMWhsenhTc0ZTSW43NHNvX095S2xlUHIwRXN5cEt1bjgxRktYMFFCb0NYNndRQXZEX0J3RQ..*_gcl_au*MTQ1NDY5ODE3My4xNzM0NzA2OTI0*_ga*MTkwNjA1Mjk3OS4xNzI5NzA0NTcx*_ga_1MEMV02JXV*MTc0MjMwMDExNi4zMDMuMS4xNzQyMzAwMTYwLjAuMC4w#tabgroup--auto--2--lambda)