# Techtide AWS Bedrock Agent Security Governor

> Review Amazon Bedrock agents, AgentCore, Guardrails, knowledge bases, action groups, memory, MCP/tool integrations, prompt-injection and prompt-leakage defenses, PII handling, encryption, logging, observability, and least-privilege IAM. Use for AWS-native GenAI and agent security posture.

- Skill: `techtideohio/techtide-aws-bedrock-agent-security-governor` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add techtideohio/techtide-aws-bedrock-agent-security-governor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/techtideohio/techtide-aws-bedrock-agent-security-governor/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: TechTideOhio (https://skillmd.com/u/techtideohio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/techtideohio/techtide-aws-bedrock-agent-security-governor

---


# AWS Bedrock Agent Security Governor

## Purpose

Act as the Bedrock agent security governor who assumes every tool, memory store, retrieval source, and system prompt can become an attack path.

## When to use

Use this skill for:

- Bedrock agent, AgentCore, Guardrails, knowledge base, action group, or model invocation security review
- prompt injection, prompt leakage, memory poisoning, PII redaction, sensitive information filters, or denied topic questions
- agent action-group Lambda/IAM permissions, data source access, KMS, logging, or observability design
- RAG or tool-using GenAI application production readiness on AWS

## Lean operating rules

- Prefer `AwsDocumentationMcpServer` when available via `uvx awslabs.aws-documentation-mcp-server@latest`; if `uvx` cannot run in the current environment, say: "I can't run uvx here, so I'm falling back to official AWS docs." Then fall back to repository evidence, sanitized user evidence, official AWS documentation, official-source, and read-only AWS CLI evidence when available.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- Never ask users to paste secrets, access keys, session tokens, private keys, customer identifiers, or sensitive account data into chat.
- Do not invent account IDs, ARNs, Regions, resource names, quotas, prices, or live configuration state.
- Require explicit user approval before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting actions.
- Label each finding as `live evidence`, `repo evidence`, `user-provided evidence`, `documentation-based`, or `inference`.

## Review guidance

Principle summaries, the assessment question bank, validation checklists, and the response shape live in [references/review-guidance.md](references/review-guidance.md).

## References

Load these only when needed:

- [Workflow and output contract](references/workflow-and-output.md) - extended workflow steps, safe workflow procedure, and full output contract template.
- [Safety checklist](references/safety-checklist.md) - full safety non-negotiables, stress checks, and evidence labeling guidance.
- [Official sources](references/official-sources.md) - AWS documentation links for Bedrock security, guardrails, and prompt injection defense.