re:Invent and the year of the boring cloud announcement
Silicon, agents, and a keynote that mostly described things that already existed. That's a healthy sign.
AWS re:Invent is underway and the announcement pace is, as always, absurd. Most of it will not matter to you. Here is the part that will.
silicon#
Amazon continues pushing Trainium and Inferentia as the alternative to buying Nvidia. The pitch is price-performance for customers who can tolerate a different software stack.
The honest state of it: the hardware is competitive on paper, the software ecosystem is meaningfully behind CUDA, and the gap is closing slowly. If your workload runs through PyTorch with standard operations, the port is manageable. If you have custom kernels, it is a project.
The strategic point is the same for every hyperscaler: reducing dependency on a single supplier with enormous pricing power. Whether the customer benefit materializes depends entirely on whether the savings get passed through.
the agent announcements#
Every cloud vendor is now shipping agent infrastructure: runtimes, memory services, gateways for tool access, identity for agents, observability for agent traces.
This category is real. Running agents in production has genuine infrastructure requirements that are different from running services:
- Long-lived sessions with state that outlives a request.
- Non-deterministic execution paths that make traditional tracing awkward.
- Cost per invocation that varies by orders of magnitude.
- Identity and permission scoping for a thing acting on a user's behalf.
- Human approval gates in the middle of automated flows.
Those are real problems and the tooling is early everywhere. Evaluate on whether it solves a problem you actually have, not on whether the demo was good.
the pattern I would push back on#
Every vendor's agent framework wants to be the place your orchestration lives. That is a lock-in position, and orchestration is the layer most likely to be absorbed by the models themselves — it has been happening steadily for two years.
Keep your orchestration portable. Use the managed pieces for the genuinely hard infrastructure — identity, secure tool access, session storage — and keep the logic in your own code.
the underrated announcements#
The ones nobody writes about and everybody uses:
- Incremental improvements to S3 consistency and performance.
- Networking latency reductions.
- Cost management tooling that is slightly less bad.
- Database engine version updates.
These are worth more to most organizations than any AI announcement, and they get four slides between two hours of agent demos.
the meta-observation#
Cloud conferences have gotten less interesting, and that is good. It means the platform is mature. The exciting years of a platform are the years when fundamental things are missing.
The interesting question for AWS is not what they announced. It is whether the operational excellence that justified the premium is still there after a year that included a major regional outage. That is an execution question and it does not get answered at a conference.
what to actually do with this#
Skip the keynote. Read the "what's new" feed filtered to the services you actually use. Look for the deprecations, which are the announcements that will cost you time and which are never on stage.
And check your bill. The single highest-value hour available to most engineering organizations is someone competent looking at the AWS bill line by line, and almost nobody does it.
— Dom, December 2, 2025