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

S3 object store always returns IMDS warnings #2460

Closed
ion-elgreco opened this issue Apr 28, 2024 · 4 comments · Fixed by #2500
Closed

S3 object store always returns IMDS warnings #2460

ion-elgreco opened this issue Apr 28, 2024 · 4 comments · Fixed by #2500
Labels
binding/rust Issues for the Rust crate bug Something isn't working

Comments

@ion-elgreco
Copy link
Collaborator

When using the S3 Object store, it will still try to use the IMDS provider by default, only when setting an environment variable AWS_EC2_METADATA_DISABLED, it's not throwing the warnings anymore.

[2024-04-24T07:55:28Z WARN  aws_config::imds::region] failed to load region from IMDS err=failed to load IMDS session token: dispatch failure: io error: error trying to connect: tcp connect error: No route to host (os error 113): tcp connect error: No route to host (os error 113): No route to host (os error 113) (FailedToLoadToken(FailedToLoadToken { source: DispatchFailure(DispatchFailure { source: ConnectorError { kind: Io, source: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 113, kind: HostUnreachable, message: "No route to host" })), connection: Unknown } }) }))
[2024-04-24T07:55:29Z WARN  aws_config::imds::region] failed to load region from IMDS err=failed to load IMDS session token: dispatch failure: timeout: error trying to connect: HTTP connect timeout occurred after 1s: HTTP connect timeout occurred after 1s: timed out (FailedToLoadToken(FailedToLoadToken { source: DispatchFailure(DispatchFailure { source: ConnectorError { kind: Timeout, source: hyper::Error(Connect, HttpTimeoutError { kind: "HTTP connect", duration: 1s }), connection: Unknown } }) }))

@mightyshazam created an issue, so we can track this

@ion-elgreco ion-elgreco added the bug Something isn't working label Apr 28, 2024
@rtyler rtyler added the binding/rust Issues for the Rust crate label May 7, 2024
@rtyler
Copy link
Member

rtyler commented May 7, 2024

@ion-elgreco I assume this is manifesting when using the S3 backend outside of the AWS environment?

@ion-elgreco
Copy link
Collaborator Author

ion-elgreco commented May 7, 2024

@ion-elgreco I assume this is manifesting when using the S3 backend outside of the AWS environment?

Yup! With custom S3 endpoints

@ion-elgreco
Copy link
Collaborator Author

ion-elgreco commented May 7, 2024

@rtyler actually, also with just aws S3. Forgot that I was seeing that when @mightyshazam and I were chatting about it

@mightyshazam
Copy link
Contributor

We were debugging it over Slack. We were both running the same code via command line and notebooks, but I wasn't seeing the error while Ion was. Ion's coworkers were also seeing it. We even accounted for potentially different environment variables, but that had no effect. I need more sample data to reproduce it.

ion-elgreco pushed a commit that referenced this issue May 15, 2024
…nd object stores (#2500)

The object store changes the keys used for creating the s3 options,
while the log store does not. The difference between the two, and their
usage together was causing some weird fallback behavior in the AWS SDK
that invoked the IMDS service despite explicitly disabling it in
multiple places. This fix handles the potentially different casing along
with passing the options unmolested. It should stop any future,
unwanted, IMDS behavior

# Description
The description of the main changes of your pull request

# Related Issue(s)
- closes #2460 
# Documentation

<!---
Share links to useful documentation
--->

---------

Co-authored-by: KyJah Keys <kyjah.keys@nextdata.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
binding/rust Issues for the Rust crate bug Something isn't working
Projects
None yet
3 participants