Install
$ agentstack add skill-aws-samples-sample-ai-agent-skills-chatbot-advanced-troubleshooting ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
AWS Chatbot Advanced Diagnostics
When to use
Any advanced AWS Chatbot investigation — custom actions, action approvals, Microsoft Teams integration, guardrail configuration, notification filtering, run command from chat, Lambda invocation, cross-account notifications, event pattern matching, or audit logging.
Investigation workflow
Step 1 — Collect and triage
aws chatbot describe-slack-channel-configurations --max-results 20
aws chatbot list-microsoft-teams-channel-configurations --max-results 20
aws sns list-topics --query 'Topics[*].TopicArn'
Step 2 — Domain deep dive
aws chatbot describe-slack-channel-configurations --chat-configuration-arn
aws chatbot get-microsoft-teams-channel-configuration --chat-configuration-arn
aws iam get-role --role-name
Step 3 — Detailed investigation
aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventSource,AttributeValue=chatbot.amazonaws.com --max-results 20
aws logs filter-log-events --log-group-name /aws/chatbot/ --start-time
aws sns get-topic-attributes --topic-arn
Read references/guardrails.md before concluding on any advanced Chatbot issue.
Tool quick reference
| Tool / API | When to use | |------------|-------------| | chatbot describe-slack-channel-configurations | List Slack configurations | | chatbot list-microsoft-teams-channel-configurations | List Teams configurations | | chatbot get-microsoft-teams-channel-configuration | Get Teams config details | | sns list-topics | List SNS topics for notifications | | sns get-topic-attributes | Get topic configuration | | iam get-role | Check Chatbot IAM role permissions | | cloudtrail lookup-events | Audit Chatbot actions |
Gotchas: AWS Chatbot Advanced
- Custom actions allow running predefined commands from chat. They require explicit IAM permissions on the Chatbot channel role AND the action must be defined in the channel configuration.
- Microsoft Teams integration uses a different OAuth flow than Slack. Teams requires Azure AD app registration and Chatbot workspace configuration before channel setup.
- Guardrails restrict which commands and actions can be run from chat. They are configured per channel and use IAM policy syntax. Overly restrictive guardrails silently block commands.
- Run Command from chat executes SSM Run Command on instances. It requires the Chatbot role to have ssm:SendCommand AND the target instances must have SSM agent running.
- Cross-account notifications require the SNS topic in the source account to allow the Chatbot account to subscribe. The Chatbot configuration must reference the cross-account topic ARN.
- Event pattern matching for notifications uses EventBridge patterns. Incorrect patterns cause notifications to be silently dropped — no error is generated.
- Audit logging for Chatbot actions goes to CloudTrail. Chat commands and their results are logged, but the chat message content itself is not stored in CloudTrail.
Anti-hallucination rules
- Always cite specific configuration ARNs, channel IDs, or API responses as evidence.
- Slack and Teams integrations have different setup flows and limitations. Never conflate them.
- Guardrails use IAM policy syntax but are NOT IAM policies. Never suggest modifying IAM policies to fix guardrail issues.
- Run Command from chat and Lambda invocation from chat have different permission models. Never mix them up.
- Spend no more than 2 minutes on any single hypothesis. Pivot if inconclusive.
12 runbooks
| Category | IDs | Covers | |----------|-----|--------| | A — Custom Actions | A1-A2 | Custom action failures, action approval issues | | B — Teams | B1-B2 | Teams integration, Teams channel config | | C — Guardrails | C1-C2 | Guardrail configuration, notification filtering | | D — Operations | D1-D2 | Run command from chat, Lambda invocation from chat | | E — Cross-Account | E1-E2 | Cross-account notifications, event pattern matching | | F — Audit | F1 | Audit logging | | Z — Catch-All | Z1 | General troubleshooting |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: aws-samples
- Source: aws-samples/sample-ai-agent-skills
- License: MIT-0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.