← All provider guides

AWS API breaking changes (2026): complete tracker and fixes

aws 6 breaking / deprecation entries 2026

AWS ships API and SDK changes continuously. Most are additive — but the ones that are not can silently break integrations that worked yesterday. This page is the complete, continuously regenerated record of every AWS breaking change and deprecation in the mendapi change database: 6 entries (4 breaking, 2 deprecation), each linked to its upstream source and, where possible, to a concrete fix.

How to read this page

Every entry carries a fixability verdict from the mendapi adjudication pipeline: code-fixable means a mechanical code change repairs the break (1 entries); not code-fixable means the change requires a business decision, credential provisioning, or upstream action that no codemod can produce (5 entries). Entries marked auto-fix pack have a deterministic, gold-tested migration pack that mendapi fix can apply locally.

Am I affected?

Reading a changelog tells you what changed — not whether your code uses the affected surface. The mendapi scanner answers that locally, in about 30 seconds, without any code leaving your machine:

npx mendapi sync
# -> one network call: pulls the change feed into a local database
npx mendapi scan
# -> N findings: file, line, provider, confidence
mendapi deps --match
# -> which of the changes below actually hit your endpoints

See Getting Started for the full workflow and the security model for why zero code upload is the default and only mode.

Complete AWS breaking change timeline

DateChangeRef
2026-08-06 v3.1105.0
breaking not code-fixable
aws-sdk-js-v3 v3.1105.0: codegen chores, endpoint refresh, and additive client features (CloudWatch Logs index		 source
2026-08-04 v3.1103.0
breaking not code-fixable
Chores (undici bump), documentation-only client updates, and additive features (iam endpoint generation		 source
2026-07-24 v3.1095.0
breaking not code-fixable
Codegen sync chores and documentation-only client updates		 source
2026-07-21 v3.1092.0
breaking not code-fixable
Documentation updates plus additive Redshift features		 source
2026-07-16 v3.1089.0
deprecation not code-fixable
Docs-only S3 lifecycle clarification and additive features		 source
2026-07-13 v3.1086.0
deprecation code-fixable
GuardDuty findings deprecate GuardrailArn/GuardrailVersion in favor of guardrail detail fields — a response-field		 source

Automated migration packs for AWS

mendapi ships 1 deterministic migration pack for AWS — verified, idempotent codemods you can apply locally with mendapi fix. Full details in the pack catalog.

  • aws-sdk-v2-to-v3-s3 — AWS SDK for JavaScript v2 -> v3 migration (S3) (upstream reference)

Recent AWS releases adjudicated non-breaking

Not paging you is the other half of the job. The same pipeline that produced the timeline above also cleared 16 AWS changes as additive or fix-only — releases an integrator can upgrade through without a migration. The most recent:

DateReleaseRef
2026-08-10 v3.1107.0
additive
client-connect: Added Malay language option to use AI to automatically fill evaluation forms in		 source
2026-08-07 v3.1106.0
additive
clients: update client endpoints as of 2026-08-07		 source
2026-08-05 v3.1104.0
additive
client-deadline: AWS Deadline Cloud now reports persistent volume costs alongside compute and		 source
2026-08-03 v3.1102.0
additive
client-direct-connect: Added route visibility support for AWS Direct Connect, allowing customers to		 source
2026-07-31 v3.1100.0
additive
clients: update client endpoints as of 2026-07-31		 source
2026-07-31 v3.1101.0
additive
client-resiliencehubv2: Adding support for new testing capability in AWS Resilience Hub		 source
2026-07-30 v3.1099.0
additive
clients: update client endpoints as of 2026-07-30		 source
2026-07-29 v3.1098.0
additive
clients: update client endpoints as of 2026-07-29		 source

Measured: what adjudication filters out of a release feed

The AWS entries above are fed by the aws-sdk-js-v3 release feed, not a spec-diff corridor — AWS publishes service models per SDK release rather than one public OpenAPI repository, so unlike the Stripe or Twilio trackers this page makes no corridor claim. What every entry does carry is an adjudicated fixability verdict with a machine-readable reason, and for AWS the split is the story: of the 6 breaking and deprecation entries above, 1 is code-fixable and 5 are not — and most of the “not” verdicts exist because the release notes cried wolf.

A verdict that says nothing broke. “v3.1095.0” was flagged by the keyword pass, but the adjudicated reason reads: Codegen sync chores and documentation-only client updates; no consumer-facing API change to mend. A weekly SDK train that ships codegen chores under alarming headings is exactly the noise an unadjudicated feed would page you for.

A verdict that says here is the fix. “v3.1086.0” is the one real consumer-facing change in the set: GuardDuty findings deprecate GuardrailArn/GuardrailVersion in favor of guardrail detail fields — a response-field rename mappable at read sites. That is the class of change a codemod can carry — the same class the aws-sdk v2 to v3 migration pack handles at scale.

Monitoring AWS going forward

This page is regenerated from the change database, which is fed by release feeds, changelog capture and OpenAPI spec diffing — so it does not depend on AWS writing a perfect changelog. mendapi monitors 84125 change records across 20 providers; hosted plans watch your repos continuously and open fix PRs when a change lands. See pricing.

Frequently asked questions

How do I check if my codebase is affected by AWS breaking changes?

Run npx mendapi scan in your repo. It statically matches your files against the 6 AWS breaking changes and deprecations in this tracker and reports file, line and confidence for every hit — locally, in about 30 seconds, with zero network calls.

How many AWS API breaking changes are on record?

This tracker records 6 entries for AWS (4 breaking changes and 2 deprecations, 2026). Each entry is adjudicated: 1 is code-fixable, 5 require a decision no codemod can make.

Are there automated fixes for AWS breaking changes?

Yes — mendapi ships 1 deterministic migration pack for AWS. mendapi fix applies them locally as reviewable diffs; every pack is gold-tested and idempotent.

Does my code get uploaded when scanning for AWS changes?

No. mendapi scan, deps and fix run with zero network code, mechanically enforced by the test suite. Optional hosted reporting is metadata-only, secrets-redacted, and requires an explicit flag.

Related

Every entry on this page is generated from the mendapi change database at build time and links its upstream source.