aws/aws-agents-for-devsecops
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-agentskill now starts setup if a 401 occurs andDEVOPS_AGENT_TOKENis 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 theurl. Some clients, for example Codex, send this text as it is. - The server will send
Access token not configuredfor 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 tool | New tool |
|---|---|
create_release_readiness_review | create_code_change_risk_analysis |
| none | list_code_change_risk_analyses |
cancel_release_readiness_review | cancel_code_change_risk_analysis |
get_release_readiness_report | get_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_ANALYSISorRELEASE_READINESS_REVIEW).list_code_change_risk_analysesreturns reviews of both types. - The aws-mcp fallback creates
CODE_CHANGE_RISK_ANALYSIStasks. - Report files are saved as
code-change-risk-analysis-<timestamp>.md, and the local flow pushesfeat/code-change-risk-analysisandfeat/code-change-risk-analysis-fixbranches. - 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_depth | Meaning | Older equivalent |
|---|---|---|
static-analysis | Static analysis only | skip_automated_testing=true |
verification-testing | Static analysis plus automated testing | skip_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-testingcan't turn it on elsewhere. - The aws-mcp fallback writes
metadata.reviewDepthtogether with the matchingmetadata.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).