{"version":"2.1.228","anchor":"aws-credential-failures-say-what-went-wrong","canonical_anchor":"aws-credential-failures-say-what-went-wrong","heading":"AWS credential failures say what went wrong","tier":"notice","area":"Bedrock","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/aws-credential-failures-say-what-went-wrong","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### AWS credential failures say what went wrong\n\nAWS credential problems now come with one clear message instead of a raw SDK error.\n\n**What**\n\nWhen Bedrock or Vertex request signing cannot get AWS credentials, you now get one clear message instead of a raw SDK rejection.\n\n**Details**\n\n- The provider chain is awaited inside a try\/catch and any failure is rewrapped as a typed error with a fixed message.\n\n**Evidence**\n\n`Failed to resolve AWS credentials from the credential provider chain.`\n\n- Area: Bedrock\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}