Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@vasireddy99 are these published in a machine readable source anywhere?

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@vasireddy99 are these published in a machine readable source anywhere?

I think the only readable source could be from here - https://github.com/aws-observability/aws-otel-lambda/pull/653/files . cause in terms of the publishing to customers we are just pasting ARNS in the website to use.

@vasireddy99 Hm, okay. You might want to consider keeping a machine readable list with all versions somewhere.

Also, I notice that this list is getting very long now. Is there a way to reduce the amount of data we need to store? I.e. could we compute the ARNs somehow instead?

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: e0f7086
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

actually, the layer is like in format -arn:aws:lambda:<region\>:901920570463:layer:aws-otel-collector-<architecture\>-ver-0-82-0:1. so the region and architecture are the fields that changes