I asked an AI agent to put a real domain in front of a live app — without touching it.
Rethink DevOps
0:00 / 0:00
I asked an AI agent to put a real domain in front of a live app — without touching it.
8 просмотров · 10 дней назад
Rethink DevOps
7 подписчиков
8 просмотров · 10 дней назад
In episode one, an AI agent got Marketing's app running in my cloud. The link worked. Nobody wanted to share it: a default Lambda URL looks like a phishing link.
So Marketing came back with a second Jira ticket. A proper address on our own domain, the padlock in the browser, and a front door we can change later without changing the link. And no downtime, because the app is already live.
Easy on paper. The catch is that the app runs in one AWS account and our DNS zone lives in another one entirely, a shared-services account marked as production. I gave the ticket to a fresh agent with no context and no AWS keys, and watched what it did with that.
This was recorded live
One session, nothing scripted for the agent. That means real waiting while AWS builds a CloudFront distribution, so I walk through the platform while it runs.
The platform holds the agent twice:
once for third-party code
and once for touching the production DNS account.
At the end the agent saves the whole thing as a draft golden path and starts its smoke test, so once it's published, the next team won't need a ticket at all.
⏱ CHAPTERS
0:00 Where episode one left off
1:45 The ticket — a link people will actually trust
2:35 How I'd architect it — and the account the DNS lives in
4:15 Where we start: a live Lambda, encrypted by default
5:32 Giving a fresh agent the ticket
7:09 Three questions — hostname, SSL, sandbox
8:20 A change to the live app, not a new project
8:42 Held for a person — third-party code
10:50 A tour of the platform while it builds
18:24 Held again — the production DNS account
21:09 Why an agent needs a control plane
24:24 CloudFront is up
27:07 The agent has no cloud credentials
28:19 The DNS record goes in
29:20 Live on our domain — and my DNS cache
31:15 Saving it as a golden path
33:22 Next: Kubernetes, behind the same address
35:09 Why I'm building this
🔗 THE PLATFORM
Archie — the governed layer between the agent and the cloud: https://askarchie.io
I'm looking for a few teams to try it with: read-only first, in your own sandbox, with real tickets instead of my made-up ones.
📺 NEXT EPISODE
Part 2 — Who composes the golden path? The app becomes a container, the agent builds a Kubernetes path next to the Lambda, and we cut over blue/green behind the same address. [link]
Episode 1: • I gave an AI agent a Jira ticket — and no ...
#PlatformEngineering #DevOps #AIAgents #InternalDeveloperPlatform #InfrastructureAsCode