Check AWS resource availability across regions for products (service and features), APIs, and CloudFormation resources.

Quick Reference

• Maximum 10 regions per call (split into multiple calls for more regions)

• Single region: filters optional, supports pagination

• Multiple regions: filters required, no pagination, queries run concurrently

• Status values: 'isAvailableIn' | 'isNotAvailableIn' | 'isPlannedIn' | 'Not Found'

• Response field: 'products' (product), 'service_apis' (api), 'cfn_resources' (cfn)

When to Use

1. Pre-deployment Validation

   • Verify resource availability before deployment

   • Prevent deployment failures due to regional restrictions

   • Validate multi-region architecture requirements

2. Architecture Planning

   • Design region-specific solutions

   • Plan multi-region deployments

   • Compare regional capabilities

Examples

Check specific resources in one region:

regions=["us-east-1"], resource_type="product", filters=["AWS Lambda"]
regions=["us-east-1"], resource_type="api", filters=["Lambda+Invoke", "S3+GetObject"]
regions=["us-east-1"], resource_type="cfn", filters=["AWS::Lambda::Function"]

Compare availability across regions:

regions=["us-east-1", "eu-west-1"], resource_type="product", filters=["AWS Lambda"]

Explore all resources (single region only, with pagination handling support via next_token due to large output):

regions=["us-east-1"], resource_type="product"

Follow up with next_token from response to get more results.

Response Format

Single Region: Flat structure with optional next_token. Example:

{"products": {"AWS Lambda": "isAvailableIn"}, "next_token": null, "failed_regions": null}

Multiple Regions: Nested by region. Example:

{"products": {"AWS Lambda": {"us-east-1": "isAvailableIn", "eu-west-2": "isAvailableIn"}}, ...}

Filter Guidelines

The filters must be passed as an array of values and must follow the format below.

1. Product - service and feature (resource_type='product') Format: 'Product' Example filters:

   • ['Latency-Based Routing', 'AWS Amplify', 'AWS Application Auto Scaling']

   • ['PrivateLink Support', 'Amazon Aurora']

2. APIs (resource_type='api') Format: to filter on API level 'SdkServiceId+APIOperation' Example filters:

   • ['Athena+UpdateNamedQuery', 'ACM PCA+CreateCertificateAuthority', 'IAM+GetSSHPublicKey'] Format: to filter on SdkService level 'SdkServiceId' Example filters:

   • ['EC2', 'ACM PCA']

3. CloudFormation (resource_type='cfn') Format: 'CloudformationResourceType' Example filters:

   • ['AWS::EC2::Instance', 'AWS::Lambda::Function', 'AWS::Logs::LogGroup']

Retrieve a list of all AWS regions.

Usage

This tool provides information about all AWS regions, including their identifiers and names.

When to Use

• When planning global infrastructure deployments

• To validate region codes for other API calls

• To get a complete AWS regional inventory

Result Interpretation

Each region result includes:

• region_id: The unique region code (e.g., 'us-east-1')

• region_long_name: The human-friendly name (e.g., 'US East (N. Virginia)')

Common Use Cases

1. Infrastructure Planning: Review available regions for global deployment

2. Region Validation: Verify region codes before using in other operations

3. Regional Inventory: Get a complete list of AWS's global infrastructure

Fetch and convert AWS related documentation pages to markdown format.

Usage

This tool reads documentation pages concurrently and converts them to markdown format. Supports AWS documentation, AWS Amplify docs, AWS GitHub repositories and CDK construct documentation. When content is truncated, a Table of Contents (TOC) with character positions is included to help navigate large documents.

Best Practices

• Batch 2-5 requests when reading multiple pages or jumping to different sections of the same document

• Use single request for initial TOC fetch (small max_length) or when evaluating content before deciding next steps

• Use TOC character positions to jump directly to relevant sections

• Stop early once you find the needed information

Request Format

Each request must be an object with:

• url: The documentation URL to fetch (required)

• max_length: Maximum characters to return (optional, default: 10000 characters)

• start_index: Starting character position (optional, default: 0)

For batching you can input a list of requests.

Example Request

{
 "requests":
 [
     {
         "url": "https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-management.html",
         "max_length": 5000,
         "start_index": 0
     },
     {
         "url": "https://repost.aws/knowledge-center/ec2-instance-connection-troubleshooting"
     }
 ]
}

URL Requirements

Allow-listed URL prefixes:

• docs.aws.amazon.com

• aws.amazon.com

• repost.aws/knowledge-center

• docs.amplify.aws

• ui.docs.amplify.aws

• github.com/aws-cloudformation/aws-cloudformation-templates

• github.com/aws-samples/aws-cdk-examples

• github.com/aws-samples/generative-ai-cdk-constructs-samples

• github.com/aws-samples/serverless-patterns

• github.com/awsdocs/aws-cdk-guide

• github.com/awslabs/aws-solutions-constructs

• github.com/cdklabs/cdk-nag

• constructs.dev/packages/@aws-cdk-containers

• constructs.dev/packages/@aws-cdk

• constructs.dev/packages/@cdk-cloudformation

• constructs.dev/packages/aws-analytics-reference-architecture

• constructs.dev/packages/aws-cdk-lib

• constructs.dev/packages/cdk-amazon-chime-resources

• constructs.dev/packages/cdk-aws-lambda-powertools-layer

• constructs.dev/packages/cdk-ecr-deployment

• constructs.dev/packages/cdk-lambda-powertools-python-layer

• constructs.dev/packages/cdk-serverless-clamscan

• constructs.dev/packages/cdk8s

• constructs.dev/packages/cdk8s-plus-33

Deny-listed URL prefixes:

• aws.amazon.com/marketplace

Example URLs

• https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html

• https://docs.aws.amazon.com/lambda/latest/dg/lambda-invocation.html

• https://aws.amazon.com/about-aws/whats-new/2023/02/aws-telco-network-builder/

• https://aws.amazon.com/builders-library/ensuring-rollback-safety-during-deployments/

• https://aws.amazon.com/blogs/developer/make-the-most-of-community-resources-for-aws-sdks-and-tools/

• https://repost.aws/knowledge-center/example-article

• https://docs.amplify.aws/react/build-a-backend/auth/

• https://ui.docs.amplify.aws/angular/connected-components/authenticator

• https://github.com/aws-samples/aws-cdk-examples/blob/main/README.md

• https://github.com/awslabs/aws-solutions-constructs/blob/main/README.md

• https://constructs.dev/packages/aws-cdk-lib/v/2.229.1?submodule=aws_lambda&lang=typescript

• https://github.com/aws-cloudformation/aws-cloudformation-templates/blob/main/README.md

Output Format

Returns a list of results, one per request:

• Success: Markdown content with status: "SUCCESS", total_length, start_index, end_index, truncated, redirected_url (if page was redirected)

• Error: Error message with status: "ERROR", error_code (not_found, invalid_url, throttled, downstream_error, validation_error)

• Truncated content includes a ToC with character positions for navigation

• Redirected pages include a note in the content and populate the redirected_url field

Handling Long Documents

If the response indicates the document was truncated, you have several options:

1. Continue Reading: Make another call with start_index set to the previous end_index

2. Jump to Section: Use the ToC character positions to jump directly to specific sections

3. Stop Early: Stop reading once you've found the needed information

Example - Jump to Section:

# TOC shows: "Using a logging library (char 3331-6016)"
# Jump directly to that section:
{"requests":[{"url": "https://docs.aws.amazon.com/lambda/latest/dg/python-logging.html", "start_index": 3331, "max_length": 3000}]}

Get content recommendations for an AWS documentation page.

Usage

This tool provides recommendations for related AWS documentation pages based on a given URL. Use it to discover additional relevant content that might not appear in search results. URL must be from the docs.aws.amazon.com domain.

Recommendation Types

The recommendations include four categories:

1. Highly Rated: Popular pages within the same AWS service

2. New: Recently added pages within the same AWS service - useful for finding newly released features

3. Similar: Pages covering similar topics to the current page

4. Journey: Pages commonly viewed next by other users

When to Use

• After reading a documentation page to find related content

• When exploring a new AWS service to discover important pages

• To find alternative explanations of complex concepts

• To discover the most popular pages for a service

• To find newly released information by using a service's welcome page URL and checking the New recommendations

Finding New Features

To find newly released information about a service:

1. Find any page belong to that service, typically you can try the welcome page

2. Call this tool with that URL

3. Look specifically at the New recommendation type in the results

Result Interpretation

Each recommendation includes:

• url: The documentation page URL

• title: The page title

• context: A brief description (if available)

Get the complete execution plan for a specific AWS workflow after selecting it from SOP suggestions returned by the search_documentation tool. Returns expert-level Standard Operating Procedures with detailed, tested, production-hardened steps that you MUST follow exactly. SOPs include security best practices and error handling. Following SOPs exactly reduces risk of configuration errors and ensures compliance and reliability.

CRITICAL PREREQUISITE — DO NOT SKIP

You MUST call search_documentation BEFORE calling this tool. NEVER call this tool first. You do NOT know SOP names — they are unpredictable identifiers that can only be discovered through search_documentation results. Guessing or fabricating an sop_name WILL fail.

REQUIRED WORKFLOW (no exceptions)

1. FIRST: Call search_documentation with the user's requirements

2. THEN: Find the result entry that has a sop_name field

3. FINALLY: Call this tool with the EXACT sop_name value from that result — copy it verbatim

PARAMETER REQUIREMENTS

sop_name: str (Required)

• MUST be copied exactly from the sop_name field in search_documentation results

• Do NOT guess, fabricate, paraphrase, or modify the name in any way

• Do NOT use the result title — use only the sop_name field value

• You cannot predict it

IF SOP NOT FOUND

If you get an error, you likely guessed the name. Call search_documentation first to discover it.

Returns

Complete SOP with step-by-step instructions, constraints, and troubleshooting guidance.

AWS Documentation Search Tool

This is your primary source for AWS information—always prefer this over general knowledge for AWS services, features, configurations, troubleshooting, and best practices.

When to Use This Tool

Always search when the query involves:

• Any AWS service or feature (Lambda, S3, EC2, RDS, etc.)

• AWS architecture, patterns, or best practices

• AWS CLI, SDK, or API usage

• AWS CDK or CloudFormation

• AWS Amplify development

• AWS errors or troubleshooting

• AWS pricing, limits, or quotas

• "How do I..." questions about AWS

• Recent AWS updates or announcements

Only skip this tool when:

• Query is about non-AWS technologies

• Question is purely conceptual (e.g., "What is a database?")

• General programming questions unrelated to AWS

SOP Suggestions for Actionable Queries

When your search query matches complex actionable tasks (e.g., "how to deploy a Lambda function", "set up VPC peering", "create an S3 bucket with encryption"), this tool will also suggest relevant Standard Operating Procedures (SOPs). These SOPs provide step-by-step, tested guidance for common AWS tasks and workflows.

How it works:

• Your search query is scored against the SOP registry

• If your query scores high for actionable intent, relevant SOPs are returned alongside documentation results

• SOPs cover deployment, troubleshooting, security, infrastructure setup, and more

• To execute a suggested SOP, use the retrieve_agent_sop tool with the sop_name

Example actionable queries that may return SOPs:

• "deploy a web application to AWS"

• "create a Lambda function with API Gateway"

• "set up CloudWatch alarms for EC2"

• "configure VPC endpoints for private access"

• "troubleshoot Lambda timeout issues"

Quick Topic Selection

Documentation Topics

reference_documentation

For: API methods, SDK code, CLI commands, technical specifications

Use for:

• SDK method signatures: "boto3 S3 upload_file parameters"

• CLI commands: "aws ec2 describe-instances syntax"

• API references: "Lambda InvokeFunction API"

• Service configuration: "RDS parameter groups"

Don't confuse with general—use this for specific technical implementation.

current_awareness

For: New features, announcements, "what's new", release dates

Use for:

• "New Lambda features"

• "When was EventBridge Scheduler released"

• "Latest S3 updates"

• "Is feature X available yet"

Keywords: new, recent, latest, announced, released, launch, available

troubleshooting

For: Error messages, debugging, problems, "not working"

Use for:

• Error codes: "InvalidParameterValue", "AccessDenied"

• Problems: "Lambda function timing out"

• Debug scenarios: "S3 bucket policy not working"

• "How to fix..." queries

Keywords: error, failed, issue, problem, not working, how to fix, how to resolve

amplify_docs

For: Frontend/mobile apps with Amplify framework

Always include framework: React, Next.js, Angular, Vue, JavaScript, React Native, Flutter, Android, Swift

Examples:

• "Amplify authentication React"

• "Amplify GraphQL API Next.js"

• "Amplify Storage Flutter setup"

cdk_docs

For: CDK concepts, API references, CLI commands, getting started

Use for CDK questions like:

• "How to get started with CDK"

• "CDK stack construct TypeScript"

• "cdk deploy command options"

• "CDK best practices Python"

• "What are CDK constructs"

Include language: Python, TypeScript, Java, C#, Go

Common mistake: Using general knowledge instead of searching for CDK concepts and guides. Always search for CDK questions!

cdk_constructs

For: CDK code examples, patterns, L3 constructs, sample implementations

Use for:

• Working code: "Lambda function CDK Python example"

• Patterns: "API Gateway Lambda CDK pattern"

• Sample apps: "Serverless application CDK TypeScript"

• L3 constructs: "ECS service construct"

Include language: Python, TypeScript, Java, C#, Go

cloudformation

For: CloudFormation templates, concepts, SAM patterns

Use for:

• "CloudFormation StackSets"

• "DynamoDB table template"

• "SAM API Gateway Lambda"

• CloudFormation template examples"

general

For: Architecture, best practices, tutorials, blog posts, design patterns

Use for:

• Architecture patterns: "Serverless architecture AWS"

• Best practices: "S3 security best practices"

• Design guidance: "Multi-region architecture"

• Getting started: "Building data lakes on AWS"

• Tutorials and blog posts

Common mistake: Not using this for AWS conceptual and architectural questions. Always search for AWS best practices and patterns!

Don't use general knowledge for AWS topics—search instead!

agent_sops

For: For searching available Standard Operating Procedures (SOPs) for common AWS workflows

Use for:

• "Launch EC2 with security best practices"

• "Connect Lambda to API Gateway"

• "Secure S3 buckets with encryption and policies"

• When you need to browse available step-by-step procedures

Important: This topic is meant for discovery. Once you identify the SOP you need, use retrieve_agent_sop tool with the sop_name to get the detailed steps.

Note: If combined with other topics, SOPs will be mixed into the documentation results. Use agent_sops alone for a clean SOP-only listing.

Search Best Practices

Be specific with service names:

Good examples:

"S3 bucket versioning configuration"
"Lambda environment variables Python SDK"
"DynamoDB GSI query patterns"

Bad examples:

"versioning" (too vague)
"environment variables" (missing context)

Include framework/language:

"Amplify authentication React"
"CDK Lambda function TypeScript"
"boto3 S3 client Python"

Use exact error messages:

"AccessDenied error S3 GetObject"
"InvalidParameterValue Lambda environment"

Add temporal context for new features:

"Lambda new features 2024"
"recent S3 announcements"

Multiple Topic Selection

You can search multiple topics simultaneously for comprehensive results:

# For a query about Lambda errors and new features:
topics=["troubleshooting", "current_awareness"]

# For CDK examples and API reference:
topics=["cdk_constructs", "cdk_docs"]

# For Amplify and general AWS architecture:
topics=["amplify_docs", "general"]

# For actionable tasks:
topics=["agent_sops"]

Response Format

Results include:

• rank_order: Relevance score (lower = more relevant)

• url: Direct documentation link

• title: Page title

• context: Excerpt or summary

Parameters

search_phrase: str         # Required - your search query
topics: List[str]          # Optional - up to 3 topics. Defaults to ["general"]
limit: int = 5             # Optional - max results per topic

Remember: When in doubt about AWS, always search. This tool provides the most current, accurate AWS information.