Sagemaker Ai

Agent Plugins for AWS

Read this in other languages: 日本語

[!IMPORTANT] Generative AI can make mistakes. You should consider reviewing all output and costs generated by your chosen AI model and agentic coding assistant. See AWS Responsible AI Policy.

What's new

[!TIP] The Agent Toolkit for AWS is now live! The Agent Toolkit for AWS is the successor to the MCP servers, plugins, and skills available on AWS Labs, and was informed by feedback from customers like you. If you're building production software using coding agents or building agents for your own customers, we recommend Agent Toolkit for AWS. It includes IAM condition keys to distinguish agent actions from human ones, CloudWatch and CloudTrail visibility, and skills that have been evaluated for accuracy and effectiveness. This repo continues to work and accept contributions. Over time, the most useful projects here will move into Agent Toolkit for AWS.

Agent Plugins for AWS

Agent Plugins for AWS equip AI coding agents with the skills to help you architect, deploy, and operate on AWS. Agent plugins are currently supported by Claude Code, Codex, and Cursor.

AI coding agents are increasingly used in software development, helping developers write, review, and deploy code more efficiently. Agent skills and the broader agent plugin packaging model are emerging as best practices for steering coding agents toward reliable outcomes without bloating model context. Instead of repeatedly pasting long AWS guidance into prompts, developers can now encode that guidance as reusable, versioned capabilities that agents invoke when relevant. This improves determinism, reduces context overhead, and makes agent behavior easier to standardize across teams. Agent plugins act as containers that package different types of expertise artifacts together. A single agent plugin can include:

• Agent skills – Structured workflows and best-practice playbooks that guide AI through complex tasks like deployment, code review, or architecture planning. Agent skills encode domain expertise as step-by-step processes.
• MCP servers – Connections to external services, data sources, and APIs. MCP servers give your assistant access to live documentation, pricing data, and other resources at runtime. Learn more about MCP servers for AWS.
• Hooks – Automation and guardrails that run on developer actions. Hooks can validate changes, enforce standards, or trigger workflows automatically.
• References – Documentation, configuration defaults, and knowledge that the agent skill can consult. References make agent skills smarter without bloating the prompt.

As new types of expertise artifacts emerge in this space, they can be packaged into agent plugins, making the evolution transparent to developers.

Best practices

To maximize the benefits of plugin-assisted development while maintaining security and code quality, follow these essential guidelines:

• Always review generated code before deployment (for example, against your constraints for security, cost, resilience)
• Use plugins as accelerators, not replacements for developer judgment and expertise.
• Keep plugins updated to benefit from the latest AWS best practices.
• Follow the principle of least privilege when configuring AWS credentials.
• Run security scanning tools on generated infrastructure code.

Plugins

Installation

Claude Code

Add the marketplace

/plugin marketplace add awslabs/agent-plugins

Install a plugin

/plugin install amazon-location-service@agent-plugins-for-aws

or

/plugin install aws-amplify@agent-plugins-for-aws

or

/plugin install aws-serverless@agent-plugins-for-aws

or

/plugin install codebase-documentor-for-aws@agent-plugins-for-aws

or

/plugin install databases-on-aws@agent-plugins-for-aws

or

/plugin install deploy-on-aws@agent-plugins-for-aws

or

/plugin install sagemaker-ai@agent-plugins-for-aws

Codex

Codex supports repo-local marketplaces and plugin manifests through .agents/plugins/marketplace.json and per-plugin manifests under plugins/*/.codex-plugin/plugin.json; this repo includes both, following the official Codex plugin packaging guidance in Build plugins.

To try these plugins in Codex from this repo:

1. Clone this repository locally.
2. Open the repo in Codex so Codex can discover .agents/plugins/marketplace.json.
3. Restart Codex.
4. Open the plugin directory, choose the Agent Plugins for AWS marketplace, and install the plugin you want to use.

Known limitation:

• Claude-specific automatic hooks are not yet wired into the Codex manifests.
• The databases-on-aws prompt hook is included because it does not depend on Claude-specific environment variables.

Cursor

You can install the deploy-on-aws plugin from the Cursor Marketplace. For additional information, please refer to the Cursor plugin documentation. You can also install within the Cursor application:

• Open Cursor Settings
• Navigate to Plugins
• Search for AWS
• Select the plugin you want to install and click Add to Cursor
• Select the scope for the installed plugin
• The plugin should appear under Plugins -> Installed

Kiro (experimental)

You can convert Claude Code plugins into Kiro format using the third-party @every-env/compound-plugin CLI. This converts skills (SKILL.md workflow instructions and reference documents) and MCP server configs into Kiro's .kiro/ format.

Requires Bun (latest version recommended).

[!NOTE] Hook conversion is a work in progress — hooks are currently dropped entirely during conversion because the Claude Code and Kiro hook models are not 1:1. Skills and MCP servers are fully supported.

Project scope

Writes to .kiro/ in the current working directory:

COMPOUND_PLUGIN_GITHUB_SOURCE=https://github.com/awslabs/agent-plugins \
  bunx @every-env/compound-plugin install deploy-on-aws --to kiro

Global scope

Writes to ~/.kiro/ so skills are available across all projects:

COMPOUND_PLUGIN_GITHUB_SOURCE=https://github.com/awslabs/agent-plugins \
  bunx @every-env/compound-plugin install deploy-on-aws --to kiro --output ~/.kiro

Replace deploy-on-aws with any plugin name from the table above (e.g., aws-serverless, amazon-location-service, migration-to-aws, aws-amplify).

[!TIP] If a skill isn't activated automatically, you can explicitly invoke it by saying "Use the deploy skill to ..." in your prompt. Kiro's intent matching may not always auto-trigger skills.

If bunx fails with a "Cannot find package" error, clear the bun cache and retry:

rm -rf ~/.bun/install/cache/@every-env

Copy to clipboard

For issues with the conversion tool, please report them at EveryInc/compound-engineering-plugin.

amazon-location-service

Guides developers through adding maps, places search, geocoding, routing, and other geospatial features with Amazon Location Service, including authentication setup, SDK integration, and best practices.

Agent Skill Triggers

MCP Servers

aws-amplify

Build full-stack apps with AWS Amplify Gen 2 using TypeScript code-first development, guided by official AWS Agent Standard Operating Procedures (SOPs).

Workflow

1. Backend - Create Amplify Gen 2 resources (auth, data, storage, functions)
2. Sandbox - Deploy to sandbox for testing
3. Frontend & Test - Connect frontend to backend, verify locally
4. Production - Deploy to production

Agent Skill Triggers

…