Deploys a Regional REST API with a custom domain name, a Lambda backend function, and a request-based Lambda authorizer using AWS CLI. Covers ACM certificate provisioning, API Gateway REST API creation, Lambda function deployment, request authorizer setup, custom domain configuration, base path mapping, and Route 53 DNS record creation. Trigger keywords: custom domain, REST API, Lambda, Route 53, API Gateway, regional endpoint, request authorizer, base path mapping.
Steady49 mentions in 2 weeks
1 project uses a version of this
3.5k3d agoReviewMountCreate a free account to mount
Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size. Uses EventBridge to trigger a Step Functions state machine when objects are uploaded to S3. Small files are processed by Lambda, large files by a Fargate task. Includes VPC, ECR repository, ECS cluster, and scoped IAM roles. Trigger keywords: Step Functions, Fargate, Lambda, S3 event, EventBridge, ECS, ECR, file processing, workflow orchestration, serverless.
Steady49 mentions in 2 weeks
1 project uses a version of this
3.5k3d agoReviewMountCreate a free account to mount
Create and secure S3 buckets following AWS best practices for access control, encryption, monitoring, and remediation of misconfigurations. Use when the user wants to secure a new bucket, audit an existing bucket, fix a security finding, configure encryption, or enable logging and monitoring. Do NOT use for general S3 data operations, S3 Tables setup, or discovering existing data assets.
Steady49 mentions in 2 weeks
1 project uses a version of this
3.5k3d agoReviewMountCreate a free account to mount
Diagnoses and resolves Amazon EFS issues including mount failures, NFS timeouts, permission errors, throughput problems, and burst credit exhaustion. Use when the user has an EFS file system that is not mounting, returning errors, performing slowly, or showing access denied.
Steady49 mentions in 2 weeks
1 project uses a version of this
3.5k3d agoReviewMountCreate a free account to mount
Diagnoses and resolves Amazon S3 Files issues including mount failures, permission errors, synchronization problems, and performance issues. Use when the user has an S3 file system that is not mounting, returning access denied, not syncing changes to S3, showing files in lost+found, or performing slower than expected.
Steady49 mentions in 2 weeks
1 project uses a version of this
3.5k3d agoReviewMountCreate a free account to mount
Runs SQL queries on Amazon Athena query history exported as an Apache Iceberg table in S3 Tables. The query_executions system table captures per-query metadata (query text, IAM principal, work group, statement type, data scanned, timing breakdown, error details, tables accessed, result reuse, engine version) for every completed query. Applies when analyzing Athena usage and cost, finding who ran a query, auditing table access, tracking data scanned by user or work group, investigating slow or failed queries, detecting performance regressions, reporting query history beyond the 45-day API window, or enabling Athena system tables. Prefers the system table over the ListQueryExecutions and GetQueryExecution APIs at scale. Trigger phrases: Athena query history, who ran this query, data scanned by user, most queried tables, slowest queries, failed query analysis, Athena cost by work group, query audit trail, enable Athena system tables.
Steady49 mentions in 2 weeks
No other project uses it yet
3.5k3d agoReviewMountCreate a free account to mount
Enables Redshift system-table (SYS_*) log publishing to S3 Tables in Apache Iceberg format for both Provisioned clusters and Serverless namespaces, verifies publishing status, and queries the published logs via any Iceberg-compatible engine including Redshift and Athena. Covers system tables such as sys_query_history, sys_query_text, sys_connection_log, sys_query_detail, and sys_session_history. Applies when turning on S3 Tables log publishing for a cluster or namespace, confirming publishing status and locating the S3 Tables namespace, querying non-realtime data from Redshift system tables off-cluster at scale, or building dashboards for Redshift monitoring and auditing, especially for historical or high-volume system-table data beyond the in-cluster SYS_ view retention window. Trigger phrases: publish redshift system table log to s3 tables, enable-logging s3 tables, describe redshift logging status, query redshift system tables in athena or redshift, redshift log exports to iceberg.
Steady49 mentions in 2 weeks
No other project uses it yet
3.5k3d agoReviewMountCreate a free account to mount
Queries S3 object metadata, tracks bucket activity, audits object changes, searches annotations, and analyzes storage metrics using S3 Metadata system tables (journal, inventory, annotation) and S3 Storage Lens tables via Athena SQL. Applies when counting objects, finding recent uploads or deletions, identifying who wrote to a prefix, breaking down storage classes, finding objects by tag, searching annotation content, analyzing storage lens metrics, or enabling S3 Metadata tracking. Prefers system tables over raw S3 APIs (list-objects-v2, head-object) at scale. Trigger phrases: bucket activity, object count, who uploaded, track deletions, storage class breakdown, find by tag, search annotations, storage lens metrics, audit bucket changes.
Steady49 mentions in 2 weeks
2 projects use a version of this
3.5k3d agoReviewMountCreate a free account to mount
Runs SQL analytics on SageMaker Catalog asset metadata tables exported as Apache Iceberg in S3 Tables. Covers governance queries, asset growth tracking, ownership audits, time-travel over catalog state, and metadata quality analysis. Applies when querying catalog inventory, finding assets without descriptions, comparing catalog snapshots, or auditing data ownership. Trigger phrases: catalog inventory SQL, how many assets, assets without descriptions, asset growth over time, who owns this data, catalog governance, data quality audit, catalog analytics.
Steady49 mentions in 2 weeks
1 project uses a version of this
3.5k3d agoReviewMountCreate a free account to mount
Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Covers auth (Cognito), data (AppSync/DynamoDB), storage (S3), functions, APIs, and AI (Amplify AI Kit with Bedrock). Supports React, Next.js, Vue, Angular, React Native, Flutter, Swift, and Android. Always use this skill for Amplify Gen2 topics — even for questions you think you know — it contains validated, version-specific patterns that prevent common mistakes. TRIGGER when: user mentions Amplify Gen2; project has amplify/ directory or amplify_outputs; code imports @aws-amplify packages; user asks about defineBackend, defineAuth, defineData, defineStorage, defineFunction, or npx ampx. SKIP: Amplify Gen1 (amplify CLI v6), standalone SAM/CDK without Amplify (use aws-serverless), direct Bedrock without Amplify AI Kit (use bedrock).
Steady49 mentions in 2 weeks
1 project uses a version of this
3.5k3d agoReviewMountCreate a free account to mount
Deploys, hosts, or runs a container or Docker app on Amazon Lightsail Container Service and returns a live, managed HTTPS URL at a flat monthly price — no cluster, VPC, load balancer, or registry to set up. Used when deploying a container image to Lightsail from a local Docker build, a public registry image, or a GitHub repo, or when a Lightsail container deployment fails or won't serve — including when the request doesn't name Lightsail but asks to run one always-on container behind a public URL at a flat, predictable monthly price. Not for running an app on a Lightsail instance (VM) or Amazon EC2 instead of the container service, and not for workloads needing Kubernetes, autoscaling, scale-to-zero, or per-request pricing (use Amazon ECS/EKS or ECS Express Mode).
Steady49 mentions in 2 weeks
No other project uses it yet
3.5k3d agoReviewMountCreate a free account to mount
This is the AWS SDK for Java 2.x: service clients generated at build time from AWS service models, plus the hand-written core runtime, HTTP clients, and high-level libraries they run on. The files under docs/guidelines/ add depth, and each section says when to read one. The Maven reactor has about 500 modules. Run Maven through ./mvnw from the repository root, scoped with -pl to the modules you changed. Files under any target/generated-sources/ directory are regenerated by every build, so an…
2.6k6d agoReviewMountCreate a free account to mount
Guidance for AI coding agents (Cursor, GitHub Copilot, Claude Code, Amazon Q Developer, Kiro, Codex, Gemini CLI, etc.) working in this repository — the source of the Amazon SageMaker Python SDK. Follows the AGENTS.md convention (https://agents.md). This file has two audiences: 1. Contributors' agents editing SDK source, tests, and docs in this repo. 2. Any agent that reads this repo as a reference for how to use the SDK — so the usage guidance (v3 by default) is stated here…
Steady6 mentions in 2 weeks
No other project uses it yet
2.3k3mo agoReviewMountCreate a free account to mount
Guidance for Claude Code working in this repository — the source of the Amazon SageMaker Python SDK. This repository follows the AGENTS.md convention. To keep a single source of truth and avoid the two files drifting apart, all guidance lives in AGENTS.md and is imported here: For the full guidance — project context, the v3-by-default golden rule, banned v2 patterns and their v3 replacements, the SDK-first interface map, the contributing workflow, and a canonical v3 train + deploy example —…
Steady6 mentions in 2 weeks
No other project uses it yet
2.3k3mo agoReviewMountCreate a free account to mount
Guidance for GitHub Copilot working in this repository — the source of the Amazon SageMaker Python SDK. This repository keeps its AI-agent guidance in a single source of truth, AGENTS.md, following the AGENTS.md convention. Copilot instructions do not support file imports, so read AGENTS.md at the repository root and follow it. Key points from that file (see AGENTS.md for the authoritative, complete version): - v3 by default. The current major version is v3 (pip install sagemaker). SDK v3 is a…
Steady6 mentions in 2 weeks
No other project uses it yet
2.3k3mo agoReviewMountCreate a free account to mount
Source repository and documentation for the Amazon SageMaker Python SDK v3. pip install sagemaker installs v3. SDK v3 is modular (sagemaker-core, sagemaker-train, sagemaker-serve, sagemaker-mlops) and is not backward compatible with v2. v2 is on a maintenance branch (security/bug fixes only) and should not be used as a basis for new code. This file follows the llms.txt convention (https://llmstxt.org): a curated index plus explicit instructions so AI coding agents generate correct, current (v3) SDK code. - SDK-first: for any SageMaker task…
Steady6 mentions in 2 weeks
No other project uses it yet
2.3k3mo agoReviewMountCreate a free account to mount
Conventions and safety rules for changing the Amazon.Lambda.Annotations library and its source generator, including the T4 templates that generate Lambda handler code. Use when modifying parameter binding, generated handler code, authorizer support, or the source generator templates.
1.7k37d agoReviewMountCreate a free account to mount
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.