Skip to content

aws/aws-agents-for-devsecops

v1.2.1Apache-2.0

Investigate incidents, review code and execute UAT for release readiness, scan code for vulnerabilities, and run penetration tests with AWS DevOps Agent and AWS Security Agent.

Changelog

Changes to the aws-agents-for-devsecops plugin that can change how it behaves for a user. Read this when a skill or command stops working as it used to.

1.2.1

Clear help for the HTTP 401 before setup

Before setup, the default aws-devops-agent entry sends Bearer ${DEVOPS_AGENT_TOKEN}. The token is not set, so the server sends HTTP 401. The 401 message was Invalid or expired access token. This message did not tell the user to do setup.

  • The setup-devops-agent skill now starts setup if a 401 occurs and DEVOPS_AGENT_TOKEN is not set. Before this change, the skill told the user to make a new token.
  • The README tells the user to do setup before first use. It also tells the user that the 401 is normal until setup is complete.
  • Setup now writes the region name into the Bearer url. Before this change, setup wrote ${DEVOPS_AGENT_REGION} in the url. Some clients, for example Codex, send this text as it is.
  • The server will send Access token not configured for a placeholder token. The skill identifies the old message and the new message.

1.2.0

Release readiness review is now code change risk analysis

The analyzing-release-readiness skill and the /aws-agents-for-devsecops:release-readiness command call the code change risk analysis tools on the AWS DevOps Agent MCP server.

Old toolNew tool
create_release_readiness_reviewcreate_code_change_risk_analysis
nonelist_code_change_risk_analyses
cancel_release_readiness_reviewcancel_code_change_risk_analysis
get_release_readiness_reportget_code_change_risk_analysis_report
  • The old tools still exist on the server and do the same thing, so older copies of the plugin keep working.
  • The server picks the task type (CODE_CHANGE_RISK_ANALYSIS or RELEASE_READINESS_REVIEW). list_code_change_risk_analyses returns reviews of both types.
  • The aws-mcp fallback creates CODE_CHANGE_RISK_ANALYSIS tasks.
  • Report files are saved as code-change-risk-analysis-<timestamp>.md, and the local flow pushes feat/code-change-risk-analysis and feat/code-change-risk-analysis-fix branches.
  • The skill and command names did not change.

If the skill falls back to aws-mcp, or prompts for every call: a tool allowlist (for example permissions.allow in Claude Code settings) or an MCP client that connected before the server update may only know the old tool names. Allow the new tool names and restart the session.

Review depth

The skill and command send review_depth instead of skip_automated_testing when starting an analysis.

review_depthMeaningOlder equivalent
static-analysisStatic analysis onlyskip_automated_testing=true
verification-testingStatic analysis plus automated testingskip_automated_testing=false
  • The skill still asks the user whether they want a quick or a full analysis. Only the parameter changed.
  • Automated testing runs only on repositories where it is enabled in the agent space. verification-testing can't turn it on elsewhere.
  • The aws-mcp fallback writes metadata.reviewDepth together with the matching metadata.skipAutomatedTesting.
  • The server still accepts skip_automated_testing.

If create_code_change_risk_analysis rejects review_depth: the server doesn't support it yet. Retry with skip_automated_testing (true for static analysis only).