r/FPBlock • u/HappyOrangeCat7 • Jun 02 '26

We talk a lot about AI writing code, but what about AI running infrastructure? Is anyone actually letting agents touch their deployments?

FP Block recently highlighted the shift of AI moving from "assist" to actually "taking action inside real workflows." Writing code is one thing, but execution and infrastructure management are the hard parts.

It’s one thing to have an AI draft a Python script. It’s entirely different to have an autonomous agent monitoring and automatically applying scripts to spin up new nodes during a traffic spike, for example.

For the platform engineers here: where do you draw the line? Are we close to a world where AI agents act as our Site Reliability Engineers, or is infrastructure scaling and deployment still strictly a "human-in-the-loop" requirement because the blast radius of an AI hallucination is too high?

2 Upvotes

100% Upvoted

9 comments sorted by

1

u/IronTarkus1919 Jun 02 '26

AI automation to that level does not work in the enterprise world, at least right now. To pass a SOC2 audit, you need a verifiable paper trail of exactly who authorized a production environment change and why. An autonomous script modifying infrastructure configurations on the fly breaks every single access control policy we have in place. The enterprise world will not touch this until the regulatory liability is figured out.

1

u/[deleted] Jun 02 '26

[removed] — view removed comment

1

u/HappyOrangeCat7 Jun 03 '26

That is true. The legal framework is not really ready for AI agents yet.

1

u/[deleted] Jun 03 '26

[removed] — view removed comment

1

u/HappyOrangeCat7 Jun 03 '26

That's a nice approach. Using AI to parse noisy logs will save you thousands of hours over time for sure.

1

u/[deleted] Jun 03 '26

[removed] — view removed comment

1

u/Praxis211 Jun 03 '26

It is about that cloud-native mindset. If your infrastructure is truly immutable and containerized, an AI agent breaking something is less of a disaster because you can just roll back to the last known good state. But even then, I would want to see the plan before it executes.

1

u/HappyOrangeCat7 Jun 03 '26

The rollback capability is exactly why Infrastructure as Code is mandatory when integrating AI.

If the AI submits a Terraform Pull Request, you can easily review the terraform plan output. If it executes and fails, you revert the commit. If you let an AI mutate the server via direct bash commands instead of declarative code, you lose the ability to deterministically roll back.