Excessive Unwanted Warning Logs

[andrewwatson]

Acknowledgements

• I have searched (https://github.com/aws/aws-sdk/issues?q=is%3Aissue) for past instances of this issue
• I have verified all of my SDK modules are up-to-date (you can perform a bulk update with go get -u github.com/aws/aws-sdk-go-v2/...)

Describe the bug

I'm running these versions of the various libraries and every time i make a call to S3 i get tons of these unstructured log messages that most emphatically do not want in my stdout / stderr

	github.com/aws/aws-sdk-go-v2 v1.36.0
	github.com/aws/aws-sdk-go-v2/config v1.29.4
	github.com/aws/aws-sdk-go-v2/feature/dynamodb/attributevalue v1.18.0
	github.com/aws/aws-sdk-go-v2/feature/dynamodb/expression v1.7.66
	github.com/aws/aws-sdk-go-v2/feature/s3/manager v1.17.57
	github.com/aws/aws-sdk-go-v2/service/dynamodb v1.39.8
	github.com/aws/aws-sdk-go-v2/service/s3 v1.75.2

SDK 2025/02/03 14:38:10 WARN Response has no supported checksum. Not validating response payload.

The documentation explicitly says By default, service clients do not produce log messages. but this seems to not be true.
How can I turn this off?

Regression Issue

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

Expected Behavior

I expect the library not to log anything by default

Current Behavior

this keeps getting piped out to my stdout/stderr

SDK 2025/02/03 14:38:10 WARN Response has no supported checksum. Not validating response payload.

Reproduction Steps

any calls to S3 to ListObjects, ListObjectVersions, PutObject etc

Possible Solution

No response

Additional Information/Context

No response

AWS Go SDK V2 Module Versions Used

	github.com/aws/aws-sdk-go-v2 v1.36.0
	github.com/aws/aws-sdk-go-v2/config v1.29.4
	github.com/aws/aws-sdk-go-v2/feature/dynamodb/attributevalue v1.18.0
	github.com/aws/aws-sdk-go-v2/feature/dynamodb/expression v1.7.66
	github.com/aws/aws-sdk-go-v2/feature/s3/manager v1.17.57
	github.com/aws/aws-sdk-go-v2/service/dynamodb v1.39.8
	github.com/aws/aws-sdk-go-v2/service/s3 v1.75.2

Compiler and Version used

% go version go version go1.23.4 darwin/arm64

Operating System and version

MacOS 15.2

[andrewwatson]

when i downgrade to 1.27.0 the issue goes away. I also tried this to override logging options and that didn't work either.

	cfg, err := config.LoadDefaultConfig(context.TODO(), config.WithRegion("us-east-1"), config.WithClientLogMode(aws.ClientLogMode(0)))
	if err != nil {
		panic(err)
	}

Maybe something like a aws.LogNone option to disable logging completely?

[andrewwatson]

ok i found this that seems relevant #2976 so I guess I just need to go into my code where i fetch things from S3 and add

func(o *s3.Options) {
		o.DisableLogOutputChecksumValidationSkipped = true
	}

[lucix-aws]

That's correct - you can disable these.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.