aws-debug

Inspect DynamoDB state, S3 buckets, Lambda execution, and CloudFormation stacks.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Stream-claims/stream-engineering --skill aws-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-debug
Source: https://github.com/Stream-claims/stream-engineering/tree/main/skills/aws-debug
Command: npx skills add https://github.com/Stream-claims/stream-engineering --skill aws-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve issues within AWS infrastructure supporting the claims processing pipeline, ensuring smooth operation and quick issue resolution.

Core Features & Use Cases

  • Infrastructure Inspection: Examine DynamoDB state, S3 bucket contents, Lambda execution, and CloudFormation stacks.
  • Root Cause Analysis: Trace issues across different AWS services to pinpoint the source of problems.
  • Use Case: When a user reports a case is failing to process, this Skill can be used to inspect the relevant DynamoDB entries, check S3 for corrupted files, and review Lambda logs for errors.

Quick Start

Use the aws-debug skill to check the status of the 'arrowhead-table-production' DynamoDB table.

Frequently Asked Questions about aws-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug AWS infrastructure when a claims processing pipeline fails?

To debug AWS infrastructure for claims processing failures, you inspect DynamoDB state, check S3 buckets for corrupted files, and review Lambda execution logs to pinpoint the root cause across services.

What's the best way to trace issues across DynamoDB, S3, and Lambda?

Tracing issues across DynamoDB, S3, and Lambda involves examining DynamoDB table entries, checking S3 bucket contents, and reviewing Lambda logs to identify execution errors and resolve processing failures.

Do I need AWS CLI to inspect CloudFormation stacks and DynamoDB state?

Yes, you need AWS CLI installed and configured, along with knowledge of AWS service configurations, to safely interact with and inspect CloudFormation stacks and DynamoDB state.

Can I use this approach to check the status of a specific DynamoDB table?

Yes, you can check the status of specific DynamoDB tables like 'arrowhead-table-production' by querying the table state to diagnose processing issues and verify data integrity.

Why does my Lambda function fail to process claims from S3?

Lambda functions fail to process claims from S3 due to corrupted files in S3 buckets, execution errors in Lambda logs, or state mismatches in DynamoDB, requiring cross-service root cause analysis.

Are there safety guidelines for interacting with AWS resources during debugging?

Yes, operational safety guidelines are provided for interacting with AWS resources during debugging to prevent accidental data modification or deletion while inspecting DynamoDB, S3, Lambda, and CloudFormation.