Skip to content

Commit

Permalink
Merge pull request #763 from vasireddy99/lambdablog
Browse files Browse the repository at this point in the history
Add Lambda Layer Release blog post
  • Loading branch information
vasireddy99 authored Jan 7, 2025
2 parents 55d5f27 + 8a2858f commit 74d0fc4
Show file tree
Hide file tree
Showing 8 changed files with 73 additions and 10 deletions.
7 changes: 7 additions & 0 deletions src/content/BlogPosts/blogPosts.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,13 @@ description:
path: /blog

blogs:
- title: "AWS Distro for OpenTelemetry Lambda Layers are now available with ADOT Collector v0.42.0"
author: "Pavan Sai Vasireddy"
date: "06-Jan-2025"
body:
"ADOT Lambda Layers now distribute ADOT Collector v0.42.0 with new layers supporting AMD64 and ARM64 Lambda functions"
link: "/docs/ReleaseBlogs/aws-distro-for-opentelemetry-lambda-layer-v0.42.0"

- title: "AWS Distro for OpenTelemetry Collector v0.42.0 is now available"
author: "Pavan Sai Vasireddy"
date: "18-December-2024"
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
---
title: 'AWS Distro for OpenTelemetry Lambda Layers that contains ADOT Collector v0.42.0 are now available'
description:
January 2025 release announcement for ADOT Lambda layers
---

import SectionSeparator from "components/MdxSectionSeparator/sectionSeparator.jsx"

<SectionSeparator />

AWS Distro for OpenTelemetry Lambda Layers now supports AMD64 and ARM64 in the following AWS regions:

|Region | AMD64 | ARM64 |
|-------------------------|-------|-------|
|Asia Pacific (Mumbai) |||
|Asia Pacific (Singapore) |||
|Asia Pacific (Sydney) |||
|Asia Pacific (Tokyo) |||
|Asia pacific (Seoul) |||
|Canada (Central) |||
|Europe (Frankfurt) |||
|Europe (Ireland) |||
|Europe (London) |||
|Europe (Stockholm) |||
|Europe(Paris) |||
|South America (Sao Paulo)|||
|US East (N. Virginia) |||
|US East (Ohio) |||
|US West (N California) |||
|US West (Oregon) |||

<SectionSeparator />

### Release Highlights
- Added support for nodejs20.x and nodejs 22.x runtime in Nodejs lambda layer.
- The `logging` exporter has been removed upstream in favor of the `debug` exporter. This release removes the logging exporter. See [#11337](https://github.com/open-telemetry/opentelemetry-collector/issues/11337) to migrate to the debug exporter.
- 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.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.

### Download

Learn more about AWS Distro for Open Telemetry Lambda support [here](https://aws-otel.github.io/docs/getting-started/lambda). All code changes are made upstream in the respective OpenTelemetry project components. Please file an [issue](https://github.com/aws-observability/aws-otel-community/issues) if you have any questions about the features, or its components.

We also welcome you to participate in the [OpenTelemetry project](https://github.com/open-telemetry). The project was [approved for incubation](https://www.cncf.io/blog/2021/08/26/opentelemetry-becomes-a-cncf-incubating-project/) status in August 2021 by the Cloud Native Computing Foundation Technical Oversight Committee (CNCF TOC).

More blog posts about
[AWS Distro for OpenTelemetry](https://aws.amazon.com/blogs/opensource/category/management-tools/aws-distro-for-opentelemetry/) can be found on the
[AWS Open Source Blog](https://aws.amazon.com/blogs/opensource/category/management-tools/aws-distro-for-opentelemetry/).


### Author

[Pavan Sai Vasireddy](https://github.com/vasireddy99) is a SDE on the AWS Open-Source Observability team.
2 changes: 1 addition & 1 deletion src/docs/getting-started/lambda/lambda-dotnet.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion src/docs/getting-started/lambda/lambda-go.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
8 changes: 4 additions & 4 deletions src/docs/getting-started/lambda/lambda-java-auto-instr.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -142,7 +142,7 @@ receivers:
grpc:
http:
exporters:
logging:
debug:
awsxray:
prometheusremotewrite:
endpoint: <workspace_remote_write_url>
Expand All @@ -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).

Expand Down
2 changes: 1 addition & 1 deletion src/docs/getting-started/lambda/lambda-java.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
4 changes: 2 additions & 2 deletions src/docs/getting-started/lambda/lambda-js.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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.50.0](https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-aws-lambda-v0.50.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.
Expand Down
2 changes: 1 addition & 1 deletion src/docs/getting-started/lambda/lambda-python.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 74d0fc4

Please sign in to comment.