Skip to content
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

Closed
jefchien opened this issue Mar 4, 2024 · 5 comments
Closed

Comments

@jefchien
Copy link
Contributor

jefchien commented Mar 4, 2024

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. The internal/aws/awsutil does not support using the AWS_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.

func ProxyServerTransport(logger *zap.Logger, config *AWSSessionSettings) (*http.Transport, error) {

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

@jefchien jefchien added enhancement New feature or request needs triage New item requiring triage labels Mar 4, 2024
Copy link
Contributor

github-actions bot commented Mar 4, 2024

Pinging code owners:

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

@KyriosGN0
Copy link

KyriosGN0 commented Jun 10, 2024

@jefchien i would like to give this a go but i am kinda confused about what ar trying to solve
the internal/aws/awsutill should be the "canon" implementation ?
as in the internal/aws/proxy should use awsutil?

@jefchien
Copy link
Contributor Author

Yeah you got it. The awsutil should be the source of truth for the session/credential assumption and everything else should be making calls to it including the internal/aws/proxy.

Copy link
Contributor

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:

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

@github-actions github-actions bot added the Stale label Aug 12, 2024
Copy link
Contributor

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

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants