Decisions teams on AWS should make before 2027, each with a deadline attached: model lifecycle and evaluation, agent identity, coding agents, container platforms, the EU's 2027 regulations, and the upgrades that get expensive if left until the summer.
Every year-ahead article guesses at trends. This one sticks to decisions that have dates or costs attached in 2027, and gives our recommendation for each. Where we are offering an opinion rather than a fact, we say so.
Bedrock now publishes an "end of life no sooner than" date for every new model, and the models most teams use today reach that date in the second half of 2027 or soon after. The decision: build an evaluation set from your own traffic for every LLM feature, keep model IDs in configuration, and route through one client or gateway. Teams that do this switch models in an afternoon; teams that do not get a forced migration under deadline.
Your customers' agents will call your product, and your own agents will call other services. The MCP authorization specification settled the inbound pattern in 2026 — OAuth resource servers, Protected Resource Metadata, Client ID Metadata Documents — and enterprise identity providers are rolling out Cross App Access for governance. The decision: treat agent access as an API product with OAuth, scopes and audit logs, rather than tolerating scraping and shared keys.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Most engineering teams now use coding agents; few have decided how. The decision: pick one or two, run them through your own AWS account where possible (Claude Code and Codex both run on Bedrock), set the permissions policy and the review rule, and measure. Our opinion: per-token billing through Bedrock suits most teams better than seats until usage is heavy and steady.
ECS gained managed EC2, one-call deployments and native canary releases; EKS gained Auto Mode and managed Argo CD — and kept charging six times as much for clusters that fall behind. The decision: if nobody wants to own Kubernetes upgrades every four months in 2027, move ordinary services to ECS now; if you stay on EKS, move to Auto Mode and put every cluster's support dates on a calendar.
The EU Cyber Resilience Act's main obligations apply from December 11, 2027 to products with digital elements placed on the EU market — software and connected devices — and its vulnerability reporting duties already applied from September 11, 2026. The AI Act's obligations for Annex III high-risk systems apply from December 2, 2027 after the 2026 Digital Omnibus moved them. The decision: if you sell into the EU, find out this quarter which of your products are in scope; a year is not long for secure-development evidence, update processes and documentation.
Lambda functions on deprecated runtimes — before the July 29 and August 31 blocks.
RDS for PostgreSQL 14 — before Extended Support charges start on March 1.
Anything on Amazon Linux 2, which stopped receiving security updates in June 2026.
PHP 8.2 by the end of 2026 and Node.js 22 by April 2027.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Platform Engineering in 2027: The AWS Stack We Would Choose Today, and Why
If we were starting a product on AWS today and wanted it to still be sensible in 2027, these are the choices we'd make (compute, data, identity, AI, delivery and observability) with the reason for each and the condition that would change our mind.
Read
AWS in 2027: Every Deadline Already on the Calendar
Lambda's update block, EKS versions, RDS Extended Support price steps, Bedrock model retirements, the end of Python 3.11, Node.js 22 and PHP 8.3, and the EU's Cyber Resilience Act and AI Act dates: every 2027 deadline we could verify, month by month, with what each costs if missed.
Read
As of October 26, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.