Diagnose application failures by finding relevant CloudWatch logs and examining error patterns and stack traces. Follow clues into related AWS configuration, identify likely causes, and produce prioritized recommendations for fixing the problem.
Troubleshoots failing applications by discovering and analyzing CloudWatch log groups to identify error patterns, root causes, and actionable solutions. Use when an application is experiencing failures and log-based diagnosis is needed.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Domain expertise for diagnosing application failures through CloudWatch log analysis. Discovers relevant log groups, searches for error patterns and stack traces, performs root cause analysis, and generates prioritized remediation recommendations.
Logs are where the investigation starts, not its boundary. When the logs point at a timeout, throttle, retry or permission problem, read the configuration that sets it, for example the API Gateway integration timeout, the queue's visibility timeout, or the function timeout and event source mapping. Read-only access normally includes these Describe and Get calls.
To diagnose and resolve application failures using CloudWatch logs, follow the procedure exactly. See Application failure troubleshooting procedure.
Ask the user for specific log group names. Common patterns: /aws/lambda/function-name,
/aws/apigateway/api-name, or custom application log groups.
Verify AWS credentials have logs:DescribeLogGroups, logs:DescribeLogStreams,
logs:StartQuery, and logs:GetQueryResults permissions.
Reduce the time window or limit results. Large log groups may require multiple smaller queries.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Choose where to run an AI agent on AWS through a guided assessment. Develop an architecture and rough cost estimate, then optionally create a migration plan and executable proof of concept to test the proposed setup.
Extend an existing AgentCore agent with memory across sessions, app integration, browser access, code execution, payments, or collaboration between agents. The skill also guides private network setup, model changes, migration from Bedrock Agent, and resource removal.
Connect an AgentCore agent to external APIs, MCP servers, and Lambda tools through AgentCore Gateway. Configure credentials and outbound authentication, and use Cedar policies, rules that control which tools an agent may call.
Diagnose AgentCore agent failures by reading logs and traces, records of execution steps. Investigate wrong answers, tool errors, timeouts, and memory problems, or check environment prerequisites when the CLI itself fails.
Prepare and troubleshoot AgentCore deployments to AWS by checking configuration, permissions, and deployment changes. Diagnose common failures, choose deployment targets, and manage versions through rollback, version pinning, or canary deployments that gradually introduce a new version.
Create a new agent project on AWS with AgentCore. Get help choosing a framework, generating the project structure, running it locally, and completing the first deployment and invocation, with explanations of the generated files.