Loading image...Kiro

Product

  • About Kiro
  • Agents
  • IDE
  • CLI
  • Web
  • Mobile
  • Crew
  • Pricing
  • Downloads

For

  • Enterprise
  • Startups
  • Students

Community

  • Overview
  • Ambassadors
  • Case studies
  • Discord
  • Events
  • Powers
  • Shop
  • Showcase
  • Stories

Resources

  • Docs
  • Blog
  • Changelog
  • FAQs
  • Videos
  • Report a bug
  • Suggest an idea
  • Billing support

Social

Site TermsLicenseResponsible AI PolicyLegalPrivacy PolicyCookie Preferences
Kiro
  • Agents
  • Enterprise
  • Pricing
  • Docs
SIGN INDOWNLOADS
Kiro

Get Started

InstallationAuthenticationYour first project

Models

OverviewAvailable modelsReasoning effortAWS GovCloud (US) models

Features

How Kiro worksLocal command sandboxACP integrations
Specs
Steering
Hooks
MCP
Permissions
Custom agents
Workflows
Agent Skills
Powers
Cloud sessionsMemoryCompactionKiroignoreCheckpoints and rewind
Built-in tools
Configuration scopes

IDE 1.x

What's new in 1.0
Setup & First Run
Editor
Chat
Experimental
Troubleshooting0.x reference

CLI

Setup & First RunChoose an agent harness
Terminal UI
Chat
Fullscreen modeVoice modeHeadless modeACPAuto complete
Experimental
Troubleshooting
Upgrade from CLI 2.x
2.x reference

Crew

Quick startInstallationRunning 24/7
Bots
Chat
Agent Capabilities
Features
Interfaces
Apps
System & storageConfigurationSecurityTroubleshooting

Web

Setup & First RunIdentity Center
Connect your repositories
Working with the agent
Autonomous modeScheduleConfiguration Sync
Sandbox

Mobile - Preview

Overview

Commands and Reference

CLI commandsSlash commandsBuilt-in toolsExit codesSettings

Billing

OverviewManaging your subscriptionUpgrading your planDowngrading your planCancelling your planPurchasing add-on creditsManaging your paymentsManaging usage notificationsManaging your taxesContacting billing supportDeleting your accountRelated questions

Enterprise

ConceptsOnboarding quickstart
Connecting your identity provider
Deployment optionsSubscribe your teamManage subscriptions
Credit pooling
Governance
Monitor and track
SettingsManaged updatesTLS inspection compatibilityBillingSupportIAMSupported regions
AWS GovCloud (US)

Privacy and Security

OverviewData protectionCode referencesCompliance validationInfrastructure securityIAM permissionsFirewalls, proxies, and data perimetersVPC endpoints (AWS PrivateLink)

Guides

OverviewRunning Kiro in the cloud
Language support
Learn by playing

Migration

Migrating from Q DeveloperMigrating from VSCodeUpgrading from Q CLI
  1. Docs
  3. Enterprise
  5. Support
View as Markdown

Support for Kiro Enterprise customers

View as Markdown

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:

OptionHow
AWS Support directlyOpen a case in the AWS Support Center console, or call the AWS Support API.
Kiro Support powerRaise 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.

Raise Kiro support cases with 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.

CapabilityIDECLIWebMobile
Use the Kiro Support power✓V3——

What you can do

TaskExample prompt
File a caseFile a normal case: Kiro chat disconnects on macOS after 10 minutes
Track casesShow my open cases or Status of case-12345
Reply to a caseAdd the latest debug log to case-12345
Resolve a caseResolve case-12345. You can reopen a resolved case within 7 days.
Capture diagnosticsCollect diagnostics for this case. Reads the conversation ID, session type, and debug log snippets from your machine.
Check accessThe power runs a pre-flight check and drafts a request to your administrator if permissions are missing.

Prerequisites

  • An AWS Business Support+, Enterprise Support, or Unified Operations plan on the account. See Compare AWS Support plans.
  • AWS Support API access. See About the AWS Support API.
  • IAM permissions for the Support actions listed in the next section.
  • uv and Python 3.10 or later. See Installing uv.
  • The AWS CLI with a configured profile.

Required IAM permissions

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 *.

ActionUsed to
support:CreateCaseFile a case
support:DescribeCasesList and search cases
support:DescribeCommunicationsRead case communications
support:AddCommunicationToCaseReply to a case
support:AddAttachmentsToSetAttach debug logs
support:DescribeAttachmentRead attachments on a case
support:DescribeServicesLook up service and category codes
support:DescribeSeverityLevelsLook up severity levels
support:DescribeCreateCaseOptionsLook up case contact options
support:DescribeSupportedLanguagesLook up supported case languages
support:ResolveCaseResolve a case

Install the power

1

Find the power

Go to kiro.dev/powers and search for Kiro Support.

2

Install it

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.

Sign in to AWS

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:

  1. Configure an AWS CLI profile for the account that has your Kiro support plan. For AWS IAM Identity Center, run aws configure sso.
  2. Set 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.
  3. If you use AWS IAM Identity Center, run aws sso login --profile <profile> at the start of each session. Sign-in tokens expire, typically daily.

How it works

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:

  1. Verifies access. Checks Support API connectivity and IAM permissions.
  2. Gathers diagnostics. Collects the conversation ID, session type, and debug logs. Reading local files is opt-in: the agent lists your recent sessions and asks which one the issue occurred in. It asks you for the Kiro version (Help > About), because that isn't stored in session data.
  3. Drafts the case. Builds a structured body with environment, reproduction steps, and errors. Service and category codes are looked up through the Support API.
  4. Files on confirmation. Shows you the full case, files it only after you approve, and returns the case ID.
Warning

Review every draft before you approve it, and remove any secrets or sensitive data. Only the case content you approve is sent, and it goes to the AWS Support API using your credentials.

MCP servers

The power's mcp.json defines two MCP servers. Both use the same IAM permissions.

RoleServerDescription
Primaryawslabs.aws-support-mcp-serverTyped tools for each Support API operation.
Fallbackaws-mcp (Agent Toolkit for AWS)Runs aws support CLI commands. Used when the primary server can't start.

Troubleshooting

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.

Related documentation

  • Powers overview - What powers are and how they work
  • Install powers - Install and manage powers
  • MCP - Configure MCP servers
  • IDE troubleshooting guide - Fix common Kiro issues
Page updated: November 5, 2026
Billing
IAM