AWS Integration

Integrate stupid-db with AWS Athena, Aurora/RDS, and S3 parquet files.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/FrancisVarga/stupid-db --skill aws-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: AWS Integration
Source: https://github.com/FrancisVarga/stupid-db/tree/main/packages/stupid-claude-agent/.claude/skills/aws-integration
Command: npx skills add https://github.com/FrancisVarga/stupid-db --skill aws-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aws-config, aws-sdk-athena, aws-sdk-s3, sqlx, bb8, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the integration of stupid-db with various AWS services, enabling efficient data querying, enrichment, and storage without complex manual configurations.

Core Features & Use Cases

  • Athena Integration: Query historical data directly from S3 using Athena, with cost control measures.
  • Aurora/RDS Enrichment: Enrich graph entities with relational data from Aurora or RDS databases.
  • S3 Direct Access: Read parquet files directly from S3 for immediate data access.
  • Secure Authentication: Utilizes standard AWS credential chains, avoiding direct storage of credentials.
  • Use Case: Analyze multi-year historical event data stored in S3 via Athena, then enrich user profiles with current information from an Aurora RDS instance to gain a comprehensive view of user behavior.

Quick Start

Configure AWS Athena integration by setting the necessary environment variables for access keys, region, and S3 output bucket.

Frequently Asked Questions about AWS Integration

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

FAQPage Schema
How do I query historical data in S3 parquet files using Athena?

Query historical S3 parquet data using Athena by configuring standard AWS credential chains and setting an S3 output bucket for results. This Skill facilitates direct Athena querying with built-in cost control mechanisms to manage expenses.

How do I enrich graph entities with relational data from Aurora or RDS?

Enrich graph entities with relational data from Aurora or RDS by connecting through standard AWS authentication chains. This integration enables seamless data enrichment without storing direct database credentials in your application.

Can I read parquet files directly from S3 without using Athena?

Read parquet files directly from S3 for immediate data access without requiring Athena. This direct access capability allows you to bypass query engines and retrieve raw file data from your S3 buckets instantly.

Does this AWS integration require hardcoding access keys for authentication?

AWS integration authentication does not require hardcoding access keys. It utilizes standard AWS credential chains to manage secure authentication, avoiding direct storage of credentials and simplifying environment configuration.

How can I control costs when running Athena queries on historical S3 data?

Control Athena query costs on historical S3 data using the built-in cost control mechanisms provided by this integration. These measures help manage and limit expenses associated with multi-year historical data analysis.

What is the best way to combine Athena historical queries with current RDS data?

Combine Athena historical queries with current RDS data by querying multi-year S3 event data and enriching user profiles with real-time Aurora information. This approach provides a comprehensive view of user behavior across time.