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

Amazon.S3.AmazonS3Exception: Error making request with Error Code BadRequest and Http Status Code BadRequest. No further error information was returned by the service. #3573

Open
1 task
danchykon opened this issue Dec 10, 2024 · 4 comments
Assignees
Labels
bug This issue is a bug. closing-soon This issue will automatically close in 4 days unless further comments are made. p2 This is a standard priority issue response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. s3

Comments

@danchykon
Copy link

Describe the bug

when i upload file from local environment everything is ok, but throws an exception when i try to upload a file from an application that runs in a private kubernetes cluster

Regression Issue

  • Select this option if this issue appears to be a regression.

Expected Behavior

successful upload response or detailed error response

Current Behavior

returns BadRequest error without further information

Reproduction Steps

impossible to reproduce because error happens in private kubernetes cluster

Possible Solution

No response

Additional Information/Context

image
image
image

AWS .NET SDK and/or Package version used

AWSSDK.Extensions.NETCore.Setup 3.7.301
AWSSDK.S3 3.7.410.1
AWSSDK.SSO 3.7.400.59
AWSSDK.SSOOIDC 3.7.400.59

Targeted .NET Platform

.NET 8

Operating System and version

docker image mcr.microsoft.com/dotnet/aspnet:8.0

@danchykon danchykon added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Dec 10, 2024
@ashishdhingra ashishdhingra added s3 p2 This is a standard priority issue and removed needs-triage This issue or PR still needs to be triaged. labels Dec 10, 2024
@ashishdhingra
Copy link
Contributor

Hi @danchykon,

Good morning. Thanks for opening the issue. Please share the minimal code solution to troubleshoot the issue. Also, is the endpoint and bucket name same as your local environment as in Kubernetes? I notice that the credentials were resolved from environment variables. Could you check if the credentials configured are correct in your private Kubernetes cluster?

Thanks,
Ashish

@ashishdhingra ashishdhingra added the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Dec 10, 2024
@danchykon
Copy link
Author

Hi @danchykon,

Good morning. Thanks for opening the issue. Please share the minimal code solution to troubleshoot the issue. Also, is the endpoint and bucket name same as your local environment as in Kubernetes? I notice that the credentials were resolved from environment variables. Could you check if the credentials configured are correct in your private Kubernetes cluster?

Thanks, Ashish

Hi @ashishdhingra

  • endpoint and bucket name is same as my local env as in kubernetes
  • credentials are same as my local env as in kubernetes and of course configured correctly

image
image

@ashishdhingra
Copy link
Contributor

@danchykon Thanks for your response. The code doesn't provide much information to troubleshoot the issue. Please enable verbose logging using code below and share the verbose logs (as text):

AWSConfigs.LoggingConfig.LogTo = LoggingOptions.Console;
AWSConfigs.LoggingConfig.LogMetricsFormat = LogMetricsFormatOption.JSON;
AWSConfigs.LoggingConfig.LogResponses = ResponseLoggingOption.Always;
AWSConfigs.LoggingConfig.LogMetrics = true;

This would at least provide the response received from service.

Thanks,
Ashish

@ashishdhingra ashishdhingra added response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. and removed response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Dec 11, 2024
@ashishdhingra ashishdhingra self-assigned this Dec 17, 2024
Copy link

This issue has not received a response in 5 days. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. closing-soon This issue will automatically close in 4 days unless further comments are made. p2 This is a standard priority issue response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. s3
Projects
None yet
Development

No branches or pull requests

2 participants