Sigv4 - Add Missing STS Dependency #1101
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Current Sigv4 Exporter is missing the required dependency from AWS SDK library to allow STS AssumeRole from the DefaultCredentialsProvider.
For example, this is the error that pops up if the exporter is used in an EKS environment:
WebIdentityTokenCredentialsProvider(): To use web identity tokens, the 'sts' service module must be on the class path.
Leading to the credentials provider to default to the worker node role:
Description of changes:
Add STS as a dependency for the OtlpAws Exporters in order to allow the exporter to AssumeRole.
Testing
A sample EKS application was deployed with a custom ADOT Java Agent artifact that has the STS dependency added. I see spans appearing in the
aws/spans
log group:By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.