Processes/product — standing up the product stackproduct
Set up cloud infrastructure — product processSet up cloud infrastructure
Configure cloud infrastructure with networking, a managed database, container hosting, and basic security. AWS (VPC, RDS, ECS) is the canonical route.
AWS has comprehensive APIs. System can provision via CloudFormation/API, but architecture decisions need human input.
Current agent ceiling
An agent can run 6 of 8 steps — 5 of them behind a human approval gate ⏸
⚡ Closable with today’s market (1 — via Browser Automation for Agents): Create AWS account + billing (computer-use candidate — a browser agent can drive this deterministic web flow)
No workaround yet (1): Design infrastructure (needs a human)
How it runs
Route-coded block flow: emerald = agent, amber = manual form/portal, red = needs a human. ⏸ approval gate · ⏳ async wait.
01Design infrastructure
human02Create AWS account + billing
manual form⚡ agentic workaround: computer-use candidate — a browser agent can drive this deterministic web flow — Steel, top of Browser Automation for Agents → · assisted, not autonomous — a human supervises; verify the portal’s terms allow automation
03Configure VPC and networking
agent3 API calls
- ec2.createVpc
- ec2.createSubnet
- ec2.createSecurityGroup
runs in parallel · 3
04Set up RDS database
agent1 API call
- rds.createDBInstance
05Configure ECS cluster
agent2 API calls
- ecs.createCluster
- ecs.registerTaskDefinition
06Set up IAM roles
agent1 API call
- iam.createRole
07Configure monitoring
agent1 API call
- cloudwatch.putMetricAlarm
08Test deployment
agentContext the agent needs first: infra expected traffic (from the founder) · infra database type (from the founder) · infra region (from the founder)