Add Missing AWS Resource Detectors

[NathanielRN]

Description

NOTE: We should block on #33 before addressing this issue because the Resource Detectors should go in the same opentelemetry-sdk-extension-aws gem as the ID Generator.

We should add Resource Detectors to automatically populate the resource.* attributes of all spans in certain attributes. For example, if an app is running on EC2, users should be able to use the OpenTelemetry EC2 Resource Detector to automatically populate information about the EC2 instance they are running on.

Resource Detectors already exist in several other OTel Languages:

OTel Java:

• SDK Extension Package (IDs Generator + AWS Resource Detectors)

OTel Python

• SDK Extension Package (IDs Generator + AWS Resource Detectors)

These languages have resource detectors, but put them in separate packages:

OTel Go:

• AWS Resource Detectors Package

OTel JS:

• IDs Generator Package
• AWS Resource Detectors Package

.NET has all X-Ray necessary components in one package, but should split the propagator out eventually

OTel .NET

• SDK Extension (Resource Detectors + ID Generator + Propagator

The X-Ray team would be happy to help contribute these in the near future! 🙂

[khyatigandhi6]

Hi,
I would love to help by contributing resource detectors for AWS EC2, ECS and Lambda as part of this issue.
Let me know if can raise a PR.

[NathanielRN]

Thanks @khyatigandhi6! I'm sure I would be able to find people on the AWS to help review 🙂 However, we should block this issue and resolve #33 first. Would you be willing to take that issue on?

[khyatigandhi6]

Hey @NathanielRN, Currently I don't have much knowledge and hands-on related to X-ray ID-generators. But I will have a look at it and will definitely take up that issue, if I find something around it :)

[github-actions]

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.