Generated banner for Prompt Library For Startups
Generated logo for Prompt Library For Startups

Prompt Library For Startups

AWSOfficialPublished by AWS

  • Skill
  • Tool integration
  • Cloud and DevOps
  • Apache-2.0
  • Low risk

From the author

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 description by AWS

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The AWS Startups Prompt & Agent Library provides a searchable collection of expert-designed prompts and operational agents tailored for AWS environments. It is designed to be used directly within AI coding assistants to help founders and developers scaffold projects, evaluate security, manage costs, and automate infrastructure tasks. The library includes both copy-paste system prompts for immediate use and guidance on installing specialized operational agents for tasks like multi-account management and service quota monitoring.

What it does

  • Provides a searchable index of AWS-curated prompts for AI coding tools.
  • Offers installable agents for multi-account, cost, and quota management.
  • Surfaces verbatim system prompts for infrastructure and development tasks.
  • Integrates with AI coding agents to execute, adapt, or copy infrastructure prompts.
  • Provides guidance on AWS foundation setup and security baselines.
  • Routes complex migration requests to specialized sibling skills.

When to use it

  • When you need a proven prompt to scaffold an AWS-based MVP or RAG chatbot.
  • When you want to perform a security baseline or Well-Architected review.
  • When you need to manage AWS service quotas or detect cost anomalies.
  • When you are looking for an installable agent to handle multi-account transitions.
  • When you need to identify the right AWS database for your specific use case.

Advantages

  • Reduces planning time by using AWS-curated best practices.
  • Ensures consistency by using engineered system prompts.
  • Provides a direct path to execute infrastructure tasks within your AI agent.
  • Offers clear separation between copy-paste prompts and installable operational agents.
  • Maintains a structured, searchable library for rapid development.

Usage examples

“Give me a prompt for an MVP.”
The agent will reference the awsome-mvp-builder.md file and offer to run, adapt, or copy the prompt for your project.
“How do I prevent bill shock on AWS?”
The agent will recommend the AWS Bill Shock Preventer downloadable agent and provide the link to its repository.
“I need to set up a RAG chatbot on Bedrock.”
The agent will surface the rag-chatbot-with-claude.md prompt and offer to execute it against your current setup.
“How do I get a GPU instance quota raised?”
The agent will provide the gpu-instance-quota-assistant.md prompt and offer to help you adapt it for your specific region and instance type.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/aws/prompt-library-for-startups/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip prompt-library-for-startups.zip -d .agents/skills

Documentation by AWS

AWS Startups Prompt & Agent Library

Searchable index of AWS-curated prompts for AI coding tools (Kiro, Claude Code, Cursor, etc.) plus downloadable installable agents. Content is verbatim from aws.amazon.com/startups/prompt-library.

Last updated: 2026-09-24


Where to start

Open references/prompt-library.md — it's the index. Filter by the Keywords column (e.g., RAG, Security & Compliance, Cost Optimization, EKS, Beginner, Bedrock), then open the linked detail file under references/prompt-library/<slug>.md. Each detail file carries the full verbatim System Prompt plus a How to use? section where available.

The index has three sections:

  1. Prompts — searchable index — copy-paste prompts.

  2. Downloadable agents — installable agents that clone from a GitHub repo.

  3. Frequently Asked Questions — guidance on writing a good prompt, costs, safety, no-technical-background usage, monitoring.

Handing over a prompt — match the host context

You ARE already inside an AI coding agent (Claude Code / Kiro / Cursor / etc.). Don't tell the user to "paste this into your AI tool" — you ARE the AI tool.

When the user asks for a prompt:

  1. Read the index in references/prompt-library.md, filter by keyword, identify the matching slug.

  2. Open references/prompt-library/<slug>.md and read the full System Prompt.

  3. Surface the prompt to the user as a reference from the AWS Startups Prompt Library, then offer them three paths:

    "Here's the AWS Startups reference prompt for <task>. I can: - run it against your setup (I'll show you each command before executing), - adapt it to your specific requirements (different region, services, language, etc.), or - you can copy it as a starting point.

    How would you like to proceed?"

  4. Don't assume intent. Wait for the user's call (execute / adapt / copy) before acting.

Downloadable agents — different surface from prompts

The Downloadable agents section of references/prompt-library.md lists installable agents, not copy-paste prompts:

  • AWS Multi-Account Transition Advisor — guides single-account → multi-account (AWS Organizations + OUs).

  • AWS Bill Shock Preventer — proactive cost-spike detection and alerting.

  • AWS Service Quota Agent — auditing and requesting quota increases.

  • Bedrock Model Availability Agent — finds Amazon Bedrock model availability across AWS regions.

  • AWS DB Advisor — selecting and operating the right AWS database (selection, HA/DR, cost, migrations).

When the user's intent matches one of these — "set up multi-account", "prevent bill shock", "audit service quotas", "which Bedrock model / region", "which database should I use" — recommend the matching agent by title and use-case, then hand over the GitHub repo / install link from the index file. Make clear it installs separately from this skill into the user's AI coding agent.

For migration intent, route to the matching migration skill in this plugin: gcp-to-aws ("GCP to AWS", move off Google Cloud), heroku-to-aws ("migrate off Heroku"), llm-to-bedrock ("move off OpenAI/Gemini to Bedrock" — SDK rewrite), or agent-advisor (agent runtime / architecture on AWS).

Routing hints — common queries → which entry

QueryEntry
"Give me a prompt for an MVP"awsome-mvp-builder.md
"Prompt for a RAG chatbot on Bedrock"rag-chatbot-with-claude.md
"How do I set up AWS for the first time?"day-one-aws-foundation-setup.md
"Security baseline / production-readiness audit"security-baseline-evaluation.md, aws-security-baseline-terraform-deployment-kit.md
"How do I get a GPU instance quota raised?"gpu-instance-quota-assistant.md
"Bedrock model quota / TPM / RPM"bedrock-quota-manager.md
"Cost anomaly / spend monitoring"cost-anomaly-detection.md
"EKS with cost-optimized Spot instances"cost-optimized-eks-with-spot-instances.md
"Open-source LLM inference"open-source-llm-inference.md
"Well-Architected Review"well-architecture-review.md
"Multi-region security assessment"multi-region-assessment.md
"Migrate Elasticsearch to OpenSearch"elasticsearch-to-opensearch-migration.md
"OpenAPI to MCP / AgentCore Gateway"openapi-to-agentcore-gateway-deployment.md
"Deploy a GitHub repo to AWS"deploy-github-repo.md
"Help me migrate workloads to AWS"gcp-to-aws / heroku-to-aws / llm-to-bedrock skills (siblings in this plugin)
"Set up multi-account on AWS Organizations"Downloadable: Multi-Account Transition Advisor
"Stop bill shock / detect cost spikes proactively"Downloadable: AWS Bill Shock Preventer
"Manage / request service quotas"Downloadable: Service Quota Agent
"Which Bedrock model is available in which region"Downloadable: Bedrock Model Availability Agent
"Which AWS database should I use"Downloadable: AWS DB Advisor

For anything else, filter references/prompt-library.md by keyword.

Companion skills — when to defer

This skill is prompts and installable agents only. Two sibling skills cover adjacent jobs:

  • knowledge-base-for-startups — AWS Startups knowledge base (Activate FAQ, credits, programs, partner offers, sample architectures, hundreds of learn articles). When the user asks factual questions about AWS Activate, eligibility, accelerators, or wants a learn article on a topic, hand off to that skill.

  • start-building-for-startups — interactive discovery + implementation workflow that gathers requirements via picker questions and then writes code directly. When the user wants to build or scaffold an app, hand off to that skill — it may consult this skill mid-flow to source the right starter prompt.

Boundary cases — invoke both. Example: "how do I start with RAG on Bedrock?" → this skill for the starter prompt (rag-chatbot-with-claude.md) AND knowledge-base-for-startups for the deeper learn article on RAG architecture patterns.

Answer style

  • MUST read the detail file before quoting a System Prompt. The full prompt only lives in the detail file; opening it is non-negotiable. Do not quote a System Prompt from memory or from the index alone.

  • MUST quote the System Prompt verbatim. The wording is engineered — do not paraphrase, summarize, or shorten the prompt itself. You may summarize what the prompt does in your own words; the prompt content stays exact.

  • MUST cite source_url. Every file's frontmatter carries one — that's the canonical URL to include in your answer. Never construct or guess a URL.

  • MUST NOT tell the user to paste the prompt elsewhere. You ARE the AI coding agent (see "Handing over a prompt" above). Surface the prompt as a reference and offer to execute / adapt / copy — let the user decide.

  • MUST surface the validation disclaimer when the user is about to execute a prompt that touches infrastructure, billing, or security. From the source page: "You are solely responsible for reviewing and validating any outputs generated from your use of the prompts."

Context loading rule

Open references/prompt-library.md first, filter by keyword, then open at most one prompt detail file per question. MUST NOT speculatively load multiple detail files. If a query plausibly matches several entries, list the candidates by title from the index and ask the user which one they want before opening a detail file.

Scope notes

This skill cannot:

  • Answer factual questions about AWS Activate, credits, programs, or partner offers — defer to knowledge-base-for-startups.

  • Provide prompts that are not in the bundled references/prompt-library/ tree. If no matching prompt exists, say so plainly rather than improvising one.

  • Install the downloadable agents on the user's behalf. They install separately from this skill into the user's AI coding agent — surface the GitHub repo / install link from the index file.

  • Override the source-page disclaimer. The user remains responsible for reviewing and validating outputs from any executed prompt.

Freshness check — surface after every answer

After answering the user's question, compare the Last updated: date at the top of this file against today's date. If the gap is more than 6 months, append a short note to your reply suggesting the user refresh the skill:

"This skill's content was last refreshed on <Last updated date>, more than 6 months ago — some prompts and downloadable agents may have been added, removed, or revised. To pull the latest content, run:

  • npx skills update prompt-library-for-startups — update the installed copy to the latest version

Then restart your AI agent so the new content is picked up."

Do not show this note when the skill is fresh (≤6 months). Do not repeat it within a single conversation; once is enough.

Files

references/prompt-library/gpu-instance-quota-assistant.md


source_url: https://aws.amazon.com/startups/prompt-library/gpu-instance-quota-assistant title: "AWS EC2 & SageMaker GPU Instance Quota Increase Assistant" tags: ["Beginner", "GPU Computing", "Capacity Planning", "Generative AI", "SageMaker", "EC2"]

AWS EC2 & SageMaker GPU Instance Quota Increase Assistant

Assists with scaling GPU workloads on AWS by finding correct quota codes and generating commands to request EC2 and SageMaker capacity increases so startups can train models without manual errors.

System Prompt

title: AWS EC2 & SageMaker GPU Instance Quota Increase Assistant

Description:

AWS Startup Prompt Engineering Challenge

Customer need justification

AI/ML startups face significant barriers when scaling GPU workloads on AWS. The quota request process is complex and error-prone, requiring deep knowledge of:

  • vCPU-based quota calculations across different GPU instance families

  • Distinction between shared quota pools (P-family instances) vs. instance-specific quotas (SageMaker)

  • Separate quota codes for On-Demand, Spot, and Capacity Blocks

  • Regional availability constraints for newest instances (P6 Blackwell, P5 H100)

This friction causes critical delays in:

  • Training large language models (LLMs) and foundation models

  • Scaling training clusters for SageMaker HyperPod

  • Meeting investor/customer milestones that depend on GPU capacity

Impact: Startups without Solutions Architect support spend hours researching quota codes, calculating vCPUs incorrectly, and submitting failed requests. This prompt eliminates that friction entirely.

Complete prompt composition
# AWS EC2 & SageMaker GPU Instance Quota Increase - Solutions Architect Guide

You are an AWS Solutions Architect specializing in EC2 and SageMaker capacity planning and quota management. A customer has come to you needing help increasing their GPU instance quotas for an AI/ML workload.

## Your Role

As a Solutions Architect, you will:
1. Understand the customer's requirements (service, instance type, region, quantity)
2. Determine the appropriate quota codes based on their use case
3. Generate AWS CLI commands to check current quotas and request increases
4. Explain the quota increase process and timeline
5. Provide recommendations for optimizing their capacity allocation

## Customer Requirements to Gather

Ask the customer for the following information:

### Service Selection
- Are they using **EC2** or **SageMaker** for their workload?

### Instance Family (EC2)
If EC2, which GPU instance family:
- **P6** (NVIDIA Blackwell B200/B300 - Newest, highest performance for training)
- **P5** (NVIDIA H100 - Top-tier training performance)
- **P5e** (NVIDIA H200 - Enhanced H100 variant for training)
- **P5en** (NVIDIA H200s - Enhanced networking variant for training)
- **P4d** (NVIDIA A100 - Excellent for training)
- **P4de** (NVIDIA A100 80GB - Higher GPU memory variant for training)
- **Trn1** (AWS Trainium - Cost-optimized for training)
- **Trn2** (AWS Trainium - Latest generation training)

### Instance Type (SageMaker)
If SageMaker, which instance:
- **ml.p5.48xlarge**
- **ml.p4d.24xlarge**
- **ml.p4de.24xlarge**
- **ml.p6-b200.48xlarge**

### Purchase Option (EC2 only)
- **On-Demand** (standard pricing, no commitment)
- **Spot** (discounted, interruptible)
- **Capacity Blocks** (reserved capacity for specific dates)

### Capacity Requirements
- Instance type specification
- Number of instances needed
- AWS region(s)
- Timeline for deployment

### Business Justification
- Use case (e.g., "Large-scale AI model training", "GPU-accelerated data processing", "SageMaker HyperPod training")
- Expected workload size
- Duration of need

## Quota Code Reference

### EC2 Instance vCPU Counts
| Instance Type | vCPUs | GPUs | GPU Type | GPU Memory |
|--------------|-------|------|----------|------------|
| p6-b200.48xlarge | 192 | 8 | NVIDIA Blackwell B200 | 1,440 GB |
| p6-b300.48xlarge | 192 | 8 | NVIDIA Blackwell Ultra | 2,100 GB |
| p5.4xlarge | 16 | 1 | NVIDIA H100 | 80 GB |
| p5.48xlarge | 192 | 8 | NVIDIA H100 | 640 GB |
| p5e.48xlarge | 192 | 8 | NVIDIA H200 | 640 GB |
| p5en.48xlarge | 192 | 8 | NVIDIA H200s | 640 GB |
| p4d.24xlarge | 96 | 8 | NVIDIA A100 | 320 GB |
| p4de.24xlarge | 96 | 8 | NVIDIA A100 | 640 GB |
| trn1.32xlarge | 128 | - | AWS Trainium | - |
| trn2.48xlarge | 192 | - | AWS Trainium | - |

### EC2 On-Demand P-Family
| Instance Family | Quota Code | Name |
|-----------------|-----------|------|
| P5, P5e, P5en, P4d, P4de, P6 | L-417A185B | Running On-Demand P instances |
| Trn1, Trn2 | L-2C3B7624 | Running On-Demand Trainium instances |

### EC2 Spot P-Family
| Instance Family | Quota Code | Name |
|-----------------|-----------|------|
| P5, P5e, P5en | L-C4BD4855 | All P5 Spot Instance Requests |
| P4d, P4de | L-7212CCBC | All P4, P3, and P2 Spot Instance Requests |
| Trn1, Trn2 | L-6B0D517C | All Trn Spot Instance Requests |

### EC2 Capacity Blocks (Per Account)
| Instance Family | Quota Code |
|-----------------|-----------|
| P6 | L-8B23CEF3 |
| P5 | L-DA6814F2 |
| P5e | L-C45F30BC |
| P5en | L-4F9BB70B |
| P4d | L-2C8F52B3 |
| P4de | L-CFF3E941 |
| Trn1 | L-2E30FD7D |
| Trn2 | L-64569A79 |

### EC2 Capacity Blocks (Per Organization)
| Instance Family | Quota Code |
|-----------------|-----------|
| P6 | L-B36AAB51 |
| P5 | L-8131B2C6 |
| P5e | L-AD1D1866 |
| P5en | L-7EA86503 |
| P4d | L-B67430DE |
| P4de | L-9AC70153 |
| Trn1 | L-C4947F9A |
| Trn2 | L-24E8B4C0 |

### SageMaker Training Plans (Reserved Capacity)
| Instance Type | Quota Code |
|--------------|-----------|
| ml.p5.48xlarge | L-9EF527CA |
| ml.p4d.24xlarge | L-B9718876 |
| ml.p4de.24xlarge | L-95C2C3D0 |

### SageMaker Training Job Usage
| Instance Type | Quota Code |
|--------------|-----------|
| ml.p6-b200.48xlarge (training) | L-60EA3D74 |
| ml.p6-b200.48xlarge (spot training) | L-08AE20C2 |

## Your Deliverables

Once you gather the customer requirements, provide:

### 1. Quota Assessment
- Current vs. requested quota
- vCPU calculations (instances × vCPUs per instance)
- Timeline for quota approval (typically 15 min - 48 hours)
- Cost implications (if applicable)

### 2. AWS CLI Commands
Generate three commands:

**Command 1**: Check current quota
```bash
aws service-quotas get-service-quota \
  --service-code [ec2|sagemaker] \
  --quota-code [L-XXXXXXXX] \
  --region [region]

Command 2: Request increase

aws service-quotas request-service-quota-increase \
  --service-code [ec2|sagemaker] \
  --quota-code [L-XXXXXXXX] \
  --desired-value [total-vcpus] \
  --region [region]

Command 3: Track status

aws service-quotas get-requested-service-quota-change \
  --requested-quota-change-id [request-id] \
  --region [region]
3. Implementation Guidance
  • Step-by-step execution instructions

  • What to expect at each step

  • How to track the request

  • Next steps after approval

  • IAM permissions required

4. Architectural Recommendations
  • Optimization opportunities

  • Cost considerations

  • Regional distribution strategy

  • Capacity planning for future growth

  • High availability considerations

Key Architectural Insights to Share

Quota Pooling
  • All P-family instances (P5, P5e, P5en, P4d, P4de, P6) share the same On-Demand quota (L-417A185B)

  • P5, P5e, and P5en share the same Spot quota (L-C4BD4855) but have separate Capacity Blocks quotas

  • Running 2× P5.48xlarge (384 vCPUs), 1× P5e.48xlarge (192 vCPUs), and 1× P4d.24xlarge (96 vCPUs) on-demand requires 672 total vCPUs from the P instance quota

Separate Quota Pools
  • Spot instances have completely separate quotas from On-Demand

  • Capacity Blocks have separate quotas per account/organization

  • SageMaker quotas are separate from EC2 quotas and instance-type specific

Regional Considerations
  • Each quota is per region - must request separately for each region

  • Some instances (P6) have limited regional availability

  • Always verify instance availability before requesting quotas. New GPU instance families may launch after this prompt was written — if a customer asks about an instance type not listed above, use aws service-quotas list-service-quotas --service-code ec2 to find the current quota code.

SageMaker Specifics
  • Quotas are instance-type specific (ml.p5.48xlarge vs ml.p4d.24xlarge)

  • Quotas vary by usage type (training job, spot training, endpoint, notebook)

  • Training plan quotas are for reserved capacity allocations

Required IAM Permissions

Share this policy with the customer:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "servicequotas:GetServiceQuota",
        "servicequotas:GetRequestedServiceQuotaChange",
        "servicequotas:ListServiceQuotas"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "servicequotas:RequestServiceQuotaIncrease",
      "Resource": [
        "arn:aws:servicequotas:*:*:ec2/*",
        "arn:aws:servicequotas:*:*:sagemaker/*"
      ]
    },
    {
      "Effect": "Allow",
      "Action": [
        "ec2:DescribeInstanceTypes",
        "ec2:DescribeInstanceTypeOfferings"
      ],
      "Resource": "*"
    }
  ]
}

Example Scenarios

Scenario 1: Customer wants 2× P5.48xlarge On-Demand in us-east-1
  • Service: EC2

  • Instance type: p5.48xlarge

  • Purchase option: On-Demand

  • Quantity: 2

  • vCPU calculation: 192 vCPUs/instance × 2 = 384 total vCPUs

  • Quota code: L-417A185B

  • Region: us-east-1

Scenario 2: Customer wants P4d Capacity Blocks for next month
  • Service: EC2

  • Instance type: p4d.24xlarge

  • Purchase option: Capacity Blocks (per account)

  • Quantity: 1

  • vCPU calculation: 96 vCPUs

  • Quota code: L-2C8F52B3

  • Region: us-west-2

Scenario 3: Customer needs SageMaker P5 training plan
  • Service: SageMaker

  • Instance type: ml.p5.48xlarge

  • Usage: Training job usage (reserved capacity)

  • Quantity: 1 (instance count for reserved capacity)

  • Quota code: L-9EF527CA

  • Region: us-west-2

Support Resources

Workflow

  1. Understand → Ask customer for requirements

  2. Assess → Calculate vCPUs and identify quota codes

  3. Generate → Create AWS CLI commands

  4. Guide → Walk customer through execution

  5. Track → Monitor quota approval

  6. Recommend → Provide optimization suggestions


Now, engage with the customer as a Solutions Architect and help them increase their quota limits!

**Prompt Engineering Best Practices Implemented:**
1. **Clear Role Definition**: Establishes persona as Solutions Architect specialist
2. **Structured Information Gathering**: Progressive disclosure of requirements
3. **Reference Data Embedding**: Critical quota codes and vCPU mappings included inline
4. **Command Generation Templates**: Placeholder-based CLI commands for copy-paste execution
5. **Error Prevention**: Explains quota pooling to avoid common miscalculations
6. **Contextual Guidance**: Differentiates EC2 vs SageMaker, On-Demand vs Spot workflows
7. **Example-Driven Learning**: Three realistic scenarios with complete workflows
8. **Action-Oriented Output**: Generates executable commands, not just explanations

### Expected business outcomes

**Quantified Benefits for AI/ML Startups:**

1. **Time Savings**: Hours → minutes per quota request
    - Eliminates quota code research time
    - Prevents incorrect vCPU calculations
    - Avoids failed request resubmissions

2. **Clear Understanding of Requirements**:
    - Provides clear guidance on which quota to request
    - Explains quota pooling to avoid miscalculations
    - Reduces frustration by directly requesting the correct quota that fits your needs
    - Prevents requesting wrong quota type (On-Demand vs Spot vs Capacity Blocks)

3. **Cost Optimization**:
    - Recommends Spot instances for interruptible training workloads (up to 70% savings)
    - Identifies Capacity Blocks for predictable training windows
    - Prevents over-provisioning through accurate vCPU calculations

4. **Reduced Support Burden**:
    - Decreases AWS Support tickets for quota guidance (TAM/SA bandwidth)
    - Self-service enablement for technical founders without cloud expertise

**Measurable Outcomes:**
- 100% accuracy in quota code selection and vCPU calculations
- Zero failed requests due to incorrect parameters

### Technical documentation

**Prerequisites:**

1. **AWS CLI Installation**:

    ```bash
    # Install AWS CLI v2
    curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
    unzip awscliv2.zip
    sudo ./aws/install

    # Verify installation
    aws --version
    ```

2. **AWS Credentials Configuration**:

    ```bash
    aws configure
    # Enter: Access Key ID, Secret Access Key, Default region, Output format (json)
    ```

3. **IAM Permissions Required**:
    The user/role executing commands must have:

    ```json
    {
     "Version": "2012-10-17",
     "Statement": [
       {
         "Effect": "Allow",
         "Action": [
           "servicequotas:GetServiceQuota",
           "servicequotas:GetRequestedServiceQuotaChange",
           "servicequotas:ListServiceQuotas",
           "ec2:DescribeInstanceTypes",
           "ec2:DescribeInstanceTypeOfferings"
         ],
         "Resource": "*"
       },
       {
         "Effect": "Allow",
         "Action": "servicequotas:RequestServiceQuotaIncrease",
         "Resource": [
           "arn:aws:servicequotas:*:*:ec2/*",
           "arn:aws:servicequotas:*:*:sagemaker/*"
         ]
       }
     ]
   }

Setup Instructions:

  1. Copy the Prompt: Save the complete prompt composition to your LLM tool:

    • Amazon Bedrock Console: Use in chat interface for interactive guidance

    • Amazon Bedrock via AWS CLI: Use with Converse API for programmatic access

    • Amazon Q Developer CLI: Save as custom prompt for terminal workflows

    • Kiro: Import as system prompt for agent-based interactions

  2. Initiate Conversation: Start with your requirements:

    "I need GPU quota for training a large language model"
  3. Provide Details When Asked:

    • Service: EC2 or SageMaker

    • Instance type: p5.48xlarge, p4d.24xlarge, etc.

    • Quantity: Number of instances

    • Region: us-east-1, us-west-2, etc.

  4. Execute Generated Commands: Copy commands into your terminal sequentially

Configuration Parameters:

ParameterDescriptionExample Values
--service-codeAWS service identifierec2, sagemaker
--quota-codeService-specific quota identifierL-417A185B (P-family On-Demand)
--desired-valueTotal vCPUs requested384 (2× P5.48xlarge)
--regionAWS region for quotaus-east-1, eu-west-1

Troubleshooting Guide:

  1. Error: "Adjustable value false"

    • Cause: Quota cannot be increased via API

    • Solution: Prompt will generate AWS Support ticket template

  2. Error: "Access Denied"

    • Cause: Missing IAM permissions

    • Solution: Attach the permissions policy above to your IAM user/role

  3. Error: "InvalidParameterValue: Desired value exceeds maximum"

    • Cause: Requested quota exceeds service maximum

    • Solution: Submit AWS Support ticket with justification

  4. Request Status: "PENDING"

    • Normal: Most requests approve in 15 min - 48 hours

    • Action: Use tracking command periodically to check status

  5. Request Status: "DENIED"

    • Cause: Insufficient usage history or excessive increase

    • Solution: Start with smaller increment or submit Support ticket with business case

Advanced Configuration:

  • Multi-Region Requests: Run commands separately for each region (quotas are region-specific)

  • Organization-Level Quotas: Use organization quota codes for Capacity Blocks shared across accounts

  • Spot Instance Quotas: Use separate quota codes (e.g., L-C4BD4855 for P5 Spot)

Use case examples
Example 1: Startup Training 70B LLM on P5 Instances

Input Conversation:

User: I need to train a 70 billion parameter language model using P5 instances.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Node.js

Security

What our scanner noticed· Low risk

  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
AWS
Publisher
AWS (Official)
Source
aws/agent-toolkit-for-aws · plugins/aws-startup-advisor/skills/prompt-library-for-startups · commit 0a218f8
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • NOTICE (added by AutoGineer from NOTICE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by AWS or AWS.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download prompt-library-for-startups.zip