Weave Code
Laravel Bridge Laravel Package
bref/laravel-bridge
Run Laravel on AWS Lambda with Bref. This bridge adapts Laravel for serverless deployment, handling queues, storage, and more, so you can scale without managing servers. Originally by CacheWerk, now maintained by Bref.
bref/laravel-bridge lets you run Laravel applications on AWS Lambda using Bref. It bridges Laravel’s request lifecycle, service container, and configuration with Bref’s serverless runtime, so you can deploy conventional Laravel apps without rewriting them for Lambda. Originally created by CacheWerk and now maintained in the Bref organization, it provides the official integration path for Laravel on Bref 2.0.
- Serverless deployment for Laravel HTTP apps, queues, and scheduled tasks
- Lambda-aware bootstrapping, configuration, and logging
- Artisan and storage integration for serverless workflows
- Bref 2.0 compatibility with official documentation and examples
Frequently asked questions about Laravel Bridge
- How do I install bref/laravel-bridge in a Laravel application?
- Install it with Composer alongside Bref itself by running composer require bref/bref bref/laravel-bridge, then follow the Bref Laravel documentation at bref.sh to set up serverless.yml and the Lambda handler. The package is a library, so there is no Artisan install command; configuration lives in your Bref serverless config and Laravel config files. Commit both composer.json and composer.lock so every deployment resolves the same dependency tree.
- What does bref/laravel-bridge actually provide for Laravel on AWS Lambda?
- It supplies the integration layer Bref needs to run a stock Laravel application: an SQS queue connector so Laravel queues work with Lambda queue consumers, an S3 filesystem adapter, a writable-storage strategy that redirects writes to /tmp because the Lambda filesystem is read-only, and the logging bridge that ships Laravel logs to CloudWatch. Without it you would have to wire all of those pieces manually.
- Which Laravel and Bref versions does bref/laravel-bridge support?
- Version 3.1.3 targets Laravel 10 and 11 on Bref 2.x with PHP 8.1 or newer, which are precisely the stacks the release was aimed at. The bridge has historically tracked Bref majors closely, so confirm your Bref core version against the package support matrix before upgrading. Running a bridge release on a lagging Bref core is the most likely source of friction.
- What changed in bref/laravel-bridge 3.1.3?
- It is a single-line dependency constraint change: the package now allows bref/monolog-bridge ^2.0 alongside the previously permitted 1.x. No PHP source changed, so nothing in your application code or configuration needs to be updated. The practical effect is that Composer can now resolve a Monolog 3 stack for teams on modern Laravel instead of forcing a downgrade or abandoning the log handler.
- Does upgrading to 3.1.3 automatically move my app to Monolog 3?
- No. The constraint is permissive rather than prescriptive, so Composer only picks bref/monolog-bridge 2.0 when your lockfile already permits it or you explicitly require it. A plain composer update may keep you on 1.x and produce no functional change. Check the resolved version in composer.lock after updating rather than assuming the major jumped.
- Is it safe to upgrade bref/laravel-bridge to 3.1.3 in production?
- The release itself is low risk because no code changed, but two teams on the same package version can end up on different Monolog majors depending on their lockfiles. Upgrade in staging first, explicitly require bref/monolog-bridge ^2.0 there, and exercise the full logging surface: request logs, queued job logs, scheduled task logs and uncaught exceptions. Diff the resulting CloudWatch log shape against production before promoting, and keep the previous lockfile so you can revert.
- How does file storage work on Lambda when the filesystem is read-only?
- The bridge redirects Laravel's writable storage paths to /tmp, which is the only writable location during a Lambda invocation. Because /tmp is per-invocation and not persistent or shared, use the bundled S3 filesystem adapter for anything that must survive between requests. Cache and session drivers should also point at external services such as Redis or DynamoDB rather than local files.
- How do I send Laravel logs to CloudWatch on AWS Lambda?
- Configure a channel in config/logging.php that uses the bridge's Monolog handler and make it the default stack channel so framework and application logs share one pipeline. Verify in staging that invocation logs, exception reports and structured context all reach CloudWatch. If you register custom channels or processors, confirm they are compatible with whichever Monolog major your lockfile resolves.
- Who maintains bref/laravel-bridge, and is it still maintained?
- It is maintained by the Bref organization. The package began as cachewerk/bref-laravel-bridge by CacheWerk, created by Till Krüss and George Boot, and was merged into the Bref repository to become bridge v2.0. Recent releases are small dependency-level patches, so maintenance is active but conservative. The next meaningful change is likely dropping the bref/monolog-bridge 1.x branch, so plan a Monolog 3 migration before that lands.
- What are the alternatives to bref/laravel-bridge for running Laravel serverless?
- You can use Bref directly and wire Laravel's queue, storage and logging integration yourself, but that is exactly the work this bridge exists to remove. Laravel Vapor is the managed alternative if you want AWS Lambda without maintaining serverless infrastructure yourself. For most teams deploying a stock Laravel app to Lambda with Bref, this package is the lowest-effort path.
Weaver
How can I help you explore Laravel packages today?