I recently wound up in conversation with someone working at Amazon. Inevitably, the convo steered into AI/LLM's at some point.

Here is what I learned:

- AWS had an in-house LLM tool that was terrible they tried to use for a while

- A lot of them still use Kiro

- Claude Code is currently the de-facto standard

- They're in the process of getting some custom Codex variant that doesn't phone-home and is audited approved

- There's no mandated organizational standard for what exact tools to some, various teams have different levels of adoption and stacks

- No org-wide/team-wide conventions for Claude Code

- They do have token budgets

- There's an intenral push for something called "Agent Spaces" which was described to me as a sort of Lovable/Bolt-type thing if I understood it right

I can't validate all of this and I might have misremembered, but just in case anyone else finds it interesting.

> There's no mandated organizational standard for what exact tools to some, various teams have different levels of adoption and stacks

> No org-wide/team-wide conventions for Claude Code

Just for context, this pattern (different teams using different tools in different ways) is extremely normal within Amazon, and is intentional. These shouldn't necessarily be seen as a failure. Amazon likes to have multiple competing options they use for everything, and they constantly evaluate which option is best performing, like an A/B test. After a couple years they will pare away whatever performs worst, replacing it with a new option. This strategy definitely has it's disadvantages, but it is an intentional chosen pattern throughout the company.

Source: I worked there for 5 years, and painfully/tearfully remember the transitions chime -> slack -> teams and workdocs -> quip -> confluence :')

I am more curious about how much token budget they have. Here I have to beg my boss for more as if he is paying from his pocket or I am using it for my hobby projects (I am not). I guess time to go back to copy/pasting to chat and doing things by hand like a caveman.

I work at AWS, we got access to Claude Code very recently, most people are using Kiro and that seems to be the defacto standard.

I have not heard of any nor run into any token budgets.

There is generally a lot of team-wide usage of CLAUDE.md/AGENTS.md, team-specific skills, oncall skills, etc.

Not as much org-wide, although my org has an MCP server built for helping with oncall.

> There's an intenral push for something called "Agent Spaces" which was described to me as a sort of Lovable/Bolt-type thing if I understood it right

Everyone and their mother making vibe-app platforms for their company API's now

Would be really curious what the internal market share for Kiro is. Not a really good look for it if it's just smattering use here and there.

assuming it hasnt changed, agent spaces is just a developer desktop running on actual aws rather than on internal hosts, and they figured out how to put vscode on it in a security approved way, including your employee credentials.

one of the things that allows is for adding mcps, skills, and various harnesses that are preconfigured to work out of the box.

i doubt its gotten out of the employee needing to sign in every couple hours

From the outside it always seems laughably circuitious compared to just learning skills ourselves.

Even if it did let me fill out TPS reports 20% faster, who even cares compared to all of this chaos?