AWS bedrock-agentcore documentation change
Summary
Added details about traffic routing methods for A/B testing (target-based vs configuration bundles) and minor capitalization change
Security assessment
The change explains technical implementation options for A/B testing traffic routing. While A/B testing could theoretically be used for security canary deployments, there's no explicit security context, vulnerability mentions, or security feature documentation added.
Diff
diff --git a/bedrock-agentcore/latest/devguide/ab-testing.md b/bedrock-agentcore/latest/devguide/ab-testing.md index 83b530ad1..69d4df44e 100644 --- a//bedrock-agentcore/latest/devguide/ab-testing.md +++ b//bedrock-agentcore/latest/devguide/ab-testing.md @@ -13 +13 @@ A/B testing splits live production traffic between two variants and continuously -A/B testing is the validation step in the [AgentCore Optimization improvement loop](./optimization-how-it-works.html). After generating a [recommendation](./optimization-recommendations.html) and validating it with [offline batch evaluations](./dataset-evaluations.html), you run an A/B test to confirm the change improves performance on live traffic before committing to a full rollout. You can route traffic to separate AgentCore Runtimes (target-based) or deliver different configurations to the same AgentCore Runtime (configuration bundles). +A/B testing is the validation step in the [AgentCore optimization improvement loop](./optimization-how-it-works.html). After generating a [recommendation](./optimization-recommendations.html) and validating it with [offline batch evaluations](./dataset-evaluations.html), you run an A/B test to confirm the change improves performance on live traffic before committing to a full rollout. You can route traffic to separate AgentCore Runtimes (target-based) or deliver different configurations to the same AgentCore Runtime (configuration bundles).