New component: AWS Lambda Telemetry API Receiver

[driverpt]

The purpose and use-cases of the new component

To be able to Stream Logs and Telemetry directly from AWS Lambda API

https://docs.aws.amazon.com/lambda/latest/dg/telemetry-api.html

Example configuration for the component

receivers:
  awslambdatelemetry:
    subscription: # Optional (true | false) Default (true), this invokes the Subscribe to the Service
    port: # Optional (Integer)
    protocols:
      tcp:
      http:

Telemetry data types supported

Traces, Metrics and Logs

Is this a vendor-specific component?

• This is a vendor-specific component
• If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

No response

Sponsor (optional)

No response

Additional context

No response

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• needs: Github issue template generation code needs this to generate the corresponding labels.

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[crobert-1]

Sorry for the delay here @driverpt! Pardon my ignorance also, but would the AWS Lambda Extension Layer fit your use case here? Here's another help doc reference.

If not, can you describe why not? I don't have much experience in this area so more information would be helpful.

[driverpt]

Hello @crobert-1, this is to be used with Lambda Layer. We have our External Provider api key in a Secret in Secrets Manager. At the moment it's running on ECS w/ Environment Variable injection. We wanted to have the OTEL Collector with the same behavior in Lambda. Since Lambda does not support Secrets like ECS does.....

[crobert-1]

Just to confirm, is this a similar request to the issue you've filed against the aws-otel-collector repo? How are they different?

I don't have much experience with AWS and its components so I'm looking ways to involve others here.

[driverpt]

It's the same request.

[crobert-1]

This should be considered a vendor-specific component, right?

I'm going to remove the needs triage label based on the fact that the AWS otel team has said it as a valid request. You'll just need a sponsor. @mhausenblas Do you have any status update on your work on this (seeing it's marked as a WIP)?

Feel free to bring this to our weekly collector sig meeting if you don't get a volunteer sponsor otherwise.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.