AWS Amplify is a declarative JavaScript library for frontend and mobile developers building cloud-enabled applications. It provides an easy-to-use interface for common cloud operations such as authentication, analytics, REST and GraphQL APIs, data synchronization, and storage, with optional support for additional services like push notifications, location, and pub/sub.
Project status
- Actively maintained: The repo has an upstream push as recently as 2026-08-07, and multiple package-level updates occurred in late July 2026, indicating ongoing development rather than dormancy.
- Apparent update cadence: Updates cluster around 2026-07-21 and 2026-07-30, suggesting a roughly weekly to 1.5 week rhythm for minor and patch updates (at least across the packages reflected here).
AI summary generated
Recent updates
@aws-amplify/storage@6.17.0
This release adds explicit AmplifyContext support across Amplify category APIs, including context-first overloads and a new createAmplifyContext factory for isolated per-request or per-tenant usage. It also tightens configuration handling by deep-freezing resources config after Amplify.configure and createAmplifyContext, and raises peer dependency minimums to prevent unsupported version skew.
BreakingFeatures@aws-amplify/pubsub@6.2.1
This patch release updates the dependency set for @aws-amplify/pubsub. The only noted change is a bump of the connected @aws-amplify/auth dependency to version 6.21.1.
@aws-amplify/predictions@6.2.0
This release introduces first-class, explicit AmplifyContext support across category APIs in addition to existing singleton-based calls. It also tightens configuration handling by deep-freezing the resources config after Amplify.configure() and createAmplifyContext(), and updates peer dependency minimums to reduce version-skew issues.
BreakingFeatures@aws-amplify/notifications@2.2.0
This release adds explicit AmplifyContext support across category APIs, including context-first overloads and a new createAmplifyContext factory for isolated per-request or per-tenant contexts. It also tightens configuration handling by deep-freezing resources config after Amplify.configure and createAmplifyContext, and includes fixes to SSR GraphQL client option honoring and clearer event error messages.
BreakingFeatures@aws-amplify/interactions@6.2.0
This release adds explicit AmplifyContext support across interactions category APIs, including context-first overloads, a factory for isolated per-request contexts, and typed context misuse errors. It also updates SSR behavior and API-GraphQL handling (request options and error messages), and raises peer dependency minimums to reduce version-skew issues. Finally, it bumps fflate to mitigate a potential DoS vulnerability in unzipSync.
BreakingSecurityFeatures@aws-amplify/geo@3.1.0
This release adds explicit AmplifyContext support across category APIs, including new context-first overloads and a factory for creating isolated contexts per request or tenant. It also tightens configuration immutability and updates peer dependency minimums, which can affect install compatibility. Additional SSR-related fixes ensure client-level options and error messages behave as expected.
BreakingFeatures@aws-amplify/datastore-storage-adapter@2.2.6
This patch release adds explicit AmplifyContext support across category APIs, including a new per-request context factory and typed misuse errors. It also fixes SSR behavior in `@aws-amplify/adapter-nextjs`, where client-level options were previously dropped, and improves event error messaging accuracy.
BreakingFeatures@aws-amplify/datastore@5.1.12
This is a patch release of @aws-amplify/datastore that primarily updates underlying AWS Amplify dependencies. No direct new datastore functionality or behavior changes are described in the release notes.
@aws-amplify/core@6.19.1
This patch fixes Cognito user-pool authentication when using a locally created AmplifyContext via createAmplifyContext(), without calling Amplify.configure(). It restores the intended getConfig contract (empty config with a warning instead of throwing NoAmplifyContextError) and ensures auth token state is read and written through the correct per-context token orchestrator for non-redirect sign-in flows.
aws-amplify@6.22.0
This release adds an events improvement for subscriptions, including resolving subscription readiness via `channel.subscribe().ready` and adding a subscription id to the `SUBSCRIPTION_ACK` Hub event. It also fixes Cognito user-pool sign-in when using a locally created `AmplifyContext` (via `createAmplifyContext()`) without calling `Amplify.configure()`, restoring the prior `Amplify.getConfig()` behavior and ensuring per-context token persistence for non-redirect flows.
Featuresaws-amplify@6.20.0
This release adds a new push notifications provider that delivers notifications via Amazon Connect Customer Profiles, exposed through the `aws-amplify/push-notifications/customer-profiles` sub-path export. It also updates several Amplify package dependencies and includes runtime guidance warning about the default `aws-amplify/push-notifications` entry point backing Amazon Pinpoint.
Features@aws-amplify/core@6.18.0
This release adds a new push notifications provider that lets applications deliver Push Notifications via Amazon Connect Customer Profiles. It also introduces a new `aws-amplify/push-notifications/customer-profiles` sub-path export and wires support for `amazon_connect` notifications configuration from `amplify_outputs.json.
Features@aws-amplify/datastore@5.1.10
This patch release updates the AWS Amplify DataStore package to include newer versions of its key dependencies. No new functionality or behavioral changes are described in the release notes.
@aws-amplify/notifications@2.1.0
This release adds support for delivering push notifications through Amazon Connect Customer Profiles via a new `aws-amplify/push-notifications/customer-profiles` sub-path export. It also introduces client-side validation and SigV4-signed device registration, and wires in `amazon_connect` push notification configuration from `amplify_outputs.json` through `Amplify.configure`. The default `aws-amplify/push-notifications` entry point now emits a one-time runtime notice because Amazon Pinpoint support is ending on October 30, 2026.
Features@aws-amplify/api-graphql@4.8.10
Release @aws-amplify/api-graphql@4.8.10 is a patch release that, per the notes, only updates a dependency on @aws-amplify/core@6.18.0. The provided code diff largely shows changes to generated API documentation assets (HTML/JS/CSS) rather than runtime source code.
@aws-amplify/api@6.3.29
This patch release updates the underlying @aws-amplify/api-graphql dependency. No other user-facing changes, API updates, or fixes are described in the release notes.
aws-amplify@6.19.0
This release adds analytics auto-tracking configuration support for Kinesis and Kinesis Firehose providers, and introduces an optional telemetry hook for ServiceWorker.register. It also starts runtime deprecation warnings for the default (Amazon Pinpoint) analytics exports and for implicit Pinpoint Service Worker lifecycle auto-recording, while remaining backwards compatible.
Features@aws-amplify/datastore@5.1.9
This patch release hardens @aws-amplify/datastore against an immer prototype pollution issue by bumping immer to a fixed version (^11.1.9). It also updates related Amplify dependencies (@aws-amplify/api and @aws-amplify/api-graphql). No API or behavior changes are called out beyond the dependency security remediation.
Security@aws-amplify/core@6.17.0
This release adds an optional telemetry hook, onStateChange, to ServiceWorker.register in aws-amplify core. It also deprecates the implicit Pinpoint auto-recording of ServiceWorker lifecycle events, moving toward an opt-in model while keeping backward compatibility for now.
Features@aws-amplify/api@6.3.28
This is a patch release of @aws-amplify/api with a single dependency update. No new features or behavior changes are described in the release notes.