Upgrading to AWSSDK.S3 v4 breaks S3 HealthCheck

[tbright92]

Please, fill the following sections to help us fix the issue

What happened: After updating to the latest major version of AWSSDK.S3, my S3 HealthCheck is getting the following error:

System.MissingMethodException: Method not found: 'Void Amazon.S3.Model.ListObjectsRequest.set_MaxKeys(Int32)'.
   at HealthChecks.Aws.S3.S3HealthCheck.CheckHealthAsync(HealthCheckContext context, CancellationToken cancellationToken)
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
   at HealthChecks.Aws.S3.S3HealthCheck.CheckHealthAsync(HealthCheckContext context, CancellationToken cancellationToken)
   at Microsoft.Extensions.Diagnostics.HealthChecks.DefaultHealthCheckService.RunCheckAsync(HealthCheckRegistration registration, CancellationToken cancellationToken)

What you expected to happen: S3 HealthCheck is able to run successfully.

How to reproduce it (as minimally and precisely as possible): Updating to the latest version of AWSSDK.S3 and adding an S3 HealthCheck.

Source code sample:

Anything else we need to know?: I believe this is happening because v4 of AWSSDK changed the type of MaxKeys from Int32 to Nullable Int32.

Environment:

• .NET Core version: .NET 9
• Healthchecks version: 9.0.0
• Operative system: Windows
• Others:

[barryguvenkaya]

Same here

[ae-naltun]

Facing the same problem.

[pokrz26]

Hey! Just wondering if there’s an estimated timeline for when the changes in this PR might be merged? Thanks!

[bill-poole]

The DynamoDB health check produces a package downgrade build warning when upgrading to v4.0 of the .NET SDK because it references v3.7.300.7 of AWSSDK.DynamoDBv2, which requires AWSSDK.Core < 4.0.0.

Please merge and publish a new NuGet package based on AWSSDK V4 as soon as possible!

[tbright92]

It's been almost 6 months since I opened this issue, and 5 months since kharedev247 raised the PR for the fix. Is there a particular reason why the fix hasn't been merged in yet?