skills.rest
expeor
expeorCOMMUNITY
Explore all skills by this author →
GitHub

error-handling-patterns

Centralize and classify AWS API errors across accounts and regions.

Updated Aug 27, 2026
Search Tags:#debugging#categorization#error-handling#retry#decorator#aws-automation#error-collector
One-click install
npx skills add https://github.com/expeor/aws-automation --skill error-handling-patterns-expeor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-handling-patterns
Source: https://github.com/expeor/aws-automation/tree/main/.claude/skills/error-handling-patterns
Command: npx skills add https://github.com/expeor/aws-automation --skill error-handling-patterns-expeor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralize and classify AWS API errors to enable resilient automation workflows.

Core Features & Use Cases

  • Unified error collection and severity handling for API calls across accounts and regions
  • Decorators for safe AWS calls with built-in retry and structured error handling
  • Automatic error categorization (THROTTLING, ACCESS_DENIED, NOT_FOUND, etc.) for consistent reporting
  • Guidance on using ErrorCollector, try_or_default, and related utilities to simplify robust automation

Quick Start

Install the library and begin wrapping AWS API calls with ErrorCollector to track and report errors during automation.

Frequently Asked Questions about error-handling-patterns

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

FAQPage Schema
How do I handle AWS API errors consistently across multi-account and multi-region automation?▼

You can centralize and classify AWS API errors using an ErrorCollector to track failures across accounts and regions, enabling structured reporting and resilient automation workflows.

What is the best way to categorize AWS API errors like throttling or access denied for reporting?▼

Automatic error categorization classifies AWS API failures into types like THROTTLING, ACCESS_DENIED, and NOT_FOUND. This structured approach ensures consistent reporting across automation dashboards.

How do I add retry logic to AWS API calls without writing custom wrappers?▼

Use decorators like safe_aws_call to wrap API calls with built-in retry mechanisms and structured error handling. This simplifies robust automation without requiring custom wrapper functions.

Can I provide a default value when an AWS API call fails during automation?▼

Yes, the try_or_default utility allows you to supply a default value when an AWS API call fails. This prevents automation workflows from breaking entirely when non-critical API errors occur.

Does this error handling approach work for AWS automation tasks spanning multiple services?▼

Yes, the ErrorCollector is designed to collect errors across multiple AWS services during multi-account and multi-region automation tasks. It aggregates failures for unified severity handling and dashboard reporting.

Related Skills

Explore More Software Engineering Skills→
markus41markus41
1

aws

Provision and manage AWS infrastructure via CLI, Boto3, and Terraform.

Community
Advanced
RB-chrismandichRB-chrismandich
1

dashboard

Aggregate agent output logs into markdown performance dashboards.

Community
Advanced
awsaws
2.3k

setting-up-cloudtrail-multi-region

Set up centralized multi-region AWS CloudTrail logging with S3 and CloudWatch.

Official
Advanced
coreyjacoreyja
6

Global Error Handling

Implement try-catch blocks, error boundaries, and retries with exponential backoff across frontend and backend.

Community
Basic