Feat/market trends agent drift detection

[akomandooru]

Amazon Bedrock AgentCore Samples Pull Request

Important

1. We strictly follow a issue-first approach, please first open an issue relating to this Pull Request.
2. Once this Pull Request is ready for review please attach review ready label to it. Only PRs with review ready will be reviewed.

Issue number:
#2055

Concise description of the PR

Changes to the Market Trends Agent sample, adding a quality drift detection
feature under drift_detection/, because the sample's evaluators already score
live traffic but nothing watches whether those scores get worse over time.
Also fixes an evaluator IAM permissions policy that had unscoped Resource: "*"
on some log actions, and a trust-policy condition that didn't cover the
runtime's own source ARN.

User experience

Before: no signal exists when the agent's live quality degrades (e.g. after a
model version update with no corresponding deploy event). Degradation is only
found via manual inspection of Evaluations dashboards or user complaints.

After: running drift_detection/scripts/deploy.py stands up a scheduled Lambda,
DynamoDB state table, one CloudWatch alarm per evaluator, and a dashboard. Each
evaluator's score stream is tracked against its own learned baseline, and an
alarm fires naming the specific evaluator that degraded and stayed degraded.
watch.py, shape_report.py, and induce_drift.py give an operator CLI visibility
into detector state and a way to demo drift without waiting for it.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• [ x] I have reviewed the contributing guidelines
• [ x] Add your name to CONTRIBUTORS.md
• [ x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Are you uploading a dataset?
• [ x] Have you documented Introduction, Architecture Diagram, Prerequisites, Usage, Sample Prompts, and Clean Up steps in your example README?
• I agree to resolve any issues created for this example in the future.
• [ x] I have performed a self-review of this change
• [ x] Changes have been tested
• [ x] Changes are documented

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

[github-actions]

Latest scan for commit: 0042bf7 | Updated: 2026-09-04 01:48:52 UTC

Security Scan Results

Scan Metadata

• Project: ASH
• Scan executed: 2026-09-04T01:42:36+00:00
• ASH version: 3.0.0

Summary

Scanner Results

The table below shows findings by scanner, with status based on severity thresholds and dependencies:

Column Explanations:

Severity Levels (S/C/H/M/L/I):

• Suppressed (S): Security findings that have been explicitly suppressed/ignored and don't affect the scanner's pass/fail status
• Critical (C): The most severe security vulnerabilities requiring immediate remediation (e.g., SQL injection, remote code execution)
• High (H): Serious security vulnerabilities that should be addressed promptly (e.g., authentication bypasses, privilege escalation)
• Medium (M): Moderate security risks that should be addressed in normal development cycles (e.g., weak encryption, input validation issues)
• Low (L): Minor security concerns with limited impact (e.g., information disclosure, weak recommendations)
• Info (I): Informational findings for awareness with minimal security risk (e.g., code quality suggestions, best practice recommendations)

Other Columns:

• Time: Duration taken by each scanner to complete its analysis
• Action: Total number of actionable findings at or above the configured severity threshold that require attention

Scanner Results:

• PASSED: Scanner found no security issues at or above the configured severity threshold - code is clean for this scanner
• FAILED: Scanner found security vulnerabilities at or above the threshold that require attention and remediation
• MISSING: Scanner could not run because required dependencies/tools are not installed or available
• SKIPPED: Scanner was intentionally disabled or excluded from this scan
• ERROR: Scanner encountered an execution error and could not complete successfully

Severity Thresholds (Thresh Column):

• CRITICAL: Only Critical severity findings cause scanner to fail
• HIGH: High and Critical severity findings cause scanner to fail
• MEDIUM (MED): Medium, High, and Critical severity findings cause scanner to fail
• LOW: Low, Medium, High, and Critical severity findings cause scanner to fail
• ALL: Any finding of any severity level causes scanner to fail

Threshold Source: Values in parentheses indicate where the threshold is configured:

• (g) = global: Set in the global_settings section of ASH configuration
• (c) = config: Set in the individual scanner configuration section
• (s) = scanner: Default threshold built into the scanner itself

Statistics calculation:

• All statistics are calculated from the final aggregated SARIF report
• Suppressed findings are counted separately and do not contribute to actionable findings
• Scanner status is determined by comparing actionable findings to the threshold

Scanner	S	C	H	M	L	I	Time	Action	Result	Thresh
bandit	0	0	0	0	1	0	1.3s	0	PASSED	MED (g)
cdk-nag	0	0	0	0	0	0	6.3s	0	PASSED	MED (g)
cfn-nag	0	0	0	0	0	0	10ms	0	PASSED	MED (g)
checkov	0	0	0	0	0	0	4.9s	0	PASSED	MED (g)
detect-secrets	0	0	0	0	0	0	1.3s	0	PASSED	MED (g)
grype	0	0	0	0	0	0	1m 7s	0	PASSED	MED (g)
npm-audit	0	0	0	0	0	0	190ms	0	PASSED	MED (g)
opengrep	0	0	0	0	0	0	<1ms	0	SKIPPED	MED (g)
semgrep	0	0	0	0	0	0	<1ms	0	MISSING	MED (g)
syft	0	0	0	0	0	0	2.0s	0	PASSED	MED (g)