Skip navigation

Model routing for agentic AI workflows on Amazon Bedrock for a US software company

IsaMar Technology Inc. helped a US software company route the AI agent workflows in its product to Anthropic Claude models on Amazon Bedrock, through the gateway it already runs, with short-lived credentials through IAM Roles Anywhere and one Amazon Bedrock Guardrails policy across every route. An e

AWS Partner: IsaMar Technology Inc. Customer: A US software company in the SMB segment Status: In production on AWS as of November 2026 AWS services: Amazon Bedrock (Anthropic Claude), Amazon Bedrock Guardrails, IAM Roles Anywhere, AWS IAM, Amazon CloudWatch, Amazon S3, AWS KMS, AWS CloudTrail, AWS Security Hub, AWS CloudFormation

About the customer

The customer is an early-stage independent software vendor (ISV) based in the United States, in the small and medium business segment. Its product runs AI agent workflows for clients in regulated industries: the agents plan multi-step work, chain model calls and call tools. Every model call those agents make goes through a gateway the customer operates outside AWS, which also serves models it hosts itself. The customer asked not to be named.

The challenge

The hardest steps in those agent workflows needed stronger reasoning than the models on the gateway offered. The customer wanted larger Anthropic Claude models as first-class routes, called through the native model API with no translation layer, so that its agents' tool definitions and tool calls pass through unchanged.

Which model served which task was set by hand. No one could show that a route earned its traffic, and a single quality score hid the failures that matter, such as omitted content or unsupported claims.

Regulated clients ask where inference runs, which identity reaches it, what is logged and whether data can stay in one geography. The customer needed accurate answers, without moving its serving or storing long-lived AWS keys on its gateway.

The solution

IsaMar Technology Inc. delivered a routing layer for the customer's agent workflows: Claude models on Amazon Bedrock as routes in the existing gateway, workload identity, one guardrail policy, an evaluation agent that sets the routing, monitoring and infrastructure as code.

A routing layer for the agents. Each step of an agent workflow, whether it plans the next action or calls a tool, goes through the gateway to the route the routing table picks for its task class. The gateway calls Amazon Bedrock in US East (N. Virginia) with Claude Haiku 4.5, Claude Sonnet 5 and Claude Opus 5, through a US cross-Region inference profile. Every call uses InvokeModel or InvokeModelWithResponseStream with the native Anthropic messages format, so the agents' tool definitions and tool-use responses pass through unchanged. Each route has its own tagged application inference profile, for per-route cost attribution.

Identity without stored keys. IAM Roles Anywhere exchanges the gateway's workload certificate, issued by the customer's own certificate authority, for short-lived credentials, and trusts only that named certificate. Each route has its own IAM role, limited to its inference profile, one guardrail and one CloudWatch namespace, with no list, read, delete or IAM management permission. The engagement's engineers use one time-limited role that requires an external ID and denies billing, user and access-key changes.

One guardrail policy on every route. One Amazon Bedrock Guardrails policy, with content filters, a prompt-attack filter on input and a sensitive-information filter, is attached inline to every Bedrock call the agents make. Outputs from self-hosted models pass through the ApplyGuardrail API before they are returned. Because wire tests showed the gateway's own guardrail settings never reached Bedrock, a small hook attaches the guardrail, the gateway will not start without it, and IAM refuses any route call that lacks it.

An evaluation agent that sets the routing. Screened request history is replayed across routes inside the customer's environment. A Claude Haiku 4.5 judge grades each output against a versioned rubric for its task class and returns its verdict through a forced, schema-checked tool call. Its scores count only after it passes a calibration gate on that rubric version, and refusals count against route health, not quality. A routing step weighs judged quality, variance, health and cost per workflow, and writes a versioned routing table with a fallback order and a reason per task class.

Data handling and operations. Request text stays in the customer's environment, and Bedrock model invocation logging is off, so no prompts or outputs are logged in AWS. Only numbers go to Amazon CloudWatch, where per-route alarms watch errors, throttles, fallbacks, refusals and guardrail interventions. AWS CloudTrail covers all Regions with log file validation, AWS Security Hub runs the AWS Foundational Security Best Practices standard, and artifacts sit in Amazon S3 under their own AWS KMS key. Traffic uses TLS 1.2 or higher with SigV4. Every AWS resource is defined in AWS CloudFormation, with a written reason for each IAM permission.

Outcomes and how they are measured

The routing layer is in production on AWS as of November 2026, and the customer's agent workflows plan and call tools through it. Measured in production:

  • Guardrail coverage: 100% of routes under one guardrail policy (target 100%).
  • Long-lived AWS keys on the gateway path: zero (target zero); credentials come only from IAM Roles Anywhere.
  • Cost per agent workflow: from $0.42 to $0.30 (target at or below $0.35), a 29% reduction.
  • Errors, fallbacks and refusals: from 12% to 4% per route (target at or below 20%).

Judged quality per task class keeps its target: the routed model scores at or above the previous route's judged quality, or within one standard deviation of it.

About IsaMar Technology Inc.

IsaMar Technology Inc. is an AWS Advanced Tier Services Partner, founded in 2025, with 53 launched AWS customer engagements (AWS Partner Central, November 2026). It delivers AWS cloud and DevOps, custom software, and CRM and ERP work for enterprises, government agencies and prime contractors nationwide. It is a WBENC-certified Women's Business Enterprise and an NMSDC-certified Minority Business Enterprise.

Customer name withheld at the customer's request. IsaMar Technology Inc. is an AWS Advanced Tier Services Partner.

Need a certified diverse partner on your next technology program?

Tell us about the contract, the scope, and your supplier diversity goals. We’ll respond with how we can deliver and how the spend can be counted.

Start a conversation Supplier diversity details