Rename FMKB to BMKB in the managed KB sample

[shraiyya]

What

Renames the FMKB abbreviation to BMKB throughout the managed Knowledge Base sample under 01-features/03-connect-your-agent-to-anything, including the sample directory itself. Naming only — no logic, control flow, or argument
changes.

Why

BMKB is the abbreviation used elsewhere for Bedrock Managed Knowledge Bases, including the aws-samples/amazon-bedrock-samples notebook this sample's own README links to as a prerequisite (01-create-bmkb-s3.ipynb). This sample was the outlier.

What changed

Every renamed token is internal to the sample:

• the generated env file, .env.fmkb-gateway -> .env.bmkb-gateway
• the --name-prefix default and the gateway/role/target names derived from it, fmkb-sample* -> bmkb-sample*
• the runtime agent name, fmkb_gateway_agent -> bmkb_gateway_agent
• the Strands entrypoint, fmkb_gateway_strands.py -> bmkb_gateway_strands.py (contents byte-identical)
• prose and comment mentions of FMKB -> BMKB
• the directory, 04-fmkb-managed-kb -> 04-bmkb-managed-kb

No package name, AWS API identifier, or external URL was touched. A repo-wide search found no reference to the old directory path outside the sample itself, so the directory rename breaks no links.

Verification

Each file from main was taken, fmkb->bmkb and FMKB->BMKB applied, and the result compared byte-for-byte against the committed version — exact match on all 17 files, confirming no incidental edits. Python sources compile and the IAM JSON documents still parse. Sibling samples (01-code-interpreter, 02-browser,
03-web-search) and the parent README are untouched.

Note for reviewers

images/architecture.png still renders "FMKB" in its title and KB node. It is a binary asset that must be re-exported from draw.io, which was deliberately kept out of this text-only rename. Happy to add the re-exported PNG here if you would prefer it land together.

[github-actions]

Latest scan for commit: 4e82f20 | Updated: 2026-07-30 20:21:06 UTC

Security Scan Results

Scan Metadata

• Project: ASH
• Scan executed: 2026-07-30T19:48:10+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	662ms	0	PASSED	MED (g)
cdk-nag	0	0	0	0	0	0	7.2s	0	PASSED	MED (g)
cfn-nag	0	0	0	0	0	0	14ms	0	PASSED	MED (g)
checkov	0	0	0	0	0	0	5.6s	0	PASSED	MED (g)
detect-secrets	0	0	0	0	0	0	1.1s	0	PASSED	MED (g)
grype	0	0	0	0	0	0	55.8s	0	PASSED	MED (g)
npm-audit	0	0	0	0	0	0	164ms	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.5s	0	PASSED	MED (g)