[!NOTE] Last Updated: 2026-07-31
Yes.
The package supports both Web Application (Hosted UI) and API-based authentication, allowing you to choose the authentication experience that best suits your application.
Not directly.
This package is built around Amazon Cognito User Pools, which provide authentication and user management.
If your application requires temporary AWS credentials to access AWS services, you can integrate the User Pool tokens issued by this package with an Identity Pool as part of your architecture.
Yes.
Supporting Amazon Cognito User Pools is the primary purpose of this package. It includes support for the majority of Cognito authentication and user management capabilities, including:
Support continues to evolve alongside new Cognito features.
Yes.
The package is designed to support multiple application architectures, including:
You can expose authentication endpoints without using any server-rendered views.
Yes.
Laravel Fortify can be integrated by replacing its default authentication implementation with Amazon Cognito while continuing to use Fortify’s authentication routes and features.
Yes.
Laravel Breeze provides the frontend scaffolding, while this package replaces the authentication backend with Amazon Cognito. This lets you keep the familiar Breeze experience without storing passwords locally.
The package currently supports:
Support for newer Laravel releases will be added as they become stable.
Yes.
Several migration strategies are supported depending on your requirements:
The appropriate approach depends on whether existing password hashes can be migrated or users need to reset their passwords.
No. This will be supported in a future release.
The package shall support any identity provider configured in your Amazon Cognito User Pool, including:
Configuration is performed in Amazon Cognito, while the package manages the authentication flow.
Yes.
The package supports Amazon Cognito’s WebAuthn (Passkey) authentication, allowing users to authenticate using platform authenticators or security keys instead of passwords.
Refer to the Passkeys Functionality for more details on how to enable and use this feature.
Yes.
The package supports Cognito’s remembered devices and device authentication features. When device tracking is enabled in your User Pool, trusted devices can participate in Cognito’s secure device authentication flow, helping reduce repeated MFA prompts based on your Cognito configuration.
Refer to the Device Authentication section for more details on how to enable and use this feature.
Yes.
A single Amazon Cognito User Pool can authenticate multiple applications using standard OAuth 2.0 and OpenID Connect (OIDC) flows.
This package makes it easy to build centralized authentication services that can be shared across web applications, APIs, mobile applications, and services developed in different programming languages.
Refer the Single Sign-On (SSO) section for more details.
No.
Multi-tenancy is not currently implemented by the package. If your application requires tenant isolation, it must be implemented as part of your application’s architecture or through separate Cognito User Pools.
Yes.
All Blade views published by the package can be customized to match your application’s branding and user experience. You may also bypass the provided views entirely and build your own frontend using the package’s authentication endpoints.
The package supports all major Amazon Cognito authentication methods, including:
This allows you to choose the authentication flow that best fits your application’s security and user experience requirements.