Staying Current: AWS What's New & SDK Release Notes

AWS ships announcements constantly - new services, new API operations, new SDK releases. No single person reads all of it. The realistic goal is a lightweight, repeatable habit that catches what's relevant to your stack, using AWS's own real sources rather than an invented tool or newsletter.

Recipe

Quick-reference recipe card - copy-paste ready.

# --- Python (boto3) ---
# Monthly habit (5-10 minutes):
# 1. Skim AWS What's New (aws.amazon.com/new), filtered to services you use.
# 2. Skim botocore's CHANGELOG.rst on GitHub for the current release line.
# 3. Note anything relevant to a tracked deprecation/dependency review.

// --- TypeScript (AWS SDK v3) ---
// Monthly habit (5-10 minutes):
// 1. Skim AWS What's New (aws.amazon.com/new), filtered to services you use.
// 2. Skim the relevant @aws-sdk/client-* package's GitHub releases.
// 3. Note anything relevant to a tracked deprecation/dependency review.

When to reach for this:

• On a recurring monthly cadence, independent of whether anything feels urgent.
• Before starting work on a service you haven't touched recently, to check for new capabilities.
• Alongside the quarterly deprecation review, as the lighter-weight habit that feeds it.

Working Example

A short, repeatable routine that turns "staying current" into five minutes a month rather than an open-ended research task.

# --- Python (boto3) ---
# staying-current.md (Python services)
#
# Sources checked monthly:
# - https://aws.amazon.com/new/ (filter: S3, DynamoDB, Lambda)
# - https://github.com/boto/botocore/blob/develop/CHANGELOG.rst
#
# Last checked: 2026-07-01
# Findings this month: no changes affecting current integrations

// --- TypeScript (AWS SDK v3) ---
// staying-current.md (Node/TypeScript services)
//
// Sources checked monthly:
// - https://aws.amazon.com/new/ (filter: S3, DynamoDB, Lambda)
// - https://github.com/aws/aws-sdk-js-v3/releases
//
// Last checked: 2026-07-01
// Findings this month: no changes affecting current integrations

What this demonstrates:

• The sources are named explicitly and are real: AWS's own What's New feed and the SDK's own GitHub changelog/releases, not a generic "check for updates" instruction.
• The habit is dated, so it's clear whether it's actually being kept up, the same pattern used in the deprecation-tracking note elsewhere in this section.
• Filtering AWS What's New to the services actually in use keeps a monthly skim to a few minutes instead of an unfiltered firehose.

Deep Dive

AWS What's New

AWS What's New, at aws.amazon.com/new, is AWS's own running feed of service-level announcements - new services, new regions, new API operations, pricing changes, and feature launches. It can be filtered by category and searched by service name, which makes a monthly skim of only the services your codebase actually uses a fast habit rather than an open-ended research project.

This is the right first stop for "did anything change about a service I use" - it is official, current, and does not require a third-party aggregator.

SDK-Specific Release Notes

For the SDK layer itself, each language has its own authoritative source. Python's boto3 and botocore publish a CHANGELOG.rst in their GitHub repositories, updated on nearly every release, listing new operations, bug fixes, and any breaking changes. The AWS SDK for JavaScript v3 publishes releases per package on GitHub (aws/aws-sdk-js-v3), with release notes describing what changed in each @aws-sdk/client-* version.

These are worth checking separately from AWS What's New, because a new SDK feature or bug fix can land without any corresponding "new service" announcement - it's purely a client-library change.

AWS re:Post

AWS re:Post is AWS's community Q&A platform. It is not an official announcement channel, but it is a genuinely useful secondary source for migration gotchas, workarounds, and discussion around a recent deprecation or SDK change that the official notes describe tersely. Treat it as a place to search when something from What's New or a changelog needs more context, not as a primary source to monitor on its own.

Making It a Habit, Not a Project

The realistic goal is a short, repeatable routine - a five-to-ten-minute monthly skim of AWS What's New filtered to your services, plus a glance at the relevant SDK's changelog or releases - not an attempt to read everything AWS publishes. This is deliberately lightweight because a habit that takes too long tends to get skipped.

This monthly habit is the input to the more formal quarterly deprecation review covered elsewhere in this section: most of what turns into a tracked deprecation or major-version item is first noticed here, in the lighter-weight monthly pass.

Gotchas

• Trying to read every AWS announcement, not just relevant ones. AWS What's New covers hundreds of services; unfiltered reading burns time on things you don't use. Fix: filter by the services actually in your stack.
• Checking only AWS What's New and skipping the SDK's own changelog. SDK-level bug fixes and behavior changes don't always get a corresponding service announcement. Fix: check both sources, not just one.
• Treating AWS re:Post as an official source. It's community content, useful for context but not authoritative on its own. Fix: use it to supplement, not replace, AWS's own notices and the SDK's own release notes.
• Making the habit too infrequent to matter. Checking once a year means months of relevant changes pile up unnoticed. Fix: monthly is a reasonable default; pick a cadence and actually keep it.
• Not writing down what was checked and when. Without a record, it's easy to lose track of whether the habit is actually happening. Fix: keep the same simple dated note used for deprecation tracking.

Alternatives

FAQs

Related

• Tracking AWS Deprecations & SDK Major Versions - the formal quarterly review this monthly habit feeds.
• Why AWS SDK Code Needs Governance - why staying current is one of the four practices this section covers.
• Standards & Governance Basics - where this habit appears as a starter checklist item.

Stack versions: This page was written for boto3 1.43.x (Python 3.10+) and the AWS SDK for JavaScript v3 (Node.js 18+).