-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use internal/aws/awsutil
for AWS session configuration in the awsproxy
#31554
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@jefchien i would like to give this a go but i am kinda confused about what ar trying to solve |
Yeah you got it. The |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
extension/awsproxy, internal/aws
Is your feature request related to a problem? Please describe.
The awsproxy session and credential configuration differs slightly from the
internal/aws/awsutil
implementation. This results in different behavior between the two particularly in the region detection. Theinternal/aws/awsutil
does not support using theAWS_DEFAULT_REGION
environment variable or ECS metadata to determine the region.Describe the solution you'd like
Consolidate the implementation for AWS session configuration to
internal/aws/awsutil
.awsutil also has a
ProxyServerTransport
function, which is currently unused.opentelemetry-collector-contrib/internal/aws/awsutil/conn.go
Line 164 in b16a03f
It has the same implementation as the one in
internal/aws/proxy
and can be reused as well.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: