AWS SSM provider for configuration

[Linaa]

Component(s)

No response

Describe the issue you're reporting

otel collector running on AWS ( ECS or K8s ) would benefit from directly reading the secrets from SSM, instead of fetching them before start up. This will greatly simplify the implementation. This is similar to the existing aws secretsmanager provider.

example configuration:

receivers:
  otlp:
    protocols:
      grpc:
      http:

processors:
  batch:
  memory_limiter:

exporters:
  otlp/provider1:
    endpoint: https://provider1.domain.com:12345
    headers:
      api-key: ${ssm:<parameter-name>}
    compression: gzip

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [otlp/provider1]
    metrics:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [otlp/provider1]

[Linaa]

@atoulme would you be able to sponser this issue?

[Linaa]

@jpkrohling would you be able to sponser this issue?

I have added #37798

[atoulme]

Sorry, probably not me as I have no working knowledge of SSM. An AWS expert is a better choice.

[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.