If your organization has an AWS Support plan that includes Enterprise support for Kiro, you can raise and manage Kiro support cases in two ways:
| Option | How |
|---|---|
| AWS Support directly | Open a case in the AWS Support Center console, or call the AWS Support API. |
| Kiro Support power | Raise cases from Kiro. The agent collects diagnostics, drafts the case, and files it after you approve it. |
The rest of this page covers the Kiro Support power.
The Kiro Support power lets you file, track, reply to, and resolve Kiro support cases without leaving Kiro. The agent collects Kiro diagnostics from your local environment, drafts a structured case body, and files the case after you approve it.
The power is open source (Apache-2.0) and follows the Agent Plugins specification. For the source and configuration files, see the Kiro Support power on GitHub.
| Capability | IDE | CLI | Web | Mobile |
|---|---|---|---|---|
| Use the Kiro Support power | ✓ | V3 | — | — |
| Task | Example prompt |
|---|---|
| File a case | File a normal case: Kiro chat disconnects on macOS after 10 minutes |
| Track cases | Show my open cases or Status of case-12345 |
| Reply to a case | Add the latest debug log to case-12345 |
| Resolve a case | Resolve case-12345. You can reopen a resolved case within 7 days. |
| Capture diagnostics | Collect diagnostics for this case. Reads the conversation ID, session type, and debug log snippets from your machine. |
| Check access | The power runs a pre-flight check and drafts a request to your administrator if permissions are missing. |
uv and Python 3.10 or later. See Installing uv.The power uses the following AWS Support actions. For a description of each action and how to add them to an IAM policy, see Manage access to AWS Support Center. AWS Support actions don't support resource-level permissions, so set Resource to *.
| Action | Used to |
|---|---|
support:CreateCase | File a case |
support:DescribeCases | List and search cases |
support:DescribeCommunications | Read case communications |
support:AddCommunicationToCase | Reply to a case |
support:AddAttachmentsToSet | Attach debug logs |
support:DescribeAttachment | Read attachments on a case |
support:DescribeServices | Look up service and category codes |
support:DescribeSeverityLevels | Look up severity levels |
support:DescribeCreateCaseOptions | Look up case contact options |
support:DescribeSupportedLanguages | Look up supported case languages |
support:ResolveCase | Resolve a case |
Go to kiro.dev/powers and search for Kiro Support.
Select the Kiro Support power, then choose Add to Kiro. Kiro IDE opens so you can complete the installation.
For other installation options, see Install powers.
The power calls the AWS Support API with your own AWS credentials, and uses the us-east-1 Region. Before you file your first case:
aws configure sso.AWS_PROFILE in the power's MCP configuration to that profile name, then reconnect the MCP server. The power checks for this on first use and asks you if the value is still the <your-aws-profile> placeholder.aws sso login --profile <profile> at the start of each session. Sign-in tokens expire, typically daily.When you mention a support keyword such as "file a case" or "check my support cases", Kiro activates the power. The agent then does the following:
The power's mcp.json defines two MCP servers. Both use the same IAM permissions.
| Role | Server | Description |
|---|---|---|
| Primary | awslabs.aws-support-mcp-server | Typed tools for each Support API operation. |
| Fallback | aws-mcp (Agent Toolkit for AWS) | Runs aws support CLI commands. Used when the primary server can't start. |
For common errors and fixes, such as AccessDenied, SubscriptionRequiredException, and expired sign-in tokens, see Troubleshooting in the Kiro Support power repository. For general Kiro issues, see the IDE troubleshooting guide.
Support for Kiro Enterprise customers