[exporter/loadbalancing] AWS Cloud Map to resolve collectors backends

[andretong]

Component(s)

exporter/loadbalancing

Is your feature request related to a problem? Please describe.

Looking at the currently supported alternatives like k8s, it would be nice to add the AWS Service discovery system (CloudMap) to resolve the Collector's Backend.

This would allow users to use this exporter when there is the case of using ECS over EKS in an AWS infrastructure.

Describe the solution you'd like

• Use the Go AWS SDK in order to use the Service Discovery service to fetch the IP addresses of the Collectors, and we could also get the port.
• Attributes needed to make the requests, like namespace and serviceName will be defined as attributes in a new Resolver Config
• Implement a new Resolver (aws_cloudmap_resolver.go for instance) based on the current interface
• The implementation of the resolve method will apply the logic required to fetch and build the list by using the AWS SDK for Service Discovery.
• This will resolve the list of backends periodically (i.e. every X amount of seconds and also configurable)

The configuration will look like this:

exporters:
  loadbalancing:
    protocol:
      otlp:
        timeout: 3s
    resolver:
      awsCloudMap:
        namespace: <aws-namespace>
        serviceName: <aws-otel-col-service-name>
        port: <port-to-override-the-default-> // https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/loadbalancingexporter/loadbalancer.go#L145
        interval: <interval-in-seconds>

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• exporter/loadbalancing: @jpkrohling

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

[bryan-aguilar]

@andretong I am going to assign this to you since I see you submitted an initial PR. Please feel free to unassign yourself if needed.

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

• exporter/loadbalancing: @jpkrohling

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

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.

[jpkrohling]

Reopening, as there's a PR for this already.

[atoulme]

OK to close as complete? PR is merged.

[mx-psi]

I agree this seems fixed by #27588