AWS Global Search

Problem Context

When evaluating cloud architecture options, engineers often need to confirm which AWS service matches a requirement, what official documentation to read, and which API names or parameters matter. Vague terms like “cloud server,” “object storage,” or “message queue” can easily point to multiple services such as EC2, S3, EBS, or SQS.

How It Works

AWS Global Search turns user input into searchable product signals, including product names, categories, functional requirements, and use cases. It matches those signals against a built-in AWS product catalog that spans common areas such as:

• Compute and serverless: EC2, Lambda, Fargate, Batch
• Storage and databases: S3, EBS, RDS, Aurora, DynamoDB
• Containers and networking: EKS, ECS, CloudFront, VPC
• Security, analytics, and integration: IAM, WAF, Kinesis, SQS, Step Functions

The workflow first normalizes aliases, for example mapping “cloud server” to EC2 and “object storage” to S3. It then records the English product name, category, and service code before using official AWS documentation and product pages to locate parameters, API references, or feature details.

Scope and Caveats

This skill is best suited for knowledge questions such as “Which AWS product is this?”, “Where is the documentation?”, or “Which service provides this capability?”. It relies on public AWS pages, so it should not be treated as a source for real-time billing, account-specific resource state, or unverified compliance conclusions.