LlamaIndex observability on AgentCore Runtime

[seanslavichaws]

Amazon Bedrock AgentCore Samples Pull Request

Issue #532:

Concise description of the PR

Changes to AgentCore Runtime Observability example, because there was no LlamaIndex example. This follows the Strands example closely.

User experience

Before: No easy example to host a LlamaIndex agent on AgentCore Runtime with Observability enabled, which is now possible.

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?
• [ x ] 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.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[mvangara10]

Feedback shared with the contributor

[github-actions]

Latest scan for commit: cfb9d3c | Updated: 2025-10-31 00:40:17 UTC

Security Scan Results

Scan Metadata

• Project: ASH
• Scan executed: 2025-10-31T00:40:04+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	0	0	680ms	0	PASSED	MED (g)
cdk-nag	0	0	0	0	0	0	27.4s	0	PASSED	MED (g)
cfn-nag	0	0	0	0	0	0	7ms	0	PASSED	MED (g)
checkov	0	0	0	0	0	0	4.6s	0	PASSED	MED (g)
detect-secrets	0	0	0	0	0	0	651ms	0	PASSED	MED (g)
grype	0	0	0	0	0	0	30.1s	0	PASSED	MED (g)
npm-audit	0	0	0	0	0	0	179ms	0	PASSED	MED (g)
opengrep	0	0	0	0	0	0	<1ms	0	SKIPPED	MED (g)
semgrep	0	0	0	0	0	0	13.5s	0	PASSED	MED (g)
syft	0	0	0	0	0	0	2.0s	0	PASSED	MED (g)

[mvangara10]

Please remove local build = True

[seanslavichaws]

Removed local build. Should be good to merge now