Closed acjay closed 1 month ago
Hi @acjay, thank you for reporting this. This is due to a bug in request compression we introduced back in May. We are looking into it to come up with a fix for it.
In the meantime, you can workaround the bug by disabling request compression through configuration, i.e., in the above code in Reproduction Steps
, change
let aws_config = aws_config::defaults(BehaviorVersion::latest()).load().await;
to
let aws_config = aws_config::defaults(BehaviorVersion::latest()).disable_request_compression(true).load().await;
Thanks! I thought I was losing my mind. Even in lieu of a fix, it would help a lot to have had a better error message, perhaps with a recommendation to disable compression.
Fix merged to main in smithy-rs
, pending to be released.
The fix was released on release-2024-09-27. Let us know if you still encounter the issue after upgrading aws-sdk-cloudwatch
to 1.49.0 or greater.
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
We're using CloudWatch metrics and we are experiencing errors with PutMetricData (via the Rust aws_sdk_cloudwatch crate) when sending metric payloads that seem to be well below the documented maximums.
Expected Behavior
The metrics to be accepted successfully.
Current Behavior
The debug error looks like the following, after what appears to be a 10 second time out:
Reproduction Steps
This program shows
PutMetricData
failing when using aMetricDatum
with 125 value/count entries and then succeeding with the same data set truncated to 100 entries.Possible Solution
No response
Additional Information/Context
No response
Version