Querying Aws S3

This teaches Claude to query S3 system tables instead of paginating through list-objects-v2 calls. If you're counting millions of objects, auditing who uploaded or deleted files, or filtering by tags, the inventory and journal tables answer in seconds what would take thousands of API calls. The skill includes a decision tree showing when system tables beat raw APIs, handles catalog setup and permissions, and covers both S3 Metadata tables (journal, inventory, annotation) and Storage Lens exports. One catch: you need to enable metadata tracking first, and the skill walks through that configuration. It's built for the AWS MCP server but works anywhere with credentials and Athena access.

skills.sh installs: 6K
GitHub stars: 3.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aws/agent-toolkit-for-aws --skill querying-aws-s3 --agent claude-code

Installs into .claude/skills of the current project.

Files

Query AWS S3 System Tables

Overview

Works best with the AWS MCP server for sandboxed execution and audit logging. All commands below use the AWS CLI and work in any environment with configured AWS credentials. Use IAM roles or temporary credentials; avoid long-lived access keys.

Amazon S3 Metadata provides continuously-updated Apache Iceberg tables that capture object-level metadata for general-purpose buckets. S3 Storage Lens exports aggregated storage and activity metrics as Iceberg tables. Both are read-only, stored in the AWS-managed aws-s3 table bucket, and queryable via Amazon Athena.

System tables are preferred over raw S3 APIs (list-objects-v2, head-object) because:

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly