[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-aws-aws-security":3,"mdc-oy1j0z-key":35,"related-repo-aws-aws-security":1396,"related-org-aws-aws-security":1498},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":24,"repoUrl":25,"updatedAt":26,"license":27,"forks":28,"topics":29,"repo":30,"sourceUrl":33,"mdContent":34},"aws-security","manage AWS security services and compliance","Covers AWS security services and workflows — Security Hub V2 (OCSF) findings, connectors, aggregators, automation rules, and security posture summaries; Security Hub CSPM (V1\u002FASFF) controls and compliance standards; GuardDuty threat findings; Inspector vulnerability findings; Macie sensitive data findings; Detective investigation; and Security Lake configuration and data aggregation. Applicable when questions involve security posture, Exposure findings, CSPM failed controls, threat findings, vulnerability findings, sensitive data findings, automation rules, or cross-service security configuration across AWS environments. Procedures use standard AWS CLI syntax and work with or without the AWS MCP server.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"aws","AWS (Amazon)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Faws.png",[12,16,19,22],{"name":13,"slug":14,"type":15},"Security","security","tag",{"name":17,"slug":18,"type":15},"Compliance","compliance",{"name":20,"slug":21,"type":15},"Automation","automation",{"name":23,"slug":8,"type":15},"AWS",1822,"https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws","2026-08-07T05:03:40.850004",null,157,[],{"repoUrl":25,"stars":24,"forks":28,"topics":31,"description":32},[],"Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS","https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws\u002Ftree\u002FHEAD\u002Fskills\u002Fcore-skills\u002Faws-security","---\nname: aws-security\ndescription: \"Covers AWS security services and workflows — Security Hub V2 (OCSF) findings, connectors, aggregators, automation rules, and security posture summaries; Security Hub CSPM (V1\u002FASFF) controls and compliance standards; GuardDuty threat findings; Inspector vulnerability findings; Macie sensitive data findings; Detective investigation; and Security Lake configuration and data aggregation. Applicable when questions involve security posture, Exposure findings, CSPM failed controls, threat findings, vulnerability findings, sensitive data findings, automation rules, or cross-service security configuration across AWS environments. Procedures use standard AWS CLI syntax and work with or without the AWS MCP server.\"\nversion: 1\n---\n\n# AWS Security\n\n**STOP — Do not answer from general knowledge.** Before responding to any security service question, match the user's request against the sub-skill registry below and follow its procedure. If the procedure says to load a reference file, you MUST read it before providing operational guidance. Never skip the routing step.\n\nAWS Security services provide threat detection (GuardDuty), vulnerability management (Inspector), unified security dashboard and exposure analysis (Security Hub), compliance posture management (Security Hub CSPM), sensitive data discovery (Macie), investigation (Detective), and centralized log storage (Security Lake). Each service has dedicated reference procedures for configuration review and findings\u002Finvestigation summarization.\n\nThis skill works with or without the AWS MCP server. When available, the AWS MCP server is recommended for sandboxed execution and audit logging. Procedures use standard AWS CLI syntax (`aws \u003Cservice> \u003Ccommand>`).\n\nSee `references\u002Fservices-overview.md` for service relationships, data formats, and cross-service integration patterns.\n\n## Global rules\n\n1. **Read-only APIs only.** This skill and all its references use exclusively non-mutating APIs. NEVER reference, recommend, or invoke any API that creates, modifies, deletes, enables, disables, or otherwise mutates resource state or configuration — not even in prose recommendations. See service reference files for the complete allowed API list.\n\n2. **No severity judgements on configuration state.** Present what is and is not configured factually. Do not assign severity labels, gap assessments, or editorial framing (e.g., \"critical gap\", \"security issue\") to configuration state.\n\n3. **No false-positive suppression recommendations.** Focus on helping customers understand findings. Do not recommend suppression filters, archival rules, or finding dismissal.\n\n4. **Prioritize Attack Sequences in GuardDuty.** Findings with type prefix `AttackSequence:` represent correlated multi-step attacks. Always surface these first, before severity breakdown.\n\n5. **Prioritize Exposure findings in Security Hub.** Exposure findings (attack paths, resource exposure) represent Security Hub's unique cross-service correlation. Surface these first in any findings summary.\n\n6. **Expensive operations require explicit request.** MUST NOT paginate through all member accounts by default. Per-account enumeration only executes if the user explicitly requests detailed account-level information. Use statistics\u002Fcount APIs where available (e.g., `get-coverage-statistics`).\n\n7. **Match the user's language.** Respond in the same language the user writes in.\n\n8. **Verify, don't guess.** If you cannot confirm a fact from a reference file or API output, say so.\n\n9. **Sensitive data disclosure.** When a procedure produces output that may contain sensitive information (full finding bodies, IP addresses, resource identifiers, network configurations, threat intelligence details), present a summary first. Note what sensitive data the full output contains. Display the complete raw response only when the caller explicitly requests it.\n\n## How this skill works\n\n1. **Find the sub-skill** — Match the user's request against the sub-skill registry below. Match on meaning, not exact wording. If ambiguous, ask: \"Are you checking configuration, or do you need a findings summary?\"\n\n2. **If a sub-skill matches** — read `references\u002F{sub-skill-id}.md` and follow its procedure.\n\n3. **If no sub-skill matches** — answer from the service reference files listed below. Load `references\u002Fservices-overview.md` for cross-service context, or the relevant service reference file (e.g., `references\u002Fguardduty.md`) for API scope and severity scoring questions.\n\n4. **Cross-service overview** — When the user asks about overall security posture across multiple services, start with `references\u002Fservices-overview.md`, then route to relevant sub-skills.\n\n## Sub-skill registry\n\n| ID | Name | Trigger Phrases | When to Route Here | Reference |\n|----|------|-----------------|-------------------|-----------|\n| `guardduty-configuration` | GuardDuty Config Review | \"is GuardDuty configured\", \"check detector\", \"GuardDuty features enabled\", \"runtime monitoring setup\" | User wants to verify GuardDuty deployment completeness | `references\u002Fguardduty-configuration.md` |\n| `guardduty-findings` | GuardDuty Findings Summary | \"summarize GuardDuty findings\", \"what threats\", \"GuardDuty severity breakdown\", \"attack sequences\" | User wants a findings posture snapshot | `references\u002Fguardduty-findings.md` |\n| `inspector-configuration` | Inspector Config Review | \"is Inspector scanning\", \"Inspector enabled\", \"scan types\", \"coverage gaps\" | User wants to verify Inspector deployment | `references\u002Finspector-configuration.md` |\n| `inspector-findings` | Inspector Findings Summary | \"vulnerabilities found\", \"Inspector findings\", \"CVE summary\", \"vulnerability posture\" | User wants vulnerability overview | `references\u002Finspector-findings.md` |\n| `security-hub-configuration` | Security Hub Config Review | \"Security Hub integrations\", \"aggregation configured\", \"connectors\", \"automation rules\", \"V2 automation rules\", \"OCSF automation rules\" | User wants to verify Security Hub V2 (OCSF) setup | `references\u002Fsecurity-hub-configuration.md` |\n| `security-hub-findings` | Security Hub Findings Summary | \"risk overview\", \"exposure findings\", \"attack paths\", \"OCSF findings\", \"security posture trends\" | User wants Security Hub V2 (OCSF) findings overview | `references\u002Fsecurity-hub-findings.md` |\n| `security-hub-cspm-configuration` | CSPM Config Review | \"standards enabled\", \"controls\", \"FSBP\", \"CIS\", \"PCI-DSS\", \"NIST\", \"compliance setup\", \"AI security\", \"AI best practices\", \"CSPM automation rules\", \"ASFF automation rules\" | User wants to verify compliance standards setup | `references\u002Fsecurity-hub-cspm-configuration.md` |\n| `security-hub-cspm-findings` | CSPM Compliance Summary | \"compliance posture\", \"failed controls\", \"pass rate\", \"ASFF findings\", \"third-party findings\" | User wants compliance findings overview | `references\u002Fsecurity-hub-cspm-findings.md` |\n| `macie-configuration` | Macie Config Review | \"Macie configured\", \"data discovery setup\", \"classification jobs\", \"Macie enabled\" | User wants to verify Macie deployment | `references\u002Fmacie-configuration.md` |\n| `macie-findings` | Macie Findings Summary | \"sensitive data found\", \"Macie findings\", \"data classification results\", \"PII detected\" | User wants sensitive data overview | `references\u002Fmacie-findings.md` |\n| `detective-configuration` | Detective Config Review | \"Detective configured\", \"behavior graph\", \"Detective members\", \"data sources\" | User wants to verify Detective deployment | `references\u002Fdetective-configuration.md` |\n| `detective-investigations` | Detective Investigations Summary | \"Detective investigations\", \"investigation status\", \"indicators\", \"finding groups\" | User wants investigation landscape overview | `references\u002Fdetective-investigations.md` |\n| `security-lake-configuration` | Security Lake Config Review | \"Security Lake configured\", \"log sources enabled\", \"subscribers\", \"data lake setup\" | User wants to verify Security Lake deployment | `references\u002Fsecurity-lake-configuration.md` |\n| `security-lake-sources` | Security Lake Sources Summary | \"what's flowing into Security Lake\", \"ingestion status\", \"source health\", \"data lake exceptions\" | User wants data lake health overview | `references\u002Fsecurity-lake-sources.md` |\n| `organization-policies` | Organization Policies Review | \"organization policies\", \"org policies\", \"SECURITYHUB_POLICY\", \"INSPECTOR_POLICY\", \"list-policies\", \"policy targets\", \"policy enforcement\" | User wants to review or discover AWS Organizations service policies | `references\u002Forganization-policies.md` |\n\n## Disambiguation\n\n| Keywords | Route to |\n|----------|----------|\n| \"automation rules\" (ambiguous) | Both Security Hub and Security Hub CSPM have automation rules. If customer uses Security Hub V2 (OCSF), route to Security Hub config. If customer uses Security Hub CSPM (ASFF), route to CSPM config. Ask if unclear. |\n| \"standards\", \"controls\", \"compliance\", \"FSBP\", \"CIS\", \"PCI\", \"NIST\", \"ASFF\" | Security Hub CSPM skills |\n| \"integrations\", \"risk score\", \"attack path\", \"OCSF\", \"exposure\", \"connectors\" | Security Hub skills |\n| \"threat detection\", \"GuardDuty\", \"detector\", \"runtime monitoring\", \"attack sequence\" | GuardDuty skills |\n| \"vulnerability\", \"CVE\", \"Inspector\", \"scanning\", \"code vulnerability\" | Inspector skills |\n| \"sensitive data\", \"classification\", \"Macie\", \"PII\", \"data discovery\" | Macie skills |\n| \"investigation\", \"behavior graph\", \"Detective\", \"indicators\" | Detective skills |\n| \"data lake\", \"log sources\", \"Security Lake\", \"subscribers\", \"ingestion\" | Security Lake skills |\n| \"organization policies\", \"org policies\", \"policy type\", \"list-policies --filter\" | Organization Policies (cross-service) |\n\n**Note:** If a customer is using Security Hub V2 (OCSF), they should use Security Hub automation rules (`list-automation-rules-v2`) and should NOT use Security Hub CSPM features for new rules, even though CSPM remains technically available.\n\n## Service reference\n\nLoad service reference files on demand — only when the current turn requires context about service capabilities, API scope, or severity scoring.\n\n| Reference | Content | When to Load |\n|-------|---------|-------------|\n| `references\u002Fservices-overview.md` | Cross-service relationships, data formats, membership models, admin discovery, API conventions | Cross-service questions, general security posture, \"which services should I enable\" |\n| `references\u002Fguardduty.md` | GuardDuty APIs, severity scoring, service notes | GuardDuty-specific questions about APIs or severity |\n| `references\u002Finspector.md` | Inspector APIs, severity scoring, service notes | Inspector-specific questions about APIs or severity |\n| `references\u002Fsecurity-hub.md` | Security Hub V2 (OCSF) APIs, severity scoring, service notes | Security Hub V2-specific questions about APIs or severity |\n| `references\u002Fsecurity-hub-cspm.md` | Security Hub CSPM (V1\u002FASFF) APIs, severity scoring, service notes | CSPM-specific questions about APIs or severity |\n| `references\u002Fmacie.md` | Macie APIs, severity scoring, service notes | Macie-specific questions about APIs or severity |\n| `references\u002Fdetective.md` | Detective APIs, severity scoring, service notes | Detective-specific questions about APIs or severity |\n| `references\u002Fsecurity-lake.md` | Security Lake APIs, service notes | Security Lake-specific questions about APIs |\n| `references\u002Forganization-policies.md` | Organization policies discovery pattern, policy types, Organizations APIs | Questions about org-level policy enforcement across security services |\n\n## Security considerations\n\n- **Logging and monitoring**: Verify CloudTrail is enabled for security service and Organizations API calls, CloudTrail log file validation is active, and CloudWatch metric filters or alarms exist for anomalous privileged read patterns such as unexpected volume, unusual principals, or unexpected regions.\n- **Encryption and destinations**: Verify publishing or export destinations such as S3 buckets, SNS topics, and CloudWatch Logs use KMS encryption at rest and TLS in transit. For downstream S3 or SNS destinations, verify resource policies use `aws:SourceArn` and `aws:SourceAccount` condition keys where applicable.\n- **Notification recipients**: Verify SNS topic subscriptions and other security alarm recipients are restricted to authorized security personnel, and periodically audit subscription endpoints.\n- **Credential management**: Confirm CLI execution is using temporary credentials such as IAM roles or AWS SSO. Verify third-party integration credentials, API tokens, or connector secrets are stored in AWS Secrets Manager or AWS Systems Manager Parameter Store rather than plaintext configuration files or environment variables.\n- **Security references**: Consult [AWS Security Hub best practices](https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fsecurityhub-best-practices.html), [AWS CloudTrail security best practices](https:\u002F\u002Fdocs.aws.amazon.com\u002Fawscloudtrail\u002Flatest\u002Fuserguide\u002Fbest-practices-security.html), [IAM security best practices](https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002Fbest-practices.html), and the [AWS Well-Architected Security Pillar](https:\u002F\u002Fdocs.aws.amazon.com\u002Fwellarchitected\u002Flatest\u002Fsecurity-pillar\u002F) for current service guidance.\n- **Sensitive data**: Security service outputs may contain sensitive information such as IP addresses, resource identifiers, account IDs, vulnerability details, exposure paths, and threat intelligence. Classification and handling requirements are customer-specific; do not store or share outputs in unprotected channels without verifying organizational data handling policies.\n",{"data":36,"body":38},{"name":4,"description":6,"version":37},1,{"type":39,"children":40},"root",[41,49,61,66,80,93,100,210,216,289,295,878,884,1023,1041,1047,1052,1273,1279],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","AWS Security",{"type":42,"tag":50,"props":51,"children":52},"p",{},[53,59],{"type":42,"tag":54,"props":55,"children":56},"strong",{},[57],{"type":47,"value":58},"STOP — Do not answer from general knowledge.",{"type":47,"value":60}," Before responding to any security service question, match the user's request against the sub-skill registry below and follow its procedure. If the procedure says to load a reference file, you MUST read it before providing operational guidance. Never skip the routing step.",{"type":42,"tag":50,"props":62,"children":63},{},[64],{"type":47,"value":65},"AWS Security services provide threat detection (GuardDuty), vulnerability management (Inspector), unified security dashboard and exposure analysis (Security Hub), compliance posture management (Security Hub CSPM), sensitive data discovery (Macie), investigation (Detective), and centralized log storage (Security Lake). Each service has dedicated reference procedures for configuration review and findings\u002Finvestigation summarization.",{"type":42,"tag":50,"props":67,"children":68},{},[69,71,78],{"type":47,"value":70},"This skill works with or without the AWS MCP server. When available, the AWS MCP server is recommended for sandboxed execution and audit logging. Procedures use standard AWS CLI syntax (",{"type":42,"tag":72,"props":73,"children":75},"code",{"className":74},[],[76],{"type":47,"value":77},"aws \u003Cservice> \u003Ccommand>",{"type":47,"value":79},").",{"type":42,"tag":50,"props":81,"children":82},{},[83,85,91],{"type":47,"value":84},"See ",{"type":42,"tag":72,"props":86,"children":88},{"className":87},[],[89],{"type":47,"value":90},"references\u002Fservices-overview.md",{"type":47,"value":92}," for service relationships, data formats, and cross-service integration patterns.",{"type":42,"tag":94,"props":95,"children":97},"h2",{"id":96},"global-rules",[98],{"type":47,"value":99},"Global rules",{"type":42,"tag":101,"props":102,"children":103},"ol",{},[104,115,125,135,153,163,180,190,200],{"type":42,"tag":105,"props":106,"children":107},"li",{},[108,113],{"type":42,"tag":54,"props":109,"children":110},{},[111],{"type":47,"value":112},"Read-only APIs only.",{"type":47,"value":114}," This skill and all its references use exclusively non-mutating APIs. NEVER reference, recommend, or invoke any API that creates, modifies, deletes, enables, disables, or otherwise mutates resource state or configuration — not even in prose recommendations. See service reference files for the complete allowed API list.",{"type":42,"tag":105,"props":116,"children":117},{},[118,123],{"type":42,"tag":54,"props":119,"children":120},{},[121],{"type":47,"value":122},"No severity judgements on configuration state.",{"type":47,"value":124}," Present what is and is not configured factually. Do not assign severity labels, gap assessments, or editorial framing (e.g., \"critical gap\", \"security issue\") to configuration state.",{"type":42,"tag":105,"props":126,"children":127},{},[128,133],{"type":42,"tag":54,"props":129,"children":130},{},[131],{"type":47,"value":132},"No false-positive suppression recommendations.",{"type":47,"value":134}," Focus on helping customers understand findings. Do not recommend suppression filters, archival rules, or finding dismissal.",{"type":42,"tag":105,"props":136,"children":137},{},[138,143,145,151],{"type":42,"tag":54,"props":139,"children":140},{},[141],{"type":47,"value":142},"Prioritize Attack Sequences in GuardDuty.",{"type":47,"value":144}," Findings with type prefix ",{"type":42,"tag":72,"props":146,"children":148},{"className":147},[],[149],{"type":47,"value":150},"AttackSequence:",{"type":47,"value":152}," represent correlated multi-step attacks. Always surface these first, before severity breakdown.",{"type":42,"tag":105,"props":154,"children":155},{},[156,161],{"type":42,"tag":54,"props":157,"children":158},{},[159],{"type":47,"value":160},"Prioritize Exposure findings in Security Hub.",{"type":47,"value":162}," Exposure findings (attack paths, resource exposure) represent Security Hub's unique cross-service correlation. Surface these first in any findings summary.",{"type":42,"tag":105,"props":164,"children":165},{},[166,171,173,179],{"type":42,"tag":54,"props":167,"children":168},{},[169],{"type":47,"value":170},"Expensive operations require explicit request.",{"type":47,"value":172}," MUST NOT paginate through all member accounts by default. Per-account enumeration only executes if the user explicitly requests detailed account-level information. Use statistics\u002Fcount APIs where available (e.g., ",{"type":42,"tag":72,"props":174,"children":176},{"className":175},[],[177],{"type":47,"value":178},"get-coverage-statistics",{"type":47,"value":79},{"type":42,"tag":105,"props":181,"children":182},{},[183,188],{"type":42,"tag":54,"props":184,"children":185},{},[186],{"type":47,"value":187},"Match the user's language.",{"type":47,"value":189}," Respond in the same language the user writes in.",{"type":42,"tag":105,"props":191,"children":192},{},[193,198],{"type":42,"tag":54,"props":194,"children":195},{},[196],{"type":47,"value":197},"Verify, don't guess.",{"type":47,"value":199}," If you cannot confirm a fact from a reference file or API output, say so.",{"type":42,"tag":105,"props":201,"children":202},{},[203,208],{"type":42,"tag":54,"props":204,"children":205},{},[206],{"type":47,"value":207},"Sensitive data disclosure.",{"type":47,"value":209}," When a procedure produces output that may contain sensitive information (full finding bodies, IP addresses, resource identifiers, network configurations, threat intelligence details), present a summary first. Note what sensitive data the full output contains. Display the complete raw response only when the caller explicitly requests it.",{"type":42,"tag":94,"props":211,"children":213},{"id":212},"how-this-skill-works",[214],{"type":47,"value":215},"How this skill works",{"type":42,"tag":101,"props":217,"children":218},{},[219,229,247,272],{"type":42,"tag":105,"props":220,"children":221},{},[222,227],{"type":42,"tag":54,"props":223,"children":224},{},[225],{"type":47,"value":226},"Find the sub-skill",{"type":47,"value":228}," — Match the user's request against the sub-skill registry below. Match on meaning, not exact wording. If ambiguous, ask: \"Are you checking configuration, or do you need a findings summary?\"",{"type":42,"tag":105,"props":230,"children":231},{},[232,237,239,245],{"type":42,"tag":54,"props":233,"children":234},{},[235],{"type":47,"value":236},"If a sub-skill matches",{"type":47,"value":238}," — read ",{"type":42,"tag":72,"props":240,"children":242},{"className":241},[],[243],{"type":47,"value":244},"references\u002F{sub-skill-id}.md",{"type":47,"value":246}," and follow its procedure.",{"type":42,"tag":105,"props":248,"children":249},{},[250,255,257,262,264,270],{"type":42,"tag":54,"props":251,"children":252},{},[253],{"type":47,"value":254},"If no sub-skill matches",{"type":47,"value":256}," — answer from the service reference files listed below. Load ",{"type":42,"tag":72,"props":258,"children":260},{"className":259},[],[261],{"type":47,"value":90},{"type":47,"value":263}," for cross-service context, or the relevant service reference file (e.g., ",{"type":42,"tag":72,"props":265,"children":267},{"className":266},[],[268],{"type":47,"value":269},"references\u002Fguardduty.md",{"type":47,"value":271},") for API scope and severity scoring questions.",{"type":42,"tag":105,"props":273,"children":274},{},[275,280,282,287],{"type":42,"tag":54,"props":276,"children":277},{},[278],{"type":47,"value":279},"Cross-service overview",{"type":47,"value":281}," — When the user asks about overall security posture across multiple services, start with ",{"type":42,"tag":72,"props":283,"children":285},{"className":284},[],[286],{"type":47,"value":90},{"type":47,"value":288},", then route to relevant sub-skills.",{"type":42,"tag":94,"props":290,"children":292},{"id":291},"sub-skill-registry",[293],{"type":47,"value":294},"Sub-skill registry",{"type":42,"tag":296,"props":297,"children":298},"table",{},[299,333],{"type":42,"tag":300,"props":301,"children":302},"thead",{},[303],{"type":42,"tag":304,"props":305,"children":306},"tr",{},[307,313,318,323,328],{"type":42,"tag":308,"props":309,"children":310},"th",{},[311],{"type":47,"value":312},"ID",{"type":42,"tag":308,"props":314,"children":315},{},[316],{"type":47,"value":317},"Name",{"type":42,"tag":308,"props":319,"children":320},{},[321],{"type":47,"value":322},"Trigger Phrases",{"type":42,"tag":308,"props":324,"children":325},{},[326],{"type":47,"value":327},"When to Route Here",{"type":42,"tag":308,"props":329,"children":330},{},[331],{"type":47,"value":332},"Reference",{"type":42,"tag":334,"props":335,"children":336},"tbody",{},[337,374,410,446,482,518,554,590,626,662,698,734,770,806,842],{"type":42,"tag":304,"props":338,"children":339},{},[340,350,355,360,365],{"type":42,"tag":341,"props":342,"children":343},"td",{},[344],{"type":42,"tag":72,"props":345,"children":347},{"className":346},[],[348],{"type":47,"value":349},"guardduty-configuration",{"type":42,"tag":341,"props":351,"children":352},{},[353],{"type":47,"value":354},"GuardDuty Config Review",{"type":42,"tag":341,"props":356,"children":357},{},[358],{"type":47,"value":359},"\"is GuardDuty configured\", \"check detector\", \"GuardDuty features enabled\", \"runtime monitoring setup\"",{"type":42,"tag":341,"props":361,"children":362},{},[363],{"type":47,"value":364},"User wants to verify GuardDuty deployment completeness",{"type":42,"tag":341,"props":366,"children":367},{},[368],{"type":42,"tag":72,"props":369,"children":371},{"className":370},[],[372],{"type":47,"value":373},"references\u002Fguardduty-configuration.md",{"type":42,"tag":304,"props":375,"children":376},{},[377,386,391,396,401],{"type":42,"tag":341,"props":378,"children":379},{},[380],{"type":42,"tag":72,"props":381,"children":383},{"className":382},[],[384],{"type":47,"value":385},"guardduty-findings",{"type":42,"tag":341,"props":387,"children":388},{},[389],{"type":47,"value":390},"GuardDuty Findings Summary",{"type":42,"tag":341,"props":392,"children":393},{},[394],{"type":47,"value":395},"\"summarize GuardDuty findings\", \"what threats\", \"GuardDuty severity breakdown\", \"attack sequences\"",{"type":42,"tag":341,"props":397,"children":398},{},[399],{"type":47,"value":400},"User wants a findings posture snapshot",{"type":42,"tag":341,"props":402,"children":403},{},[404],{"type":42,"tag":72,"props":405,"children":407},{"className":406},[],[408],{"type":47,"value":409},"references\u002Fguardduty-findings.md",{"type":42,"tag":304,"props":411,"children":412},{},[413,422,427,432,437],{"type":42,"tag":341,"props":414,"children":415},{},[416],{"type":42,"tag":72,"props":417,"children":419},{"className":418},[],[420],{"type":47,"value":421},"inspector-configuration",{"type":42,"tag":341,"props":423,"children":424},{},[425],{"type":47,"value":426},"Inspector Config Review",{"type":42,"tag":341,"props":428,"children":429},{},[430],{"type":47,"value":431},"\"is Inspector scanning\", \"Inspector enabled\", \"scan types\", \"coverage gaps\"",{"type":42,"tag":341,"props":433,"children":434},{},[435],{"type":47,"value":436},"User wants to verify Inspector deployment",{"type":42,"tag":341,"props":438,"children":439},{},[440],{"type":42,"tag":72,"props":441,"children":443},{"className":442},[],[444],{"type":47,"value":445},"references\u002Finspector-configuration.md",{"type":42,"tag":304,"props":447,"children":448},{},[449,458,463,468,473],{"type":42,"tag":341,"props":450,"children":451},{},[452],{"type":42,"tag":72,"props":453,"children":455},{"className":454},[],[456],{"type":47,"value":457},"inspector-findings",{"type":42,"tag":341,"props":459,"children":460},{},[461],{"type":47,"value":462},"Inspector Findings Summary",{"type":42,"tag":341,"props":464,"children":465},{},[466],{"type":47,"value":467},"\"vulnerabilities found\", \"Inspector findings\", \"CVE summary\", \"vulnerability posture\"",{"type":42,"tag":341,"props":469,"children":470},{},[471],{"type":47,"value":472},"User wants vulnerability overview",{"type":42,"tag":341,"props":474,"children":475},{},[476],{"type":42,"tag":72,"props":477,"children":479},{"className":478},[],[480],{"type":47,"value":481},"references\u002Finspector-findings.md",{"type":42,"tag":304,"props":483,"children":484},{},[485,494,499,504,509],{"type":42,"tag":341,"props":486,"children":487},{},[488],{"type":42,"tag":72,"props":489,"children":491},{"className":490},[],[492],{"type":47,"value":493},"security-hub-configuration",{"type":42,"tag":341,"props":495,"children":496},{},[497],{"type":47,"value":498},"Security Hub Config Review",{"type":42,"tag":341,"props":500,"children":501},{},[502],{"type":47,"value":503},"\"Security Hub integrations\", \"aggregation configured\", \"connectors\", \"automation rules\", \"V2 automation rules\", \"OCSF automation rules\"",{"type":42,"tag":341,"props":505,"children":506},{},[507],{"type":47,"value":508},"User wants to verify Security Hub V2 (OCSF) setup",{"type":42,"tag":341,"props":510,"children":511},{},[512],{"type":42,"tag":72,"props":513,"children":515},{"className":514},[],[516],{"type":47,"value":517},"references\u002Fsecurity-hub-configuration.md",{"type":42,"tag":304,"props":519,"children":520},{},[521,530,535,540,545],{"type":42,"tag":341,"props":522,"children":523},{},[524],{"type":42,"tag":72,"props":525,"children":527},{"className":526},[],[528],{"type":47,"value":529},"security-hub-findings",{"type":42,"tag":341,"props":531,"children":532},{},[533],{"type":47,"value":534},"Security Hub Findings Summary",{"type":42,"tag":341,"props":536,"children":537},{},[538],{"type":47,"value":539},"\"risk overview\", \"exposure findings\", \"attack paths\", \"OCSF findings\", \"security posture trends\"",{"type":42,"tag":341,"props":541,"children":542},{},[543],{"type":47,"value":544},"User wants Security Hub V2 (OCSF) findings overview",{"type":42,"tag":341,"props":546,"children":547},{},[548],{"type":42,"tag":72,"props":549,"children":551},{"className":550},[],[552],{"type":47,"value":553},"references\u002Fsecurity-hub-findings.md",{"type":42,"tag":304,"props":555,"children":556},{},[557,566,571,576,581],{"type":42,"tag":341,"props":558,"children":559},{},[560],{"type":42,"tag":72,"props":561,"children":563},{"className":562},[],[564],{"type":47,"value":565},"security-hub-cspm-configuration",{"type":42,"tag":341,"props":567,"children":568},{},[569],{"type":47,"value":570},"CSPM Config Review",{"type":42,"tag":341,"props":572,"children":573},{},[574],{"type":47,"value":575},"\"standards enabled\", \"controls\", \"FSBP\", \"CIS\", \"PCI-DSS\", \"NIST\", \"compliance setup\", \"AI security\", \"AI best practices\", \"CSPM automation rules\", \"ASFF automation rules\"",{"type":42,"tag":341,"props":577,"children":578},{},[579],{"type":47,"value":580},"User wants to verify compliance standards setup",{"type":42,"tag":341,"props":582,"children":583},{},[584],{"type":42,"tag":72,"props":585,"children":587},{"className":586},[],[588],{"type":47,"value":589},"references\u002Fsecurity-hub-cspm-configuration.md",{"type":42,"tag":304,"props":591,"children":592},{},[593,602,607,612,617],{"type":42,"tag":341,"props":594,"children":595},{},[596],{"type":42,"tag":72,"props":597,"children":599},{"className":598},[],[600],{"type":47,"value":601},"security-hub-cspm-findings",{"type":42,"tag":341,"props":603,"children":604},{},[605],{"type":47,"value":606},"CSPM Compliance Summary",{"type":42,"tag":341,"props":608,"children":609},{},[610],{"type":47,"value":611},"\"compliance posture\", \"failed controls\", \"pass rate\", \"ASFF findings\", \"third-party findings\"",{"type":42,"tag":341,"props":613,"children":614},{},[615],{"type":47,"value":616},"User wants compliance findings overview",{"type":42,"tag":341,"props":618,"children":619},{},[620],{"type":42,"tag":72,"props":621,"children":623},{"className":622},[],[624],{"type":47,"value":625},"references\u002Fsecurity-hub-cspm-findings.md",{"type":42,"tag":304,"props":627,"children":628},{},[629,638,643,648,653],{"type":42,"tag":341,"props":630,"children":631},{},[632],{"type":42,"tag":72,"props":633,"children":635},{"className":634},[],[636],{"type":47,"value":637},"macie-configuration",{"type":42,"tag":341,"props":639,"children":640},{},[641],{"type":47,"value":642},"Macie Config Review",{"type":42,"tag":341,"props":644,"children":645},{},[646],{"type":47,"value":647},"\"Macie configured\", \"data discovery setup\", \"classification jobs\", \"Macie enabled\"",{"type":42,"tag":341,"props":649,"children":650},{},[651],{"type":47,"value":652},"User wants to verify Macie deployment",{"type":42,"tag":341,"props":654,"children":655},{},[656],{"type":42,"tag":72,"props":657,"children":659},{"className":658},[],[660],{"type":47,"value":661},"references\u002Fmacie-configuration.md",{"type":42,"tag":304,"props":663,"children":664},{},[665,674,679,684,689],{"type":42,"tag":341,"props":666,"children":667},{},[668],{"type":42,"tag":72,"props":669,"children":671},{"className":670},[],[672],{"type":47,"value":673},"macie-findings",{"type":42,"tag":341,"props":675,"children":676},{},[677],{"type":47,"value":678},"Macie Findings Summary",{"type":42,"tag":341,"props":680,"children":681},{},[682],{"type":47,"value":683},"\"sensitive data found\", \"Macie findings\", \"data classification results\", \"PII detected\"",{"type":42,"tag":341,"props":685,"children":686},{},[687],{"type":47,"value":688},"User wants sensitive data overview",{"type":42,"tag":341,"props":690,"children":691},{},[692],{"type":42,"tag":72,"props":693,"children":695},{"className":694},[],[696],{"type":47,"value":697},"references\u002Fmacie-findings.md",{"type":42,"tag":304,"props":699,"children":700},{},[701,710,715,720,725],{"type":42,"tag":341,"props":702,"children":703},{},[704],{"type":42,"tag":72,"props":705,"children":707},{"className":706},[],[708],{"type":47,"value":709},"detective-configuration",{"type":42,"tag":341,"props":711,"children":712},{},[713],{"type":47,"value":714},"Detective Config Review",{"type":42,"tag":341,"props":716,"children":717},{},[718],{"type":47,"value":719},"\"Detective configured\", \"behavior graph\", \"Detective members\", \"data sources\"",{"type":42,"tag":341,"props":721,"children":722},{},[723],{"type":47,"value":724},"User wants to verify Detective deployment",{"type":42,"tag":341,"props":726,"children":727},{},[728],{"type":42,"tag":72,"props":729,"children":731},{"className":730},[],[732],{"type":47,"value":733},"references\u002Fdetective-configuration.md",{"type":42,"tag":304,"props":735,"children":736},{},[737,746,751,756,761],{"type":42,"tag":341,"props":738,"children":739},{},[740],{"type":42,"tag":72,"props":741,"children":743},{"className":742},[],[744],{"type":47,"value":745},"detective-investigations",{"type":42,"tag":341,"props":747,"children":748},{},[749],{"type":47,"value":750},"Detective Investigations Summary",{"type":42,"tag":341,"props":752,"children":753},{},[754],{"type":47,"value":755},"\"Detective investigations\", \"investigation status\", \"indicators\", \"finding groups\"",{"type":42,"tag":341,"props":757,"children":758},{},[759],{"type":47,"value":760},"User wants investigation landscape overview",{"type":42,"tag":341,"props":762,"children":763},{},[764],{"type":42,"tag":72,"props":765,"children":767},{"className":766},[],[768],{"type":47,"value":769},"references\u002Fdetective-investigations.md",{"type":42,"tag":304,"props":771,"children":772},{},[773,782,787,792,797],{"type":42,"tag":341,"props":774,"children":775},{},[776],{"type":42,"tag":72,"props":777,"children":779},{"className":778},[],[780],{"type":47,"value":781},"security-lake-configuration",{"type":42,"tag":341,"props":783,"children":784},{},[785],{"type":47,"value":786},"Security Lake Config Review",{"type":42,"tag":341,"props":788,"children":789},{},[790],{"type":47,"value":791},"\"Security Lake configured\", \"log sources enabled\", \"subscribers\", \"data lake setup\"",{"type":42,"tag":341,"props":793,"children":794},{},[795],{"type":47,"value":796},"User wants to verify Security Lake deployment",{"type":42,"tag":341,"props":798,"children":799},{},[800],{"type":42,"tag":72,"props":801,"children":803},{"className":802},[],[804],{"type":47,"value":805},"references\u002Fsecurity-lake-configuration.md",{"type":42,"tag":304,"props":807,"children":808},{},[809,818,823,828,833],{"type":42,"tag":341,"props":810,"children":811},{},[812],{"type":42,"tag":72,"props":813,"children":815},{"className":814},[],[816],{"type":47,"value":817},"security-lake-sources",{"type":42,"tag":341,"props":819,"children":820},{},[821],{"type":47,"value":822},"Security Lake Sources Summary",{"type":42,"tag":341,"props":824,"children":825},{},[826],{"type":47,"value":827},"\"what's flowing into Security Lake\", \"ingestion status\", \"source health\", \"data lake exceptions\"",{"type":42,"tag":341,"props":829,"children":830},{},[831],{"type":47,"value":832},"User wants data lake health overview",{"type":42,"tag":341,"props":834,"children":835},{},[836],{"type":42,"tag":72,"props":837,"children":839},{"className":838},[],[840],{"type":47,"value":841},"references\u002Fsecurity-lake-sources.md",{"type":42,"tag":304,"props":843,"children":844},{},[845,854,859,864,869],{"type":42,"tag":341,"props":846,"children":847},{},[848],{"type":42,"tag":72,"props":849,"children":851},{"className":850},[],[852],{"type":47,"value":853},"organization-policies",{"type":42,"tag":341,"props":855,"children":856},{},[857],{"type":47,"value":858},"Organization Policies Review",{"type":42,"tag":341,"props":860,"children":861},{},[862],{"type":47,"value":863},"\"organization policies\", \"org policies\", \"SECURITYHUB_POLICY\", \"INSPECTOR_POLICY\", \"list-policies\", \"policy targets\", \"policy enforcement\"",{"type":42,"tag":341,"props":865,"children":866},{},[867],{"type":47,"value":868},"User wants to review or discover AWS Organizations service policies",{"type":42,"tag":341,"props":870,"children":871},{},[872],{"type":42,"tag":72,"props":873,"children":875},{"className":874},[],[876],{"type":47,"value":877},"references\u002Forganization-policies.md",{"type":42,"tag":94,"props":879,"children":881},{"id":880},"disambiguation",[882],{"type":47,"value":883},"Disambiguation",{"type":42,"tag":296,"props":885,"children":886},{},[887,903],{"type":42,"tag":300,"props":888,"children":889},{},[890],{"type":42,"tag":304,"props":891,"children":892},{},[893,898],{"type":42,"tag":308,"props":894,"children":895},{},[896],{"type":47,"value":897},"Keywords",{"type":42,"tag":308,"props":899,"children":900},{},[901],{"type":47,"value":902},"Route to",{"type":42,"tag":334,"props":904,"children":905},{},[906,919,932,945,958,971,984,997,1010],{"type":42,"tag":304,"props":907,"children":908},{},[909,914],{"type":42,"tag":341,"props":910,"children":911},{},[912],{"type":47,"value":913},"\"automation rules\" (ambiguous)",{"type":42,"tag":341,"props":915,"children":916},{},[917],{"type":47,"value":918},"Both Security Hub and Security Hub CSPM have automation rules. If customer uses Security Hub V2 (OCSF), route to Security Hub config. If customer uses Security Hub CSPM (ASFF), route to CSPM config. Ask if unclear.",{"type":42,"tag":304,"props":920,"children":921},{},[922,927],{"type":42,"tag":341,"props":923,"children":924},{},[925],{"type":47,"value":926},"\"standards\", \"controls\", \"compliance\", \"FSBP\", \"CIS\", \"PCI\", \"NIST\", \"ASFF\"",{"type":42,"tag":341,"props":928,"children":929},{},[930],{"type":47,"value":931},"Security Hub CSPM skills",{"type":42,"tag":304,"props":933,"children":934},{},[935,940],{"type":42,"tag":341,"props":936,"children":937},{},[938],{"type":47,"value":939},"\"integrations\", \"risk score\", \"attack path\", \"OCSF\", \"exposure\", \"connectors\"",{"type":42,"tag":341,"props":941,"children":942},{},[943],{"type":47,"value":944},"Security Hub skills",{"type":42,"tag":304,"props":946,"children":947},{},[948,953],{"type":42,"tag":341,"props":949,"children":950},{},[951],{"type":47,"value":952},"\"threat detection\", \"GuardDuty\", \"detector\", \"runtime monitoring\", \"attack sequence\"",{"type":42,"tag":341,"props":954,"children":955},{},[956],{"type":47,"value":957},"GuardDuty skills",{"type":42,"tag":304,"props":959,"children":960},{},[961,966],{"type":42,"tag":341,"props":962,"children":963},{},[964],{"type":47,"value":965},"\"vulnerability\", \"CVE\", \"Inspector\", \"scanning\", \"code vulnerability\"",{"type":42,"tag":341,"props":967,"children":968},{},[969],{"type":47,"value":970},"Inspector skills",{"type":42,"tag":304,"props":972,"children":973},{},[974,979],{"type":42,"tag":341,"props":975,"children":976},{},[977],{"type":47,"value":978},"\"sensitive data\", \"classification\", \"Macie\", \"PII\", \"data discovery\"",{"type":42,"tag":341,"props":980,"children":981},{},[982],{"type":47,"value":983},"Macie skills",{"type":42,"tag":304,"props":985,"children":986},{},[987,992],{"type":42,"tag":341,"props":988,"children":989},{},[990],{"type":47,"value":991},"\"investigation\", \"behavior graph\", \"Detective\", \"indicators\"",{"type":42,"tag":341,"props":993,"children":994},{},[995],{"type":47,"value":996},"Detective skills",{"type":42,"tag":304,"props":998,"children":999},{},[1000,1005],{"type":42,"tag":341,"props":1001,"children":1002},{},[1003],{"type":47,"value":1004},"\"data lake\", \"log sources\", \"Security Lake\", \"subscribers\", \"ingestion\"",{"type":42,"tag":341,"props":1006,"children":1007},{},[1008],{"type":47,"value":1009},"Security Lake skills",{"type":42,"tag":304,"props":1011,"children":1012},{},[1013,1018],{"type":42,"tag":341,"props":1014,"children":1015},{},[1016],{"type":47,"value":1017},"\"organization policies\", \"org policies\", \"policy type\", \"list-policies --filter\"",{"type":42,"tag":341,"props":1019,"children":1020},{},[1021],{"type":47,"value":1022},"Organization Policies (cross-service)",{"type":42,"tag":50,"props":1024,"children":1025},{},[1026,1031,1033,1039],{"type":42,"tag":54,"props":1027,"children":1028},{},[1029],{"type":47,"value":1030},"Note:",{"type":47,"value":1032}," If a customer is using Security Hub V2 (OCSF), they should use Security Hub automation rules (",{"type":42,"tag":72,"props":1034,"children":1036},{"className":1035},[],[1037],{"type":47,"value":1038},"list-automation-rules-v2",{"type":47,"value":1040},") and should NOT use Security Hub CSPM features for new rules, even though CSPM remains technically available.",{"type":42,"tag":94,"props":1042,"children":1044},{"id":1043},"service-reference",[1045],{"type":47,"value":1046},"Service reference",{"type":42,"tag":50,"props":1048,"children":1049},{},[1050],{"type":47,"value":1051},"Load service reference files on demand — only when the current turn requires context about service capabilities, API scope, or severity scoring.",{"type":42,"tag":296,"props":1053,"children":1054},{},[1055,1075],{"type":42,"tag":300,"props":1056,"children":1057},{},[1058],{"type":42,"tag":304,"props":1059,"children":1060},{},[1061,1065,1070],{"type":42,"tag":308,"props":1062,"children":1063},{},[1064],{"type":47,"value":332},{"type":42,"tag":308,"props":1066,"children":1067},{},[1068],{"type":47,"value":1069},"Content",{"type":42,"tag":308,"props":1071,"children":1072},{},[1073],{"type":47,"value":1074},"When to Load",{"type":42,"tag":334,"props":1076,"children":1077},{},[1078,1099,1120,1142,1164,1186,1208,1230,1252],{"type":42,"tag":304,"props":1079,"children":1080},{},[1081,1089,1094],{"type":42,"tag":341,"props":1082,"children":1083},{},[1084],{"type":42,"tag":72,"props":1085,"children":1087},{"className":1086},[],[1088],{"type":47,"value":90},{"type":42,"tag":341,"props":1090,"children":1091},{},[1092],{"type":47,"value":1093},"Cross-service relationships, data formats, membership models, admin discovery, API conventions",{"type":42,"tag":341,"props":1095,"children":1096},{},[1097],{"type":47,"value":1098},"Cross-service questions, general security posture, \"which services should I enable\"",{"type":42,"tag":304,"props":1100,"children":1101},{},[1102,1110,1115],{"type":42,"tag":341,"props":1103,"children":1104},{},[1105],{"type":42,"tag":72,"props":1106,"children":1108},{"className":1107},[],[1109],{"type":47,"value":269},{"type":42,"tag":341,"props":1111,"children":1112},{},[1113],{"type":47,"value":1114},"GuardDuty APIs, severity scoring, service notes",{"type":42,"tag":341,"props":1116,"children":1117},{},[1118],{"type":47,"value":1119},"GuardDuty-specific questions about APIs or severity",{"type":42,"tag":304,"props":1121,"children":1122},{},[1123,1132,1137],{"type":42,"tag":341,"props":1124,"children":1125},{},[1126],{"type":42,"tag":72,"props":1127,"children":1129},{"className":1128},[],[1130],{"type":47,"value":1131},"references\u002Finspector.md",{"type":42,"tag":341,"props":1133,"children":1134},{},[1135],{"type":47,"value":1136},"Inspector APIs, severity scoring, service notes",{"type":42,"tag":341,"props":1138,"children":1139},{},[1140],{"type":47,"value":1141},"Inspector-specific questions about APIs or severity",{"type":42,"tag":304,"props":1143,"children":1144},{},[1145,1154,1159],{"type":42,"tag":341,"props":1146,"children":1147},{},[1148],{"type":42,"tag":72,"props":1149,"children":1151},{"className":1150},[],[1152],{"type":47,"value":1153},"references\u002Fsecurity-hub.md",{"type":42,"tag":341,"props":1155,"children":1156},{},[1157],{"type":47,"value":1158},"Security Hub V2 (OCSF) APIs, severity scoring, service notes",{"type":42,"tag":341,"props":1160,"children":1161},{},[1162],{"type":47,"value":1163},"Security Hub V2-specific questions about APIs or severity",{"type":42,"tag":304,"props":1165,"children":1166},{},[1167,1176,1181],{"type":42,"tag":341,"props":1168,"children":1169},{},[1170],{"type":42,"tag":72,"props":1171,"children":1173},{"className":1172},[],[1174],{"type":47,"value":1175},"references\u002Fsecurity-hub-cspm.md",{"type":42,"tag":341,"props":1177,"children":1178},{},[1179],{"type":47,"value":1180},"Security Hub CSPM (V1\u002FASFF) APIs, severity scoring, service notes",{"type":42,"tag":341,"props":1182,"children":1183},{},[1184],{"type":47,"value":1185},"CSPM-specific questions about APIs or severity",{"type":42,"tag":304,"props":1187,"children":1188},{},[1189,1198,1203],{"type":42,"tag":341,"props":1190,"children":1191},{},[1192],{"type":42,"tag":72,"props":1193,"children":1195},{"className":1194},[],[1196],{"type":47,"value":1197},"references\u002Fmacie.md",{"type":42,"tag":341,"props":1199,"children":1200},{},[1201],{"type":47,"value":1202},"Macie APIs, severity scoring, service notes",{"type":42,"tag":341,"props":1204,"children":1205},{},[1206],{"type":47,"value":1207},"Macie-specific questions about APIs or severity",{"type":42,"tag":304,"props":1209,"children":1210},{},[1211,1220,1225],{"type":42,"tag":341,"props":1212,"children":1213},{},[1214],{"type":42,"tag":72,"props":1215,"children":1217},{"className":1216},[],[1218],{"type":47,"value":1219},"references\u002Fdetective.md",{"type":42,"tag":341,"props":1221,"children":1222},{},[1223],{"type":47,"value":1224},"Detective APIs, severity scoring, service notes",{"type":42,"tag":341,"props":1226,"children":1227},{},[1228],{"type":47,"value":1229},"Detective-specific questions about APIs or severity",{"type":42,"tag":304,"props":1231,"children":1232},{},[1233,1242,1247],{"type":42,"tag":341,"props":1234,"children":1235},{},[1236],{"type":42,"tag":72,"props":1237,"children":1239},{"className":1238},[],[1240],{"type":47,"value":1241},"references\u002Fsecurity-lake.md",{"type":42,"tag":341,"props":1243,"children":1244},{},[1245],{"type":47,"value":1246},"Security Lake APIs, service notes",{"type":42,"tag":341,"props":1248,"children":1249},{},[1250],{"type":47,"value":1251},"Security Lake-specific questions about APIs",{"type":42,"tag":304,"props":1253,"children":1254},{},[1255,1263,1268],{"type":42,"tag":341,"props":1256,"children":1257},{},[1258],{"type":42,"tag":72,"props":1259,"children":1261},{"className":1260},[],[1262],{"type":47,"value":877},{"type":42,"tag":341,"props":1264,"children":1265},{},[1266],{"type":47,"value":1267},"Organization policies discovery pattern, policy types, Organizations APIs",{"type":42,"tag":341,"props":1269,"children":1270},{},[1271],{"type":47,"value":1272},"Questions about org-level policy enforcement across security services",{"type":42,"tag":94,"props":1274,"children":1276},{"id":1275},"security-considerations",[1277],{"type":47,"value":1278},"Security considerations",{"type":42,"tag":1280,"props":1281,"children":1282},"ul",{},[1283,1293,1319,1329,1339,1386],{"type":42,"tag":105,"props":1284,"children":1285},{},[1286,1291],{"type":42,"tag":54,"props":1287,"children":1288},{},[1289],{"type":47,"value":1290},"Logging and monitoring",{"type":47,"value":1292},": Verify CloudTrail is enabled for security service and Organizations API calls, CloudTrail log file validation is active, and CloudWatch metric filters or alarms exist for anomalous privileged read patterns such as unexpected volume, unusual principals, or unexpected regions.",{"type":42,"tag":105,"props":1294,"children":1295},{},[1296,1301,1303,1309,1311,1317],{"type":42,"tag":54,"props":1297,"children":1298},{},[1299],{"type":47,"value":1300},"Encryption and destinations",{"type":47,"value":1302},": Verify publishing or export destinations such as S3 buckets, SNS topics, and CloudWatch Logs use KMS encryption at rest and TLS in transit. For downstream S3 or SNS destinations, verify resource policies use ",{"type":42,"tag":72,"props":1304,"children":1306},{"className":1305},[],[1307],{"type":47,"value":1308},"aws:SourceArn",{"type":47,"value":1310}," and ",{"type":42,"tag":72,"props":1312,"children":1314},{"className":1313},[],[1315],{"type":47,"value":1316},"aws:SourceAccount",{"type":47,"value":1318}," condition keys where applicable.",{"type":42,"tag":105,"props":1320,"children":1321},{},[1322,1327],{"type":42,"tag":54,"props":1323,"children":1324},{},[1325],{"type":47,"value":1326},"Notification recipients",{"type":47,"value":1328},": Verify SNS topic subscriptions and other security alarm recipients are restricted to authorized security personnel, and periodically audit subscription endpoints.",{"type":42,"tag":105,"props":1330,"children":1331},{},[1332,1337],{"type":42,"tag":54,"props":1333,"children":1334},{},[1335],{"type":47,"value":1336},"Credential management",{"type":47,"value":1338},": Confirm CLI execution is using temporary credentials such as IAM roles or AWS SSO. Verify third-party integration credentials, API tokens, or connector secrets are stored in AWS Secrets Manager or AWS Systems Manager Parameter Store rather than plaintext configuration files or environment variables.",{"type":42,"tag":105,"props":1340,"children":1341},{},[1342,1347,1349,1358,1360,1367,1368,1375,1377,1384],{"type":42,"tag":54,"props":1343,"children":1344},{},[1345],{"type":47,"value":1346},"Security references",{"type":47,"value":1348},": Consult ",{"type":42,"tag":1350,"props":1351,"children":1355},"a",{"href":1352,"rel":1353},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fsecurityhub\u002Flatest\u002Fuserguide\u002Fsecurityhub-best-practices.html",[1354],"nofollow",[1356],{"type":47,"value":1357},"AWS Security Hub best practices",{"type":47,"value":1359},", ",{"type":42,"tag":1350,"props":1361,"children":1364},{"href":1362,"rel":1363},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fawscloudtrail\u002Flatest\u002Fuserguide\u002Fbest-practices-security.html",[1354],[1365],{"type":47,"value":1366},"AWS CloudTrail security best practices",{"type":47,"value":1359},{"type":42,"tag":1350,"props":1369,"children":1372},{"href":1370,"rel":1371},"https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002Fbest-practices.html",[1354],[1373],{"type":47,"value":1374},"IAM security best practices",{"type":47,"value":1376},", and the ",{"type":42,"tag":1350,"props":1378,"children":1381},{"href":1379,"rel":1380},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fwellarchitected\u002Flatest\u002Fsecurity-pillar\u002F",[1354],[1382],{"type":47,"value":1383},"AWS Well-Architected Security Pillar",{"type":47,"value":1385}," for current service guidance.",{"type":42,"tag":105,"props":1387,"children":1388},{},[1389,1394],{"type":42,"tag":54,"props":1390,"children":1391},{},[1392],{"type":47,"value":1393},"Sensitive data",{"type":47,"value":1395},": Security service outputs may contain sensitive information such as IP addresses, resource identifiers, account IDs, vulnerability details, exposure paths, and threat intelligence. Classification and handling requirements are customer-specific; do not store or share outputs in unprotected channels without verifying organizational data handling policies.",{"items":1397,"total":1497},[1398,1413,1428,1443,1458,1468,1481],{"slug":1399,"name":1399,"fn":1400,"description":1401,"org":1402,"tags":1403,"stars":24,"repoUrl":25,"updatedAt":1412},"agents-build","add capabilities to existing agent projects","Use to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal. Triggers: \"add memory\", \"remember across sessions\", \"call agent from app\", \"invoke agent from code\", \"agent auth\", \"streaming\", \"VPC\", \"VPC connectivity\", \"can't reach from VPC\", \"multi-agent\", \"A2A\", \"A2A auth\", \"orchestrator not delegating\", \"specialist not called\", \"migrate Bedrock Agent\", \"migration issue\", \"change model\", \"browser tool\", \"code interpreter\", \"delete agent\", \"tear down\", \"agentcore remove\", \"cross-account memory\", \"add payments capability to my agent\", \"wire payments plugin\", \"payments middleware for my agent\", \"integrate x402 payments with the agent I'm building\", \"enable my agent project with x402 payments\". External APIs via Gateway: use agents-connect. New project: use agents-get-started. CLI\u002Fdev-server errors: use agents-debug. Runtime x402 payments: use agents-pay. Migration-specific Strands vs LangGraph routes here.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1404,1407,1408,1409],{"name":1405,"slug":1406,"type":15},"Agents","agents",{"name":20,"slug":21,"type":15},{"name":23,"slug":8,"type":15},{"name":1410,"slug":1411,"type":15},"Engineering","engineering","2026-08-07T04:38:08.981896",{"slug":1414,"name":1414,"fn":1415,"description":1416,"org":1417,"tags":1418,"stars":24,"repoUrl":25,"updatedAt":1427},"agents-connect","connect agents to external services","Use when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies. Handles gateway setup, target types, outbound auth (OAuth, API key, IAM), credentials, and Cedar policy authoring. Triggers on: \"connect to API\", \"add gateway\", \"connect to MCP server\", \"Lambda tools\", \"OpenAPI\", \"gateway target\", \"Cedar policy\", \"restrict tools\", \"policy engine\", \"gateway auth error\", \"store API key\", \"outbound credential\", \"env var API key\", \"API key None after deploy\", \"credential not available after deploy\", \"should this be a gateway target\", \"give my agent tools\", \"add tools to agent\". Not for inbound auth (who can call your agent) — use agents-harden. Not for debugging agent behavior — use agents-debug. Not for VPC networking errors (agent can't reach APIs due to VPC) — use agents-build. Not for creating or hosting a new MCP server project — use agents-get-started.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1419,1420,1423,1426],{"name":1405,"slug":1406,"type":15},{"name":1421,"slug":1422,"type":15},"API Development","api-development",{"name":1424,"slug":1425,"type":15},"Authentication","authentication",{"name":23,"slug":8,"type":15},"2026-07-16T06:00:38.866147",{"slug":1429,"name":1429,"fn":1430,"description":1431,"org":1432,"tags":1433,"stars":24,"repoUrl":25,"updatedAt":1442},"agents-debug","debug agent and environment issues","Use when your agent or environment is broken — wrong answers, errors, timeouts, tool failures, or CLI issues. Reads traces and logs to diagnose root causes. Also checks prerequisites when the CLI itself isn't working. Triggers on: \"agent not working\", \"wrong answer\", \"agent error\", \"tool call failing\", \"debug agent\", \"check logs\", \"read traces\", \"broken\", \"500 error\", \"424 error\", \"model access denied\", \"command not found\", \"stuck in DELETING\", \"maxVms exceeded\", \"cold start diagnosis\", \"cold start slow\", \"agentcore create error\", \"create failed\", \"exit code 7\", \"connection refused local dev\". Not for deploy failures — use agents-deploy. Not for performance tuning without errors — use agents-optimize. Not for VPC configuration — use agents-build. Not for observability setup or missing logs — use agents-optimize.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1434,1435,1436,1439],{"name":1405,"slug":1406,"type":15},{"name":23,"slug":8,"type":15},{"name":1437,"slug":1438,"type":15},"Debugging","debugging",{"name":1440,"slug":1441,"type":15},"Observability","observability","2026-07-16T06:00:44.679093",{"slug":1444,"name":1444,"fn":1445,"description":1446,"org":1447,"tags":1448,"stars":24,"repoUrl":25,"updatedAt":1457},"agents-deploy","deploy AI agents to AWS","Use when deploying your agent to AWS, or when a deploy has failed. Handles pre-flight validation, CDK\u002FIAM\u002Fquota error diagnosis, version management, rollback, and canary deployments. Triggers on: \"deploy my agent\", \"agentcore deploy\", \"deploy failed\", \"CDK error\", \"rollback\", \"canary deploy\", \"pin version\", \"redeploy\", \"deploy stuck\". Not for production hardening — use agents-harden. Not for adding capabilities before deploy — use agents-build or agents-connect. Not for VPC configuration errors — use agents-build.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1449,1450,1451,1454],{"name":1405,"slug":1406,"type":15},{"name":23,"slug":8,"type":15},{"name":1452,"slug":1453,"type":15},"CI\u002FCD","ci-cd",{"name":1455,"slug":1456,"type":15},"Deployment","deployment","2026-07-12T08:42:55.059577",{"slug":1459,"name":1459,"fn":1460,"description":1461,"org":1462,"tags":1463,"stars":24,"repoUrl":25,"updatedAt":1467},"agents-get-started","scaffold and deploy new agent projects","Use when a developer wants to create a new agent project or get started with AgentCore. Handles framework selection, project scaffolding, first deploy, and first invocation. Triggers on: \"build an agent\", \"create an agent\", \"get started\", \"new project\", \"agentcore create\", \"which framework\", \"Strands vs LangGraph\", \"hello world agent\", \"first agent\", \"create MCP server\", \"host MCP server\", \"agentcore dev\", \"dev server\", \"what port\", \"local development\". Not for adding capabilities to existing projects — use agents-build or agents-connect. Strands vs LangGraph in a migration context routes to agents-build, not here. Connecting to an existing MCP server routes to agents-connect, not here.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1464,1465,1466],{"name":1405,"slug":1406,"type":15},{"name":23,"slug":8,"type":15},{"name":1455,"slug":1456,"type":15},"2026-07-12T08:42:51.963247",{"slug":1469,"name":1469,"fn":1470,"description":1471,"org":1472,"tags":1473,"stars":24,"repoUrl":25,"updatedAt":1480},"agents-harden","harden agents for production","Use when preparing your agent for production — IAM scoping, inbound auth (JWT, SigV4), secrets management, cold start optimization, session lifecycle, rate limiting, input validation, and quota guidance. Triggers on: \"production checklist\", \"harden agent\", \"production ready\", \"secure agent\", \"inbound auth\", \"going live\", \"cold start optimization\", \"session lifecycle\", \"StopRuntimeSession\", \"quota\", \"throttling\", \"maxVms\", \"rate limit\", \"security audit of outbound API calls\", \"gateway target audit for production\", \"restrict who can call\", \"lock down endpoint\", \"only our app can call\". Not for Cedar tool-restriction policies — use agents-connect. Not for quality measurement — use agents-optimize. Not for outbound credential storage or API key wiring — use agents-connect. Not for A2A agent-to-agent auth — use agents-build. Cold start observation and diagnosis (not optimization) routes to agents-debug.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1474,1475,1476,1479],{"name":1405,"slug":1406,"type":15},{"name":23,"slug":8,"type":15},{"name":1477,"slug":1478,"type":15},"Best Practices","best-practices",{"name":13,"slug":14,"type":15},"2026-07-16T06:00:42.174705",{"slug":1482,"name":1482,"fn":1483,"description":1484,"org":1485,"tags":1486,"stars":24,"repoUrl":25,"updatedAt":1496},"agents-optimize","optimize agent quality and performance","Use when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI\u002FCD quality gates, observability, or cost optimization. Triggers on: \"evaluate my agent\", \"add evaluator\", \"measure quality\", \"quality gate\", \"run evals\", \"agent too slow\", \"why is it slow\", \"reduce latency\", \"set up observability\", \"CloudWatch dashboard\", \"how much does my agent cost\", \"cost optimization\", \"logs not showing up\", \"logs missing\", \"spans not found\", \"eval failing\", \"eval error\", \"dev traces\", \"local traces\", \"agentcore dev traces\", \"traces to CloudWatch\". Not for debugging errors or crashes — use agents-debug. Slow but correct routes here; broken routes to debug.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1487,1488,1489,1492,1493],{"name":1405,"slug":1406,"type":15},{"name":23,"slug":8,"type":15},{"name":1490,"slug":1491,"type":15},"Evals","evals",{"name":1440,"slug":1441,"type":15},{"name":1494,"slug":1495,"type":15},"Performance","performance","2026-07-12T08:42:56.488105",117,{"items":1499,"total":1620},[1500,1507,1514,1521,1528,1534,1541,1549,1563,1580,1593,1605],{"slug":1399,"name":1399,"fn":1400,"description":1401,"org":1501,"tags":1502,"stars":24,"repoUrl":25,"updatedAt":1412},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1503,1504,1505,1506],{"name":1405,"slug":1406,"type":15},{"name":20,"slug":21,"type":15},{"name":23,"slug":8,"type":15},{"name":1410,"slug":1411,"type":15},{"slug":1414,"name":1414,"fn":1415,"description":1416,"org":1508,"tags":1509,"stars":24,"repoUrl":25,"updatedAt":1427},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1510,1511,1512,1513],{"name":1405,"slug":1406,"type":15},{"name":1421,"slug":1422,"type":15},{"name":1424,"slug":1425,"type":15},{"name":23,"slug":8,"type":15},{"slug":1429,"name":1429,"fn":1430,"description":1431,"org":1515,"tags":1516,"stars":24,"repoUrl":25,"updatedAt":1442},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1517,1518,1519,1520],{"name":1405,"slug":1406,"type":15},{"name":23,"slug":8,"type":15},{"name":1437,"slug":1438,"type":15},{"name":1440,"slug":1441,"type":15},{"slug":1444,"name":1444,"fn":1445,"description":1446,"org":1522,"tags":1523,"stars":24,"repoUrl":25,"updatedAt":1457},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1524,1525,1526,1527],{"name":1405,"slug":1406,"type":15},{"name":23,"slug":8,"type":15},{"name":1452,"slug":1453,"type":15},{"name":1455,"slug":1456,"type":15},{"slug":1459,"name":1459,"fn":1460,"description":1461,"org":1529,"tags":1530,"stars":24,"repoUrl":25,"updatedAt":1467},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1531,1532,1533],{"name":1405,"slug":1406,"type":15},{"name":23,"slug":8,"type":15},{"name":1455,"slug":1456,"type":15},{"slug":1469,"name":1469,"fn":1470,"description":1471,"org":1535,"tags":1536,"stars":24,"repoUrl":25,"updatedAt":1480},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1537,1538,1539,1540],{"name":1405,"slug":1406,"type":15},{"name":23,"slug":8,"type":15},{"name":1477,"slug":1478,"type":15},{"name":13,"slug":14,"type":15},{"slug":1482,"name":1482,"fn":1483,"description":1484,"org":1542,"tags":1543,"stars":24,"repoUrl":25,"updatedAt":1496},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1544,1545,1546,1547,1548],{"name":1405,"slug":1406,"type":15},{"name":23,"slug":8,"type":15},{"name":1490,"slug":1491,"type":15},{"name":1440,"slug":1441,"type":15},{"name":1494,"slug":1495,"type":15},{"slug":1550,"name":1550,"fn":1551,"description":1552,"org":1553,"tags":1554,"stars":24,"repoUrl":25,"updatedAt":1562},"agents-pay","handle x402 payments for agent tasks","Use when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits. Covers payment setup, policy, session budgets, and troubleshooting. Triggers on: \"my agent hit a 402 while calling an API\", \"a tool call returned 402 Payment Required\", \"my agent needs to pay for x402-protected content\", \"let the agent pay for content, capped at $5 per session\", \"set a spend limit for the agent\", \"ProcessPayment failed\", or \"why did my agent refuse to pay\". Not for BUILDING payment capability for end users, including wallets and framework middleware; use agents-build and references\u002Fpayments.md. For non-paid APIs via Gateway use agents-connect. For inbound auth use agents-harden. For project scaffolding use agents-get-started.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1555,1556,1557,1560],{"name":1405,"slug":1406,"type":15},{"name":20,"slug":21,"type":15},{"name":1558,"slug":1559,"type":15},"Payments","payments",{"name":1561,"slug":1561,"type":15},"x402","2026-08-07T05:03:33.377867",{"slug":1564,"name":1564,"fn":1565,"description":1566,"org":1567,"tags":1568,"stars":24,"repoUrl":25,"updatedAt":1579},"amazon-aurora-mysql","manage Amazon Aurora MySQL clusters","Amazon Aurora MySQL — creates, modifies, and advises on Aurora MySQL clusters specifically (MySQL-compatible engine, Aurora serverless, parallel query). Trigger for Aurora MySQL cluster operations, ACU sizing, I\u002FO-Optimized storage, commitment pricing, or MySQL upgrade planning. Aurora MySQL uses full (VPC-based) configuration — express configuration is PostgreSQL-only. For Aurora PostgreSQL, use amazon-aurora-postgresql instead. Contains safety guardrails and response templates that override defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1569,1570,1573,1576],{"name":23,"slug":8,"type":15},{"name":1571,"slug":1572,"type":15},"Database","database",{"name":1574,"slug":1575,"type":15},"MySQL","mysql",{"name":1577,"slug":1578,"type":15},"Serverless","serverless","2026-07-12T08:43:13.27939",{"slug":1581,"name":1581,"fn":1582,"description":1583,"org":1584,"tags":1585,"stars":24,"repoUrl":25,"updatedAt":1592},"amazon-aurora-postgresql","configure Amazon Aurora PostgreSQL clusters","Amazon Aurora PostgreSQL — creates, modifies, and advises on Aurora PostgreSQL clusters specifically (PostgreSQL-compatible engine, Aurora serverless, express configuration, pgvector, Babelfish). Trigger for Aurora PostgreSQL cluster operations, express-configuration quick-start, ACU sizing, I\u002FO-Optimized storage, commitment pricing, or PostgreSQL upgrade planning. For Aurora MySQL, use amazon-aurora-mysql instead. Contains safety guardrails, express-first routing, and response templates that override defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1586,1587,1588,1591],{"name":23,"slug":8,"type":15},{"name":1571,"slug":1572,"type":15},{"name":1589,"slug":1590,"type":15},"PostgreSQL","postgresql",{"name":1577,"slug":1578,"type":15},"2026-07-16T06:00:34.789624",{"slug":1594,"name":1594,"fn":1595,"description":1596,"org":1597,"tags":1598,"stars":24,"repoUrl":25,"updatedAt":1604},"amazon-bedrock","build generative AI apps with Amazon Bedrock","Builds generative AI applications on Amazon Bedrock. Covers model invocation (Converse API, InvokeModel), RAG with Knowledge Bases, Bedrock Agents, Guardrails, and AgentCore (including the Harness managed agent loop). Use when invoking models, setting up Knowledge Bases, creating agents, applying guardrails, deploying to AgentCore, migrating\u002Fporting\u002Fconverting a Bedrock Agent (including inline agents) to an AgentCore Harness, troubleshooting Bedrock errors (ThrottlingException, AccessDeniedException), or choosing models (Claude, Llama, Nova, Titan). ALSO USE for prompt caching, quota health checks and throttling diagnosis, cost attribution, migrating between Claude model generations, chunking strategies, API selection (Converse vs InvokeModel), and model selection. Also covers AgentCore Payments setup (x402, microtransactions, Payment Manager, Coinbase CDP, Stripe Privy, 402 Payment Required, paid endpoint). NOT for custom model training, Rekognition, or Comprehend.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1599,1600,1601],{"name":1405,"slug":1406,"type":15},{"name":23,"slug":8,"type":15},{"name":1602,"slug":1603,"type":15},"LLM","llm","2026-08-07T04:38:13.03499",{"slug":1606,"name":1606,"fn":1607,"description":1608,"org":1609,"tags":1610,"stars":24,"repoUrl":25,"updatedAt":1619},"amazon-documentdb","manage Amazon DocumentDB clusters","Manages Amazon DocumentDB end-to-end — serverless-on-8.0 cluster setup, TLS\u002FVPC\u002Fdriver config, flexible-schema and vector-search data modeling, MongoDB compatibility assessment, DMS-based migration, slow-query diagnosis, major version upgrades (4.0→5.0→8.0), Well-Architected reviews (41-check wa_review.py), cost estimation, and security hardening. Retrieve for every DocumentDB question and when the user asks to set up or migrate MongoDB to AWS — DocumentDB is AWS's MongoDB-compatible managed database. Triggers: JSON document store, document database, MongoDB on AWS, Nested fields, Lambda cannot connect, TLS handshake, VPC port 27017, IAM auth, Secrets Manager, encryption at rest, $graphLookup, flexible schema, COLLSCAN, compound index, DMS migration, CDC cutover, $vectorSearch, RAG, Global Clusters, DR replication, cost sizing, audit, health check, production-readiness.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1611,1612,1613,1616],{"name":23,"slug":8,"type":15},{"name":1571,"slug":1572,"type":15},{"name":1614,"slug":1615,"type":15},"MongoDB","mongodb",{"name":1617,"slug":1618,"type":15},"NoSQL","nosql","2026-07-12T08:43:00.455878",118]