# Infra at Scale: Agents, Tools and Infra-as-Code

DevFeed: [Infra at Scale: Agents, Tools and Infra-as-Code](<https://devfeed.tech/articles/infra-at-scale-agents-tools-and-infra-as-code-122088.md>)

Original publisher: [Read original article](<https://benchling.engineering/infra-at-scale-agents-tools-and-infra-as-code-105645ea7b58?source=rss----3d4aa8fb07ea---4>)

Author: Brendan Neutra

Published: 2026-11-06T21:51:13Z

Content type: article

Language: en

Sources: [Benchling](<https://devfeed.tech/sources/benchling.md>)

Topics: [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Travis CI](<https://devfeed.tech/topics/travis-ci.md>), [GitOps](<https://devfeed.tech/topics/gitops.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [github](<https://devfeed.tech/tags/github.md>), [human-review](<https://devfeed.tech/tags/human-review.md>), [iac](<https://devfeed.tech/tags/iac.md>), [infra](<https://devfeed.tech/tags/infra.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [tools](<https://devfeed.tech/tags/tools.md>)

## AI overview

Benchling uses scheduled Cursor Cloud Agents to raise staged Terraform PRs for routine Kubernetes component updates, increasing rollout cadence about fivefold across more than thirty components. Version constants keyed by development, staging, and production compile into per-cluster variables, so each stage's update is a one-line change; PRs advance through stages after testing and bake periods. Per-component configs guide release detection, compatibility research, health checks, and expected Terraform changes. Agents can run plans and test in a development sandbox but need no privileged production access. An authorized engineer reviews PRs, and production runs still require review: a Plan Matcher lets the Reviewer service apply only Terraform changes matching the approved expression; unmatched changes wait for human review. The article's example shows an agent identifying a release-note warning that applied to Benchling's configuration, preserving a controller default and verifying it in development. Staging is intended to limit production risk if an agent misses a breaking change.

## Source excerpt

In a previous post, How We Run Terraform At Scale, we shared how Benchling moved from a painful, laptop-driven, apply-then-merge workflow to an automated infrastructure release system built on Terraform Cloud (TFC). That migration dramatically reduced conflicts and drift, saved an estimated 8,000 developer hours annually, and gave us the foundation to scale from 350 to 625 workspaces managing many thousands of cloud resources across 38 AWS accounts. We also walked through the ecosystem of custom tooling we built around TFC to make it work at our scale: a CLI for bulk review and approval, Slack notifications for pending runs, and automated workspace dependency mapping. Benchling continues to expand both in platform capabilities and geographical reach (close to a thousand Terraform workspaces!). This post will discuss how we leverage AI agents to operate faster and more safely than ever before. We will focus on how we now roll out routine updates to our Kubernetes clusters. What's good for humans is good for agents Before we dive into our AI agent workflows it's important to state what has not changed: Infrastructure as Code (IaC). It turns out the values we embraced to ensure human change management was safe still hold true when AI agents are introduced into the mix: Modular, declarative Terraform: changes at scale are clearly represented in code Changes require authorized human review/approval in a GitHub Pull Request (PR) before merge Terraform Cloud (or any CI/CD) provides a secure environment where approved changes are rolled out automatically Since our customers and their work are our highest priority, it was critical that AI agents be incorporated into this process in the safest manner possible, with a human in the loop. So this is where we landed: AI agents can produce PRs but an authorized engineer must review and approve them. This is a great fit because the majority of effort lies in understanding the required change, making the right code change and testin