iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
AWS Agent Toolkit connects coding agents to AWS documentation and, when authorized, AWS services through the AWS MCP Server. A production setup is not just an install: choose a connection method your agent supports, separate documentation discovery from authenticated actions, limit the IAM permissions available to the agent, and monitor the resulting API activity.
What the AWS Agent Toolkit includes
AWS describes four parts that work together:
- AWS MCP Server: A managed service that lets compatible agents interact with AWS through the Model Context Protocol (MCP). It can provide documentation access and, when properly authenticated and authorized, tools that make AWS API calls or run scripts.
- Skills: Curated packages of task-specific instructions and reference materials. AWS says skills can be discovered at runtime through the MCP Server or installed locally.
- Plugins: Installable bundles that pair server configuration with a selected set of skills, providing a convenient setup path where a client supports plugins.
- Rules files: Persistent project-level instructions and guardrails that shape how an agent works within a project.
Together, these components are intended to help coding agents build, deploy, and manage AWS applications using AWS documentation and guided procedures. Skills provide task guidance; rules set project-specific expectations; the server supplies the connection to AWS; and plugins can bundle configuration and selected skills for installation. These parts are related, but they are not interchangeable: installing a plugin does not itself define the least-privilege permissions for AWS actions.
Choose a connection and installation path
The right path depends on the client and how your team wants to manage configuration and skills. AWS describes plugins as the fastest setup route for supported clients, but direct MCP configuration and AWS CLI-managed setup are alternatives.
Recommended Free Tools
| Path | When it fits | What to plan for |
|---|---|---|
| Plugin installation | Your client supports AWS’s plugin setup and you want a bundled server configuration and selected skills. | Follow the current client-specific AWS setup instructions. The quick-start describes adding the AWS marketplace and installing the aws-core plugin in Codex, with a separate command for Claude Code. |
| Direct MCP configuration | Your client can connect to a remote MCP server, or you prefer to manage server configuration yourself. | Configure the server in the client using AWS’s current instructions. AWS documents this route for Kiro and other compatible clients; Kiro also has a separate skills-installation path. |
| AWS CLI setup wizard | You want an interactive, CLI-managed setup and skill-management workflow. | AWS’s quick-start states AWS CLI 2.35.0 or later as a prerequisite for the wizard. Check the live AWS CLI reference for current version requirements and command details. |
AWS lists support for compatible clients including Claude Code, Cursor, Codex, and Kiro, but support varies by component: its documentation describes plugin support for Claude Code and Codex, while Kiro connects directly and does not require a plugin. Client support and setup steps can change, so verify the current AWS instructions for your exact client before rolling out a configuration.
#1 Best Overall
AWS CLI reference results available on October 7, 2026 showed commands including add-skill, check-skill-updates, list-available-skills, and update-skill, and displayed AWS CLI version 2.37.9. Treat those as a dated snapshot, not a guarantee about the current CLI: confirm syntax and availability in the live reference before using them.
Separate documentation discovery from AWS actions
Documentation search and skill discovery do not require AWS credentials, according to AWS. That allows an agent to answer questions using AWS documentation without being granted an AWS identity. Credentials are required when a tool executes AWS API calls or runs scripts. Those operations are then subject to the permissions of the identity used.
For example, AWS’s quick-start gives prompts such as “What AWS Regions are available?” and “What AWS services should I use to build a serverless API?” as natural-language examples. A prompt such as “Help me troubleshoot why my CloudFormation deployment failed” may begin with documentation-based guidance, but any operation that inspects or changes AWS resources requires authenticated access and appropriate authorization.
Make that boundary explicit in your team’s operating rules. Decide which tasks are documentation-only, which may inspect live resources, and which may create, update, or delete them. Do not treat an agent’s ability to describe an action as evidence that it has permission to perform it; nor should a successful connection be mistaken for approval to use every AWS service.
Rank #3
Choose how the agent authenticates
AWS documents two authentication approaches: SigV4 credentials through the MCP Proxy for AWS, and OAuth 2.1 through AWS Sign-in for compatible clients. Neither is universally preferable; the fit depends on client support, whether the workflow is interactive or headless, and how your organization manages credentials and tokens.
| Authentication path | Useful distinction | Documented token or credential behavior |
|---|---|---|
| SigV4 through the MCP Proxy for AWS | Uses AWS credentials and the caller’s existing IAM permissions for server-mediated requests. | Uses SigV4 credentials; the exact credential source and lifecycle depend on your AWS environment and client configuration. |
| OAuth 2.1 through AWS Sign-in | Available to compatible clients; AWS documents interactive and client-credentials flows. | At the time of AWS’s OAuth guide reviewed on October 7, 2026, access tokens were valid for one hour. Interactive refresh tokens were valid for up to 12 hours; AWS Sign-in did not issue a refresh token for client-credentials access. |
Token lifetimes and client support are operational details that can change. Check AWS’s current OAuth guide and your client’s current setup documentation before relying on a particular flow, especially for unattended jobs. Plan how the client obtains, stores, refreshes, and expires credentials rather than placing secrets in project instructions or other files available to the agent.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Keep permissions scoped to the task
In AWS’s documented SigV4 path, the MCP Server authenticates a request, adds the global context keys aws:ViaAWSMCPService and aws:CalledViaAWSMCP, forwards it, and the target AWS service authorizes it against the caller’s existing IAM policies. AWS says no separate MCP-specific IAM actions are required. The server is described as a stateless proxy; the identity’s permissions govern what its operations can do.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteAWS recommends: “We recommend scoping down IAM roles to the minimum permissions that your agent needs to perform its task.” — Amazon Web Services, Agent Toolkit for AWS user guide, “What is the Agent Toolkit for AWS?”
Best Value
For production, translate that principle into an explicit role boundary:
- Grant only the AWS actions and resources needed for the defined task; avoid broad, persistent access just because an agent could use it.
- Separate read-only investigation from deployment or modification workflows where practical, using identities with different permission sets.
- Use the documented MCP context keys in IAM policies or service control policies when you need controls to distinguish server-mediated calls from direct API calls. Test policy conditions against your intended requests before relying on them as a guardrail.
- Review permissions when the agent’s task, installed skills, or project rules change. Instructions can guide behavior, but IAM authorization is what enforces access to AWS resources.
Monitor activity and preserve an audit trail
AWS describes two complementary operational views. The MCP Server automatically publishes metrics to CloudWatch at no additional cost, which supports service and activity monitoring. CloudTrail captures API calls and related events, helping teams investigate which users or accounts called AWS, the source IP, and when calls occurred.
Metrics and audit events answer different questions: CloudWatch helps monitor service activity, while CloudTrail helps establish what API activity occurred and who or what initiated it. Before deployment, verify the available metric names and confirm that the account’s CloudTrail logging configuration captures the events and regions relevant to your workload. Do not assume that the presence of server metrics alone gives you a complete record of AWS resource changes.
Free tools Windows power users keep installed
One-click scans. No signup required.
Understand the cost boundary
AWS states that the Agent Toolkit is available at no additional charge. That does not make agent-driven AWS usage free: AWS resources the agent provisions or interacts with remain subject to standard AWS rates. Budget and review costs based on the services, regions, and usage your workflow can create, not merely the toolkit’s price.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
