Fix: Lambda Topology Issue

[yiyuan-he]

Issue #, if available:

Lambda Topology issue -- more context in PRs for Python and JavaScript:

• Fix: Lambda Topology Issue aws-otel-python-instrumentation#319
• Fix: Lambda Topology Issue aws-otel-js-instrumentation#149

Description of changes:

• Apply fix for the Lambda Topology issue. The logic mimics the fix in our other ADOT SDKs.
• Adding back AWS Resource support for Lambda.
  • Remove Lambda:Function:Name resource type support  #907
  • We previously removed support due to the Lambda Topology issue

Test plan:

Set up two Lambda functions with Java runtimes and tested with custom Lambda layer with fix built-in. Tested both AWS SDK v1 and v2. Below are screenshots of the topology for various configurations.

v1 Topology (lambdaA & lambdaB instrumented)

v2 Topology (lambdaA & lambdaB instrumented)

We observe the following correct behaviors for topology above:

• Service entity node for Invoke call to downstream lambda.
• AWS Resource node for GetFunction call to downstream lambda.
• AWS Resource node for ListBuckets call to downstream s3.

v1 Topology (lambdaB not instrumented)

v2 Topology (lambdaB not instrumented)

We observe the following correct behaviors for topology above:

• Downstream lambda called with Invoke is correctly treated as RemoteService entity when not instrumented

Additionally, I generated the spans locally to verify the lambda instrumentation patch behaves correctly.

v1 Invoke

v2 Invoke

v1 GetFunction

v2 GetFunction

We observe the following correct behaviors in the spans above:

• For Invoke calls, we see aws.remote.service and aws.remote.environment correctly populated in the spans.
• For non-Invoke calls (i.e. GetFunction), we see AWS Resource attributes such as aws.remote.resource.identifier and aws.cloudformation.primary.identifier correctly populated.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.