Request to include the awskinesisexporter

[jordankay13]

We have an AWS Organization with multiple accounts. Each team builds their services in their own account. In order to create a central OpenTelemetry Collector, we didn't want to deal with publicly available endpoints and manage our own Authentication and Authorization.

Instead, we have our OpenTelemetry Collector hosted in our own account (within the Organization), and we get all other accounts to ship their OpenTelemetry data to us via our Kinesis Stream. With this solution, we can manage our OpenTelemetry backend vendor's keys centrally, we can manage Sampling centrally, and we can trust the data we receive because only trusted IAM Roles can put data to our stream. This works great for EC2 and ECS applications.

However, Lambda Functions require special care, and because aws-otel-lambda does not have the awskinesisexporter, we are currently required to build our own Lambda Layer.

Describe the solution you'd like
We would like the awskinesisexporter to be included in the aws-otel-lambda build.

This was previously requested in issue 298 but was closed as a stale issue.

Describe alternatives you've considered
We currently build our own Lambda Layer, but OpenTelemetry changes so frequently that it's difficult to keep up with the updates. We also don't have Go expertise in our organization, so each update takes longer than necessary.

[github-actions]

This issue is stale because it has been open 90 days with no activity. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled

[jordankay13]

Commenting to indicate I still care about this to remove the stale label