[1.3.24] — 2026-05-02
Fixed
x-amzn-errortypeheader now emitted on every JSON-protocol error response. Real AWS sends the error type in both the body (__type) and thex-amzn-errortypeheader. boto3 falls back to the body, but Java SDK v2, Go SDK v2, and Rust SDK prefer the header — without it they surfaceSdkClientException: unknown error typeinstead of the actual code. Applied centrally inerror_response_jsonand inline in 12 services that build error bodies directly (apigateway v1/v2, opensearch, scheduler, eks, ses, backup, sqs, cloudwatch, dynamodb, tagging).- AppConfig 404 bodies now include
__type. Was{"Code": ..., "Message": ...}; generic JSON error parsers that look for__typesaw an unknown shape. Body now carries both styles. - Three previously-stateless services expose a no-op
reset()(account,waf-classic,resourcegroupstaggingapi) so/_ministack/resetno longer logs a warning per call.