Deployment & infraDatabases & storageAI models

AWS

Cloud APIs, CLI, SDKs, IAM, and infrastructure services.

Powerful for agents that can operate within least-privilege IAM and infrastructure-as-code guardrails.

Agent access evidence

CLI

native

AWS CLI supports scriptable access to AWS services.

Evidence

API

native

AWS services expose APIs and SDKs with service-specific references.

Evidence

MCP

strong

AWS provides managed and open-source MCP servers for AWS docs, APIs, infrastructure, databases, observability, and service-specific workflows.

Evidence

Browser

strong

Console is broad and useful but risky for unsupervised agents.

Evidence

Account creation

strong

Self-serve account creation with billing and identity verification.

Evidence

Pricing clarity

strong

Public service pricing calculators and per-service rates; complex at scale.

Evidence

Docs quality

strong

Docs are extensive, service-specific, and versioned.

Evidence

Sandbox

partial

Separate accounts, IAM boundaries, and IaC plans can make agent work safer.

Evidence

Readiness score

Strong

Strong: 77/100. Strongest in machine operability; weakest in production reliability.

Machine operability23.2/25

Agent safety16.2/25

Agent readability17.4/20

Auth and setup12/15

Production reliability8.6/15

Best for

Cloud provisioning, compute, storage, queues, AI services, logs, and enterprise infrastructure.

Pricing

Public service pricing calculators and per-service rates; complex at scale.

Auth

IAM users/roles, STS, SSO, policies, permission boundaries, and access keys.

Account creation

Self-serve account creation with billing and identity verification.

Browser support

Console is broad and useful but risky for unsupervised agents.

CLI

aws

API

https://aws.amazon.com/api

MCP

https://awslabs.github.io/mcp/

Limitations

Key limitations: High blast radius: IAM, billing, data deletion, networking, and production changes require strict review. Model behavior, costs, rate limits, data retention, and safety policies can change by model and account tier; use evals, spend caps, and data controls for sensitive workloads. MCP servers inherit the connected account's scopes and may send prompts or data to third-party services; configure read-only or narrow scopes when available. CLI access is powerful but can run destructive local or production commands; prefer dry runs, preview environments, and non-production credentials.