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 repository shows a very recent upstream push (2026-10-15) and multiple package updates on 2026-10-13, indicating ongoing maintenance rather than a dormant state.
- Update cadence: There is evidence of near-daily activity in the last couple of days (several patch updates across core and service packages on 2026-10-13), with a prior bundle update on 2026-09-28.
AI summary generated
Recent updates
@aws-amplify/pubsub@6.2.2
This patch release updates the underlying dependency on @aws-amplify/auth to version 6.21.2. No other changes, features, bug fixes, or behavior updates are described in the release notes.
@aws-amplify/datastore@5.1.14
This patch release fixes a datastore lifecycle issue where calling DataStore.stop() or DataStore.clear() before the initial sync is ready could hang. It also updates dependencies on @aws-amplify/api and @aws-amplify/api-graphql.
@aws-amplify/api@6.4.3
This is a patch release of @aws-amplify/api that updates key sub-packages. No direct API changes, new features, or bug fixes are described in the release notes.
aws-amplify@6.22.2
This patch improves server-side auth cookie cleanup by ensuring cookies are deleted using the same Path and Domain values they were originally set with. It also updates several Amplify packages (@aws-amplify/core, auth, api, and datastore). If you maintain custom cookie/storage adapters, you may need to account for the new optional delete options.
Features@aws-amplify/core@6.19.3
This patch improves server-side auth cookie cleanup by ensuring cookies are deleted using the same Path and Domain they were originally set with. As a result, Next.js server cookie adapters can correctly remove auth cookies across data, nested-route, and API-route requests.
@aws-amplify/auth@6.21.2
This patch release fixes the Auth behavior when user tokens are cleared without signing the user out. In that scenario, the guest identityId is now retrieved instead of incorrectly reusing the signed-in user's identityId.
@aws-amplify/api-rest@4.7.1
This patch tightens how api-rest resolves REST request URLs against the configured endpoint origin. If a request `path` would change the endpoint host, port, or protocol, the client now rejects the request with an `InvalidPath` validation error instead of sending it to the computed URL.
Breaking@aws-amplify/api-graphql@4.10.2
This patch release updates dependencies used by @aws-amplify/api-graphql, including a newer @aws-amplify/core and @aws-amplify/api-rest. No direct feature changes or bug fixes are described in the release notes.
@aws-amplify/adapter-nextjs@1.8.1
adapter-nextjs@1.8.1 primarily updates server-side auth cookie deletion so cookies are removed using the same Path and Domain they were originally set with. This change requires a corresponding core type change to CookieStorage.Adapter.delete to accept optional DeleteCookieOptions.
aws-amplify@6.22.1
aws-amplify 6.22.1 is a patch release with no documented code changes in the release notes. The main impact is updated dependencies across the Amplify packages it bundles, specifically core, api, and datastore.
@aws-amplify/core@6.19.2
This patch release includes two core fixes. It ensures custom Auth providers passed via `libraryOptions.Auth` are honored when no `Auth` block exists in the resource configuration, and it fixes SSR bundler module resolution issues caused by how `tslib` is bundled and imported.
@aws-amplify/datastore@5.1.13
This patch release of @aws-amplify/datastore primarily updates its upstream dependency versions. No new datastore functionality or user-facing behavior changes are described in the release notes.
@aws-amplify/api-graphql@4.10.1
Release @aws-amplify/api-graphql@4.10.1 is described as a patch-level change that only updates @aws-amplify/core to 6.19.2. The provided diff content, however, shows multiple additions and signature changes in published API docs, implying public surface area changes not mentioned in the release notes.
@aws-amplify/api@6.4.2
This is a patch release of @aws-amplify/api (v6.4.2). The release notes only mention an update to the underlying @aws-amplify/api-graphql dependency.
@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