Update Layer ARN version in the docs and release highlights

aws-otel · Jan 6, 2025 · 19b09d0 · 19b09d0
1 parent 19989f9
commit 19b09d0
Show file tree

Hide file tree

Showing 7 changed files with 12 additions and 12 deletions.
diff --git a/...ontent/Blogs/ReleaseBlogs/aws-distro-for-opentelemetry-lambda-layer-v0.42.0.mdx b/...ontent/Blogs/ReleaseBlogs/aws-distro-for-opentelemetry-lambda-layer-v0.42.0.mdx
@@ -32,9 +32,9 @@ AWS Distro for OpenTelemetry Lambda Layers now supports AMD64 and ARM64 in the f
 <SectionSeparator />
 
 ### Release Highlights
-
+- Added support for nodejs20.x and nodejs 22.x runtime in Nodejs lambda layer.
 - Python layer [**aws-otel-python-<amd64|arm64>-ver-1-29-0**](https://aws-otel.github.io/docs/getting-started/lambda/lambda-python) contains OpenTelemetry Python `v1.29.0` and ADOT Collector for Lambda `v0.42.0`
-- Nodejs layer [**aws-otel-nodejs-<amd64|arm64>-ver-1-30-0**](https://aws-otel.github.io/docs/getting-started/lambda/lambda-js) contains OpenTelemetry JavaScript Core `v1.30.0` with AWS Lambda Instrumentation `v0.41.0` and ADOT Collector for Lambda `v0.42.0`
+- Nodejs layer [**aws-otel-nodejs-<amd64|arm64>-ver-1-30-0**](https://aws-otel.github.io/docs/getting-started/lambda/lambda-js) contains OpenTelemetry JavaScript Core `v1.30.0` with AWS Lambda Instrumentation `v0.50.0` and ADOT Collector for Lambda `v0.42.0`
 - Java-Wrapper layer [**aws-otel-java-wrapper-<amd64|arm64>-ver-1-32-0**](https://aws-otel.github.io/docs/getting-started/lambda/lambda-java) contains OpenTelemetry Java `v1.32.0` and ADOT Collector for Lambda `v0.42.0`
 - Java-Agent layer [**aws-otel-java-agent-<amd64|arm64>-ver-1-32-0**](https://aws-otel.github.io/docs/getting-started/lambda/lambda-java-auto-instr) contains AWS Distro for OpenTelemetry Java Instrumentation `v1.32.0` and ADOT Collector for Lambda `v0.42.0`
 - Collector layer **aws-otel-collector-<amd64|arm64>-ver-0-115-0** contains ADOT Collector for Lambda `v0.42.0`. Compatible with [.NET](https://aws-otel.github.io/docs/getting-started/lambda/lambda-dotnet) and [Go](https://aws-otel.github.io/docs/getting-started/lambda/lambda-go) runtimes.

diff --git a/src/docs/getting-started/lambda/lambda-dotnet.mdx b/src/docs/getting-started/lambda/lambda-dotnet.mdx
@@ -69,7 +69,7 @@ Find the supported regions and amd64/arm64 layer ARN in the table below for the
 
 |Supported   Regions  |Lambda layer ARN format  | Contents |
 |---------------------|-------------------------|----------|
-| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-collector-<architecture\>-ver-0-102-1:1 | Contains ADOT Collector v0.40.0 |
+| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-collector-<architecture\>-ver-0-115-0:2 | Contains ADOT Collector v0.42.0 |
 
 ### Enable Tracing
 Once you’ve instrumented the Lambda function code and deployed to Lambda service, you can follow the instructions below to apply Lambda layer.

diff --git a/src/docs/getting-started/lambda/lambda-go.mdx b/src/docs/getting-started/lambda/lambda-go.mdx
@@ -87,7 +87,7 @@ Find the supported regions and amd64/arm64 layer ARN in the table below for the
 
 |Supported   Regions  |Lambda layer ARN format  | Contents |
 |---------------------|-------------------------|----------|
-| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-collector-<architecture\>-ver-0-102-1:1 | Contains ADOT Collector v0.40.0 |
+| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-collector-<architecture\>-ver-0-115-0:2 | Contains ADOT Collector v0.42.0 |
 
 ### Enable Tracing
 Once you’ve instrumented the Lambda function code and deployed to Lambda service, you can follow the instructions below to apply Lambda layer.

diff --git a/src/docs/getting-started/lambda/lambda-java-auto-instr.mdx b/src/docs/getting-started/lambda/lambda-java-auto-instr.mdx
@@ -29,7 +29,7 @@ Find the supported regions and amd64/arm64 layer ARN in the table below for the
 
 |Supported   Regions  |Lambda layer ARN format  | Contents |
 |---------------------|-------------------------|----------|
-| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-java-agent-<architecture\>-ver-1-32-0:3 | Contains [ADOT Java Auto-Instrumentation Agent v1.32.0](https://github.com/aws-observability/aws-otel-java-instrumentation/releases/tag/v1.32.0) <br/><br/> Contains ADOT Collector v0.40.0 |
+| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-java-agent-<architecture\>-ver-1-32-0:4 | Contains [ADOT Java Auto-Instrumentation Agent v1.32.0](https://github.com/aws-observability/aws-otel-java-instrumentation/releases/tag/v1.32.0) <br/><br/> Contains ADOT Collector v0.42.0 |
 
 ### Enable auto-instrumentation for your Lambda function
 
@@ -142,7 +142,7 @@ receivers:
       grpc:
       http:
 exporters:
-  logging:
+  debug:
   awsxray:
   prometheusremotewrite:
     endpoint: <workspace_remote_write_url>
@@ -157,9 +157,9 @@ service:
       exporters: [awsxray]
     metrics:
       receivers: [otlp]
-      exporters: [logging, prometheusremotewrite]
+      exporters: [debug, prometheusremotewrite]
 ```
-2. Upload this collector config as the OPENTELEMETRY_CONFIG_FILE environment variable to configure the Lambda Layer to export metrics to your workspace, following these [instructions](/docs/getting-started/lambda#custom-configuration-for-the-adot-collector-on-lambda).
+2. Upload this collector config as the OPENTELEMETRY_COLLECTOR_CONFIG_URI environment variable to configure the Lambda Layer to export metrics to your workspace, following these [instructions](/docs/getting-started/lambda#custom-configuration-for-the-adot-collector-on-lambda).
 
 Note: If enabling metrics, make sure your Lambda role has the required AWS Prometheus permissions. For more on permissions and policies required on AMP for AWS Lambda, see the [AWS Managed Service for Prometheus documentation](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-and-IAM.html#AMP-IAM-policies-built-in).
 

diff --git a/src/docs/getting-started/lambda/lambda-java.mdx b/src/docs/getting-started/lambda/lambda-java.mdx
@@ -39,7 +39,7 @@ Find the supported regions and amd64/arm64 layer ARN in the table below for the
 
 |Supported   Regions  |Lambda layer ARN format  | Contents |
 |---------------------|-------------------------|----------|
-| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-java-wrapper-<architecture\>-ver-1-32-0:3 | Contains [OpenTelemetry for Java v1.32.0](https://github.com/open-telemetry/opentelemetry-java/releases/tag/v1.32.0) with [Java Instrumentation v1.32.0](https://github.com/aws-observability/aws-otel-java-instrumentation/releases/tag/v1.32.0) <br/><br/> Contains ADOT Collector v0.40.0 |
+| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-java-wrapper-<architecture\>-ver-1-32-0:4 | Contains [OpenTelemetry for Java v1.32.0](https://github.com/open-telemetry/opentelemetry-java/releases/tag/v1.32.0) with [Java Instrumentation v1.32.0](https://github.com/aws-observability/aws-otel-java-instrumentation/releases/tag/v1.32.0) <br/><br/> Contains ADOT Collector v0.42.0 |
 
 ### Enable auto-instrumentation for your Lambda function
 To enable the AWS Distro for OpenTelemetry in your Lambda function, you need to add and configure the layer, and then enable tracing.

diff --git a/src/docs/getting-started/lambda/lambda-js.mdx b/src/docs/getting-started/lambda/lambda-js.mdx
@@ -17,7 +17,7 @@ The AWS managed Lambda layer for ADOT JavaScript provides a plug and play user e
 
 ## Requirements
 
-The Lambda layer supports Node.JS v14+ Lambda runtimes. For more information about supported JavaScript and Node.JS versions, see the [OpenTelemetry JavaScript documentation](https://github.com/open-telemetry/opentelemetry-js).
+The Lambda layer supports Node.JS v18+ Lambda runtimes. For more information about supported JavaScript and Node.JS versions, see the [OpenTelemetry JavaScript documentation](https://github.com/open-telemetry/opentelemetry-js).
 
 For *TypeScript users*, if you are using `esbuild` (either directly or through tools such as the AWS CDK), you *must* export your handler function through `module.exports` rather than with the `export` keyword! The AWS mananaged layer for ADOT JavaScript needs to hot-patch your handler at runtime, but can't because `esbuild` makes your handler immutable when using the `export` keyword. 
 
@@ -31,7 +31,7 @@ Find the supported regions and amd64/arm64 layer ARN in the table below for the
 
 |Supported   Regions  |Lambda layer ARN format  | Contents |
 |---------------------|-------------------------|----------|
-| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-nodejs-<architecture\>-ver-1-18-1:4 |Contains [OpenTelemetry for JavaScript v1.18.1](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v1.18.1) with [Lambda instrumentation v0.41.0](https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-aws-lambda-v0.41.0) <br/><br/> Contains ADOT Collector v0.40.0 |
+| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-nodejs-<architecture\>-ver-1-30-1:1 |Contains [OpenTelemetry for JavaScript v1.30.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v1.30.0) with [Lambda instrumentation v0.41.0](https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-aws-lambda-v0.41.0) <br/><br/> Contains ADOT Collector v0.42.0 |
 
 ### Enable auto-instrumentation for your Lambda function
 To enable the AWS Distro for OpenTelemetry in your Lambda function, you need to add and configure the layer, and then enable tracing.

diff --git a/src/docs/getting-started/lambda/lambda-python.mdx b/src/docs/getting-started/lambda/lambda-python.mdx
@@ -32,7 +32,7 @@ Find the supported regions and amd64/arm64 layer ARN in the table below for the
 
 |Supported   Regions  |Lambda layer ARN format  | Contents |
 |---------------------|-------------------------|----------|
-| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-python-<architecture\>-ver-1-25-0:1 | Contains [OpenTelemetry Python v1.25.0](https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.25.0) <br/><br/> Contains ADOT Collector v0.40.0 |
+| ap-northeast-1<br/>ap-northeast-2<br/>ap-south-1<br/>ap-southeast-1<br/>ap-southeast-2<br/>ca-central-1<br/>eu-central-1<br/>eu-north-1<br/>eu-west-1<br/>eu-west-2<br/>eu-west-3<br/>sa-east-1<br/>us-east-1<br/>us-east-2<br/>us-west-1<br/>us-west-2 | arn:aws:lambda:<region\>:901920570463:layer:aws-otel-python-<architecture\>-ver-1-29-0:1 | Contains [OpenTelemetry Python v1.29.0](https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.29.0) <br/><br/> Contains ADOT Collector v0.42.0 |
 
 ### Enable auto-instrumentation for your Lambda function
 To enable the AWS Distro for OpenTelemetry in your Lambda function, you need to add and configure the layer, and then enable tracing.