Can AI agents automate Amazon Web Services?

Amazon Web Services is automatable today through its public service APIs and the AWS CLI. This record is the AWS cloud platform — compute, storage, networking, IAM, and the other billed AWS services — not Microsoft Azure, not one MCP server per AWS product, and not Amazon retail. AWS states that all IaaS administration, management, and access functions in the AWS Management Console are available in the AWS API and AWS CLI, and that new IaaS features appear there at launch or within 180 days. Callers send HTTPS API requests signed with AWS Signature Version 4. Documented programmatic credentials are IAM user access keys, IAM roles that issue temporary credentials, and IAM Identity Center (SSO) sessions configured with the AWS CLI. Official SDKs cover C++, Go, Java, JavaScript, Kotlin, .NET, PHP, Python, Ruby, Rust, and Swift. The AWS CLI v2 is the official cross-platform tool, with json, yaml, text, and table output for scripts. CloudFormation templates and the AWS CDK, which synthesizes CloudFormation, are the first-party infrastructure-as-code path. EventBridge API destinations can invoke HTTPS endpoints with PUT or POST. AWS Labs publishes a suite of specialized open-source MCP servers at github.com/awslabs/mcp (stdio, Apache-2.0). That README states that the Agent Toolkit for AWS is now live as the successor to the MCP servers, plugins, and skills available on AWS Labs; if you are building production software using coding agents or building agents for your own customers, AWS recommends Agent Toolkit for AWS; the awslabs/mcp repository continues to work and accept contributions. Official Agent Toolkit docs describe a managed AWS MCP Server at https://aws-mcp.us-east-1.api.aws/mcp and https://aws-mcp.eu-central-1.api.aws/mcp that can search documentation without authentication and run API calls, sandboxed Python, and curated skills with IAM, using OAuth 2.1 via AWS Sign-in or SigV4 through a local proxy. Connector catalogs were not opened. Computer-use viability is unassessed. API scores 8 and is the best path because it is the durable signed service-API contract. CLI also scores 8 as a maintained wrapper over that contract. MCP scores 7: official and useful, with production guidance pointing at Agent Toolkit rather than the local Labs suite, and with managed-server Regions limited to us-east-1 and eu-central-1.

Best path today: api · Overall automatability: 8/10