[processor/resourcedetection][exporter/datadog] Supress unwanted warning logs coming from EC2 metdata provider

[matej-g]

Description:
Some users are seeing unwanted logs that are coming from the metadaproviders package, specifically from EC2 provider. This is caused by the fact that the portion of the code in AWS SDK does not respect the default logger configuration (logging is turned off by default for the SDK). To sidestep the issue, the suggested solution in this PR is to introduce simple custom logging function to supress any output from SDK.

Link to tracking Issue: #22807

Testing: Manually tested

Documentation: N/A

[bryan-aguilar]

I'm a little wary of suppressing all SDK logs. What is the impact from this bug, how noisy are these logs?

Edit: I see I misread the original issues, is logging off by default? Is there documentation you can link to so we can verify that?

[matej-g]

I'm a little wary of suppressing all SDK logs. What is the impact from this bug, how noisy are these logs?

Edit: I see I misread the original issues, is logging off by default? Is there documentation you can link to so we can verify that?

• You can take a look at LogLevelType documentation https://pkg.go.dev/github.com/aws/aws-sdk-go/aws#LogLevelType
• It's being used as a default value from here https://github.com/aws/aws-sdk-go/blob/v1.49.6/aws/defaults/defaults.go#L63, which is then used in the config for EC2 metadata service

[songy23]

LGTM, pinging code owners @dashpole @Aneurysm9

[matej-g]

This is already obsolete as it has been fixed in the upstream (https://github.com/aws/aws-sdk-go/releases/tag/v1.49.16) and will be fixed by merging the PR to update AWS dependencies - #30341. Closing this.