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.
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
| Plugin | Description | Status |
|---|
| amazon-location-service | Add maps, geocoding, routing, places search, and geospatial features to applications with Amazon Location Service | Available |
| aws-amplify | Build full-stack apps with AWS Amplify Gen 2 using guided workflows for auth, data, storage, and functions | Available |
| aws-serverless | Build serverless applications with Lambda, API Gateway, EventBridge, Step Functions, and durable functions | Available |
| codebase-documentor-for-aws | Analyze AWS-deployed services and codebases to generate structured technical documentation with source-of-truth citations | Available |
| databases-on-aws | Database guidance for the AWS database portfolio — schema design, queries, migrations, and multi-tenant patterns | Some Services Available (Aurora DSQL) |
| deploy-on-aws | Deploy applications to AWS with architecture recommendations, cost estimates, and IaC deployment | Available |
