Results for “aws”

AWS-curated copy-paste prompts for AI coding agents (MVP scaffolding, RAG chatbot with Claude on Bedrock, security baseline evaluation, cost anomaly detection, GPU quota requests, EKS deployment, Well-Architected review, etc.) plus downloadable installable agents (Multi-Account Transition Advisor, Bill Shock Preventer, Service Quota Agent, Bedrock Model Availability Agent, AWS DB Advisor). Use when the user asks for a prompt to do X on AWS, wants an installable agent for multi-account / cost monitoring / quota management / Bedrock model availability / database selection, or asks how to use AWS prompts. For migration intent (GCP to AWS, Azure to AWS, OpenAI/Gemini to Bedrock), route to the migration skills in this plugin (`gcp-to-aws`, `azure-to-aws`, `heroku-to-aws`, `llm-to-bedrock`). Do not use for: factual AWS Activate / programs / credits questions, learn articles, sample architectures, or for prompts that are not in the bundled `references/prompt-library/` tree.

The English summary is being prepared. Showing the original description.

Provides advanced AWS CLI patterns for managing EC2, Lambda, S3, DynamoDB, RDS, VPC, IAM, and CloudWatch. Generates bulk operation scripts, automates cross-service workflows, validates security configurations, and executes JMESPath queries for complex filtering. Triggers on "aws cli help", "aws command line", "aws scripting", "aws automation", "aws batch operations", "aws bulk operations", "aws cli pagination", "aws multi-region", "aws profiles", "aws cli troubleshooting".

The English summary is being prepared. Showing the original description.

AWS Advisor workflow skill. Use this skill when the user needs Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway, or any AWS service. Do NOT use for non-AWS cloud providers or general infrastructure without AWS context and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

The English summary is being prepared. Showing the original description.

Manage AWS infrastructure as TypeScript code with SST v4 and Pulumi. Guides resource creation, connections between services, infrastructure tests, deployment checks, troubleshooting, and resource migrations while accounting for existing project conventions.

• Adding AWS resources to an SST v4 application
• Connecting resources and reviewing access permissions
• Adding infrastructure tests and reviewing deployment changes

Configure and audit AWS users, roles, and access policies. Work through least-privilege permissions, granting only the access needed, along with GitHub Actions authentication, cross-account access, permission boundaries, and checks for unused or excessive access.

• Create execution roles for EC2 and Lambda
• Design policies with only the required permissions
• Configure GitHub Actions authentication through OIDC

Review AWS spending and identify savings through resource sizing, unused resource cleanup, discount commitments, and storage policies. It also guides budget alerts and recurring cost reviews so teams can track spending and plan changes using usage data.

• Investigating an unexpected AWS bill increase
• Preparing cost reviews with engineering and finance
• Comparing Savings Plans and Reserved Instances

Store database credentials and API keys in AWS Secrets Manager, configure automatic credential changes, and connect applications to stored secrets. Follow examples for access policies, Lambda rotation functions, and integration with ECS and EKS.

• Move hardcoded credentials into AWS Secrets Manager
• Configure automatic database credential rotation
• Provide stored secrets to ECS and EKS workloads

Estimate AWS costs before deployment, analyze spending trends, and investigate metrics and logs with CloudWatch. The skill guides cost reviews, alert setup, and operational improvements through connected tools, with additional integrations for audits and security assessments.

• Estimating monthly AWS costs before deployment
• Investigating unexpected charges and spending trends
• Setting up CloudWatch alarms and investigating logs

Design and configure an AWS VPC, a private cloud network, with separate public, application, and database subnets. Covers traffic routing, access rules, private service connections, and troubleshooting connectivity between resources.

• Build separate networks for production and development
• Separate public, application, and database resources
• Connect VPCs or access AWS services privately

Set up AWS CloudTrail to record activity across accounts, protect audit logs, and alert on sensitive operations. Includes guidance for querying past events with Athena or CloudTrail Lake and checking log integrity during investigations.

• Set up audit logging across AWS accounts
• Investigate suspicious API activity
• Configure alerts for sensitive operations

Analyze AWS infrastructure definitions, deployed resources, usage metrics, and actual costs to identify savings opportunities. Rank recommendations by savings, risk, and effort, then create individual GitHub issues and a coordinating issue after approval.

• Identify underused AWS resources
• Estimate monthly savings from configuration changes
• Prioritize cost reductions by risk and implementation effort

Analyze AWS IAM access policies with boto3 and Cloudsplaining-style checks to find permissions that could grant greater access. Produces a JSON report linking risky permissions to users or roles, with severity ratings and remediation guidance.

• Audit AWS IAM policies for excessive permissions
• Find permission combinations that enable privilege escalation
• Trace risky policies to affected users and roles

Check AWS S3 buckets and IAM roles against documented compliance rules. Identify public exposure, missing tags, and overly broad permissions, trace changes through audit logs, and prepare remediation requests for human review without applying fixes.

• Running daily checks for AWS policy violations
• Reviewing bucket exposure, tags, and role permissions
• Tracing who changed a resource and when

Assess AWS, Azure, and GCP environments by identifying identities, permissions, and paths to broader access or data exposure. Covers cloud storage, secrets, cross-account trust, and CI/CD, the automated systems used to build and deploy software.

• Planning an AWS, Azure, or GCP security assessment
• Tracing privilege escalation from current permissions
• Reviewing CI/CD credentials and OIDC trust settings

Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow. Triggers on: which runtime for my agent, AgentCore vs ECS vs EKS vs Lambda, AgentCore vs Lambda MicroVMs, deploy an AI agent on AWS, agent architecture on AWS, I have an agent idea what do I build, move/migrate my agents to AWS, agent migration plan, add AgentCore services (memory, gateway, identity, policy, observability) to an agent already on AWS, Temporal on AWS (migrate/run Temporal workers on AWS, a service orchestrated by Temporal, Temporal Cloud vs self-hosted). Temporal Workflow code is never rewritten into Step Functions. Requires at least one agentic component — a purely non-agent system (plain services, batch jobs, HTTP endpoints, non-agent Temporal Activities) is out of scope, redirected to gcp-to-aws / heroku-to-aws / llm-to-bedrock. Not for: compute/data migration with no AI agent; pure LLM SDK rewrite (use llm-to-bedrock); per-model pricing.

The English summary is being prepared. Showing the original description.

Startup-tailored AWS architecture advice for non-agent workloads, adjusted to the company's stage (pre-revenue through Series B+), team size, runway, and credits. Not for AI agents: deploying an AI agent on AWS, picking its runtime, or any agentic architecture is agent-advisor. Use when a founder wants guidance or a recommendation rather than code changes: which services to choose, how to plan or review an architecture, how to stretch credits and control cost, or how to prepare architecture for a fundraise or technical diligence. For an interactive discovery flow that scaffolds and writes the architecture into the codebase, use start-building-for-startups. Do not use for: writing or scaffolding code, factual AWS Activate / programs / credits lookups (see knowledge-base-for-startups), a single copy-paste prompt (see prompt-library-for-startups), or migration intent such as GCP-to-AWS, Azure-to-AWS, or Heroku-to-AWS (see the migration skills: `gcp-to-aws`, `azure-to-aws`, `heroku-to-aws`, `llm-to-bedrock`).

The English summary is being prepared. Showing the original description.

Gets AWS credentials for CLI/SDK access via `aws login`. Activates when a developer needs to authenticate to AWS for local development, when an AWS operation fails due to missing or expired credentials, or when someone asks about setting up AWS access. Triggers: "set up AWS", "configure AWS", "aws login", "get credentials", "authenticate", "session expired", "token expired", "no credentials", "AccessDeniedException" with no configured credentials.

The English summary is being prepared. Showing the original description.

Design AWS applications that run without managing servers and respond to events. Get guidance on Lambda APIs, asynchronous workflows, retries, monitoring, and scaling, with implementation patterns based on the AWS Well-Architected Framework.

• Designing APIs backed by Lambda
• Building asynchronous job processing
• Coordinating services with Step Functions

Support authorized penetration testing of AWS environments by examining IAM permissions and resources such as S3, EC2, and Lambda. It guides identifying privilege escalation paths, where access can be expanded, and documenting security audit findings.

• Review IAM permissions for privilege escalation paths
• Assess access to S3 buckets and Lambda functions
• Validate credential exposure risks through EC2 metadata

Build voice skills for Amazon Alexa and plan an assistant that uses Claude for its intelligence. Covers integration with AWS services including Lambda, DynamoDB, Polly, Transcribe, and Lex, as well as Smart Home.

• Developing voice skills for Amazon Alexa
• Building an Alexa assistant that uses Claude
• Planning Alexa integrations with AWS services

Build automated responses to AWS GuardDuty security findings using EventBridge and Lambda. Configure severity filters, isolate EC2 instances, disable compromised access keys, preserve disk snapshots for investigation, and send notifications to security teams.

• Triggering responses to high-severity GuardDuty findings
• Isolating EC2 instances and preserving investigation data
• Disabling compromised IAM access keys

Create and refine draw.io diagrams by editing XML files, adjusting labels, arrows, and spacing, and using AWS icons. Export transparent PNG images for slides, with guidance for readable Japanese text and consistent layouts.

• Create an AWS architecture diagram
• Fix Japanese labels and overlapping arrows
• Export transparent PNG diagrams for slides

Operate a live AWS workload with AWS DevOps Agent — incident investigation, root-cause analysis, and release-readiness review — for startups with no dedicated DevOps or SRE engineer. Use when a live AWS workload is misbehaving (production is down, 5xx errors, latency spike, timeouts, it broke after the last deploy, an alarm fired, a pasted CloudWatch alarm or stack trace, find the root cause, write a postmortem, no one on call), for pre-merge review (is this PR safe to ship, blast radius), or to set up, pause, stop, or check the cost of AWS DevOps Agent. Detects existing setup first and never re-onboards. Cost, account access, and code egress are each disclosed in one line with safe defaults: cost and access proceed, code egress stays off unless asked. Do not use for: new architecture (architect-for-startups), scaffolding (start-building-for-startups), migrations (gcp-to-aws, azure-to-aws, heroku-to-aws, llm-to-bedrock), or general Activate and credits questions (knowledge-base-for-startups).

The English summary is being prepared. Showing the original description.

Discover the user's local AWS context (active profile, region, account ID, caller identity) at the start of any AWS task. Use this skill before any other AWS work — deploying to SageMaker, creating resources, calling AWS APIs, or anything that touches an AWS account. Use it especially when the user has not specified a region or profile explicitly, when they say things like "use my AWS account", "deploy to AWS", "use my profile", or when about to make any AWS CLI or SDK call. Never guess the region or account ID — always use this skill to read it from the local configuration first.

The English summary is being prepared. Showing the original description.