Cloud Infrastructure Architect

What it does

Cloud Infrastructure Architect is a Cursor agent playbook named cloud-architect. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The cloud-architect agent provisions resilient cloud infrastructure using Infrastructure as Code (IaC). It creates Terraform modules for VPC networks, serverless fleets, managed databases, S3 object storage, and Cloudflare DNS.

Writes Terraform & IaC scripts for AWS, GCP, Cloudflare, and serverless fleets. Cloud infrastructure architect for Cursor that generates Terraform, AWS CDK, and Cloudflare Workers configs with high availability.

Why it exists

A pile of agent files is not a team. cloud-architect exists so one job, cloud infrastructure architect, has a written brief, required skills, and a stop condition.

It ships in the Engineering Kit. Skills it must read: Terraform Infrastructure as Code (IaC); Multi-Stage Docker & Container Deployments; Observability, Telemetry & SRE Monitoring. Commands that adopt this role: /cloud-infra: Cloud Infrastructure as Code (Terraform / IaC); /dockerize: Docker & Containerization Configurator; /ci-pipeline: GitHub Actions CI/CD Pipeline Generator.

When to use it

• Provisioning production AWS or GCP cloud environments
• Setting up Terraform infrastructure from scratch
• Configuring Cloudflare caching and security firewalls

When not to use it

• Do not ask cloud-architect to do a different role's job. If you need a launch post, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Engineering Kit so .cursor/agents/cloud-architect is on disk.
2. Run /cloud-infra: Cloud Infrastructure as Code (Terraform / IaC), or start a chat and tell Cursor to adopt the cloud-architect role.
3. The agent should read: Terraform Infrastructure as Code (IaC); Multi-Stage Docker & Container Deployments; Observability, Telemetry & SRE Monitoring.
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are cloud-architect. Provisioning production AWS or GCP cloud environments. Read terraform-iac before you edit."

Or let the pipeline invoke it: /cloud-infra: Cloud Infrastructure as Code (Terraform / IaC).

Capabilities you should actually see: Terraform and OpenTofu infrastructure provisioning

Example output

• cloud-architect should leave files or a written verdict, not a vibe check. Terraform and OpenTofu infrastructure provisioning Serverless architecture design (Lambda, Edge Functions, Workers)
• Engineering agents should touch the slice they were given (schema, route, test, or review note) and nothing else.

Best practices

• Terraform and OpenTofu infrastructure provisioning
• Serverless architecture design (Lambda, Edge Functions, Workers)
• Cloudflare CDN, DNS, and DDoS mitigation rules
• Cost optimization and idle resource elimination
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using cloud-architect as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Letting the writer approve its own PR.
• Invoking this agent and three unrelated ones in the same prompt.