s3 client put_bucket_lifecycle_configuration in govcloud : S3 API MD5 error Fix

[openmarmot]

Note that if you are using s3.put_bucket_lifecycle_configuration in govcloud you will likely receive the error "Missing required header for this request: Content-MD5"

This is because the S3 GovCloud endpoints enforce this header but the Boto3 client does not provide it , possibly because MD5 is disabled on a FIPS compliant server.

The solution is to add ChecksumAlgorithm='SHA256' to your request. This should be marked as a required parameter - but I think that is a change that would have to be made by the S3 API team as the boto documentation is generated.

[tayfuryldz]

This distinction is important: Content-MD5 and ChecksumAlgorithm='SHA256' are not interchangeable request parameters from boto3's point of view. The lifecycle API model and the service's endpoint behavior determine which checksum headers are emitted, and boto3's API reference is generated from those service models.

So I would avoid marking ChecksumAlgorithm universally required in boto3 documentation solely as a workaround for a GovCloud/FIPS environment. If adding ChecksumAlgorithm='SHA256' fixes the call, that's a useful workaround, but the mismatch should be reported against the S3 service model/endpoint behavior with the exact region, botocore version, and whether FIPS mode/FIPS endpoint is enabled.

That information can distinguish a stale SDK model from an endpoint-specific requirement. A boto3-only documentation change could otherwise incorrectly describe the public API for regions/endpoints where the parameter is optional.