{"version":"2.1.273","anchor":"aws-error-parsing-now-also-reads-detailserror-code","canonical_anchor":"aws-error-parsing-now-also-reads-detailserror-code","heading":"AWS error parsing now also reads details.error_code","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/aws-error-parsing-now-also-reads-detailserror-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### AWS error parsing now also reads details.error_code\n\nAWS server error parsing now also reads error codes nested under `details.error_code`\n\n**What**\n\nClaude Code's normalizer for AWS server errors now checks `details?.error_code` on the error response before falling back to the older `error_code`\/`code` fields. This means error payloads that nest their error code inside a `details` object are now correctly recognized and mapped to a known server error code.\n\n**Why**\n\nThis lets Claude Code correctly identify and handle a wider range of AWS error response shapes instead of missing the ones with a nested error code.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}