aws

Implements secure boto3 and AWS SDK v3 patterns for S3, DynamoDB, Lambda, and SQS.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/MARUCIE/openclaw-foundry --skill aws-marucie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws
Source: https://github.com/MARUCIE/openclaw-foundry/tree/main/web/public/packs/spellbook-security-auditor/skills/aws
Command: npx skills add https://github.com/MARUCIE/openclaw-foundry --skill aws-marucie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing AWS code often leads to hardcoded credentials, overly permissive IAM policies, DynamoDB scans that blow up costs, and SQS consumers that duplicate or lose messages. This Skill provides production-grade patterns for boto3 and AWS SDK v3 that prevent credential leaks, throttling failures, and audit findings. ## Core Features & Use Cases - Credential Chain & IAM Least Privilege: Enforces role-based authentication (instance profiles, OIDC for GitHub Actions, Lambda execution roles) and provides scoped IAM policy templates with specific actions and resource ARNs. - Service Patterns for S3, DynamoDB, Lambda, SQS: Covers presigned URLs, multipart uploads, single-table DynamoDB design, warm-instance client reuse in Lambda handlers, and SQS partial batch failure handling. - Secrets, Retries, and Cost Controls: Includes Secrets Manager vs Parameter Store guidance, botocore adaptive retry configuration, ClientError branching by error code, and cost levers like S3 lifecycle policies. - Use Case: You are writing a Lambda function triggered by SQS that reads from DynamoDB and writes to S3. Activate this Skill to get the correct handler structure, visibility timeout guidance, batchItemFailures response format, and a least-privilege IAM policy. ## Quick Start Ask the AI to write a Lambda handler that processes SQS messages with partial batch failure support and least-privilege IAM permissions.

Frequently Asked Questions about aws

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

FAQPage Schema
How do I authenticate boto3 without hardcoding AWS credentials?▼

boto3 resolves credentials through a chain: environment variables, ~/.aws/credentials, then IAM instance profiles or task roles. Use named profiles locally with aws configure --profile dev, and IAM roles in Lambda, ECS, or EC2 so no long-lived keys exist in code.

How do I handle partial batch failures in a Lambda SQS consumer?▼

Return a batchItemFailures list containing only the messageIds that failed processing, and enable ReportBatchItemFailures in the event source mapping. SQS then retries only failed messages instead of requeuing the entire batch.

Should I use DynamoDB or RDS for my application?▼

Choose DynamoDB when access patterns are known, key-based, and need massive scale with minimal operations. Choose RDS when you need ad-hoc queries, complex joins, strict ACID transactions, or a rigid relational schema.

Why does my Lambda function create slow database connections on every invocation?▼

SDK clients initialized inside the handler are recreated per invocation. Initialize boto3 clients and DynamoDB table resources in module scope outside the handler so they are reused across warm invocations.

What is the difference between Secrets Manager and Parameter Store?▼

Secrets Manager supports built-in rotation and 64 KB secrets at $0.40 per secret per month, suiting database passwords and API keys. Parameter Store standard tier is free with 4 KB limits, better for configuration values and feature flags.

Why are my SQS messages being processed more than once?▼

Duplicate delivery occurs when the SQS visibility timeout is shorter than the Lambda timeout, making messages visible before processing finishes. Set the visibility timeout to six times the Lambda timeout to prevent this.