Retrieve AWS regional availability information for products (service and features), sdk service APIs and CloudFormation resources.

Core Features

• Real-time availability checking across AWS regions

• Support for AWS products, APIs and CloudFormation resources

• Batch query support with filtering options

• Pagination if no filters are passed and all results are to be returned

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

Result Format

Returns a list of dictionaries with:

• Resource identifiers

• Resource status:

  • 'isAvailableIn': Resource is available

  • 'isNotAvailableIn': Resource is not available

  • 'Not Found': Resource name or identifier is not valid

  • and other availability status (e.g. 'isPlannedIn')

Filter Guidelines

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

1. 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']

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

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

• ['AWS::CodeBuild::Project', 'AWS::CloudTrail::Dashboard']

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

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

• ['PrivateLink Support', 'Amazon Aurora'] Note: Without filters, all resources are returned with pagination support via next_token.

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 an AWS documentation page to markdown format.

Usage

This tool retrieves the content of an AWS documentation page and converts it to markdown format. For long documents, you can make multiple calls with different start_index values to retrieve the entire content in chunks.

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

• https://github.com/cdk-patterns

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

• https://constructs.dev/

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

Output Format

The output is formatted as markdown text with:

• Preserved headings and structure

• Code blocks for examples

• Lists and tables converted to markdown format

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 end of the previous response

2. Stop Early: For very long documents (>30,000 characters), if you've already found the specific information needed, you can stop reading

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)

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

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!

Search Best Practices

Be specific with service names:

Good examples:

Bad examples:

Include framework/language:

Use exact error messages:

Add temporal context for new features:

Multiple Topic Selection

You can search multiple topics simultaneously for comprehensive results:

Response Format

Results include:

• rank_order: Relevance score (lower = more relevant)

• url: Direct documentation link

• title: Page title

• context: Excerpt or summary

Parameters

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