aws-connector

List AWS Lambda, RDS, S3, and CloudWatch metrics via read-only SDK operations.

10|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/narailabs/narai-primitives --skill aws-connector-narailabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-connector
Source: https://github.com/narailabs/narai-primitives/tree/main/plugins/aws-connector/skills/aws-connector
Command: npx skills add https://github.com/narailabs/narai-primitives --skill aws-connector-narailabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you answer questions about an AWS account’s read-only inventory—such as what Lambda functions exist, which RDS instances are running, what S3 buckets are available, and what CloudWatch metrics show—without manually digging through multiple AWS consoles.

Core Features & Use Cases

  • Read-only AWS inventory queries: Lists Lambda functions and S3 buckets, and describes RDS instances to quickly understand what’s deployed.
  • CloudWatch metric retrieval: Fetches CloudWatch datapoints for a given namespace, metric, and dimensions to support operational investigations.
  • Example Use Case: Ask what functions exist in us-east-1 with a specific naming prefix, then retrieve CloudWatch metrics for a related namespace to validate system behavior.

Quick Start

Run the aws-connector CLI with the list_functions action and your region and optional prefix to get a JSON inventory of Lambda functions.

Frequently Asked Questions about aws-connector

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

FAQPage Schema
How do I list AWS Lambda functions in a specific region?

You can list AWS Lambda functions by executing a read-only list action scoped to a specific AWS region, optionally filtering by a naming prefix. The query returns a JSON inventory of functions without requiring direct AWS console access.

Can I retrieve CloudWatch metrics for troubleshooting without write access?

Yes, you can retrieve CloudWatch metrics by fetching datapoints for a specified namespace, metric, and dimensions. This read-only operation uses whitelisted Get* SDK operations to safely support operational investigations without write access.

What is the safest way to check RDS instances and S3 buckets across an AWS account?

The safest way to check RDS instances and S3 buckets is using a read-only connector restricted to whitelisted Describe* and List* SDK operations. S3 bucket listing runs account-wide, while RDS queries scope to a single AWS region.

Does this approach support AWS inventory queries for multiple services?

Yes, this approach supports AWS inventory queries across Lambda, RDS, S3, and CloudWatch. It parameterizes read-only actions to list, describe, or fetch datapoints, returning a single JSON envelope on stdout for easy parsing and troubleshooting.

What are the limitations of using read-only AWS inventory queries?

Limitations include being restricted to whitelisted Describe*, List*, and Get* SDK operations only, preventing any resource modifications. Additionally, queries must be scoped to a single AWS region, except for account-wide S3 bucket listing.