Agents Harden
Use when preparing your agent for production, IAM scoping, inbound auth (JWT, SigV4)...
Install
npx skills add aws/agent-toolkit-for-aws --skill agents-harden -g -a claude-code -y- Repository
- aws/agent-toolkit-for-aws3.4k
- Category
- Testing
- Updated
- 5d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use when preparing your agent for production, IAM scoping, inbound auth (JWT, SigV4), secrets management, cold start optimization, session lifecycle, rate limiting, input validation, and quota guidance. Triggers on: "production checklist", "harden agent", "production ready", "secure agent", "inbound auth", "going live", "cold start optimization", "session lifecycle", "StopRuntimeSession", "quota", "throttling", "maxVms", "rate limit", "security audit of outbound API calls", "gateway target audit for production", "restrict who can call", "lock down endpoint", "only our app can call". Not for Cedar tool-restriction policies, use agents-connect. Not for quality measurement, use agents-optimize. Not for outbound credential storage or API key wiring, use agents-connect. Not for A2A agent-to-agent auth, use agents-build. Cold start observation and diagnosis (not optimization) routes to agents-debug.
harden
Prepare your AgentCore agent for production, security, reliability, and performance.
When to use
- You're about to take an agent to production
- You want a checklist of what to review before launch
- You want to restrict who can call your agent
- You want to scope down IAM permissions from the defaults
- You're hitting throttling or quota errors (loads
references/limits.md) - You need to tune session lifecycle for your workload
- You're running long-running background work in your agent
Input
No arguments required. The skill reads your project config and produces a checklist with specific findings for your project.
Process
Step 0: Verify CLI version
Run agentcore --version. This skill requires v0.9.0 or later. If the version is older, tell the developer to run agentcore update before proceeding.
Step 1: Read the project
Read agentcore/agentcore.json to understand:
- What resources are configured (memory, gateway, credentials, evaluators)
- What framework is being used
- What network mode is configured (PUBLIC or VPC)
Step 2: Run through the checklist
Work through each category and report findings specific to the project.
IAM: Scope down permissions
The auto-created execution role has broad Bedrock access (arn:aws:bedrock:*::foundation-model/*). For production, scope it to the specific models your agent uses.
Check the current execution role:
agentcore status --json | jq -r '.runtimes[0].executionRoleArn'
Recommended production Bedrock policy:
{
"Effect": "Allow",
"Action": [
"bedrock:InvokeModel",
"bedrock:InvokeModelWithResponseStream"
],
"Resource": [
"arn:aws:bedrock:<REGION>::foundation-model/anthropic.claude-sonnet-4-5-20250929-v1:0"
]
}
Replace the resource ARN with the specific model(s) your agent uses.
ECR access: Scope to your specific repository:
