Laravel packages

Most Laravel packages work on AWS Lambda without changes. This page covers the first-party packages that need configuration, or that do not work on Lambda.

Livewire

Livewire file uploads must use S3 for their temporary files: see Livewire file uploads.

Laravel Telescope

Laravel Telescope  stores its entries in the database, so it needs one: see Databases. It records HTTP requests, Artisan commands and queue jobs processed by the Bref queue worker.

Telescope writes its entries at the end of each request, before the response is returned (code cannot run after the response on Lambda): every recorded request includes these database writes in its duration.

After deploying, create the Telescope table in the production database:

bref command "migrate --force"

serverless bref:cli --args="migrate --force"

Telescope does not delete old entries on its own: run the telescope:prune command every day with the Laravel scheduler, see Cron tasks.

Laravel Pulse

Laravel Pulse  stores its data in the database, so it needs one: see Databases. After deploying, create the Pulse tables with migrate --force, like for Telescope above.

Keep the default ingest driver (storage). The redis ingest driver (PULSE_INGEST_DRIVER=redis) needs php artisan pulse:work, a long-running command that cannot run on Lambda.

The Servers card shows data sent by php artisan pulse:check, another long-running command. Remove <livewire:pulse.servers /> from the dashboard (publish it with php artisan vendor:publish --tag=pulse-dashboard, it is copied to resources/views/vendor/pulse/dashboard.blade.php).

Queue jobs

Pulse stores what it records during jobs when the queue:work loop starts a new iteration. The Bref queue worker does not run that loop: Pulse keeps the data of jobs in memory, where it is lost when the Lambda instance stops, and slow jobs or slow queries of jobs never reach the dashboard. Store it after each job in AppServiceProvider::boot():

use Illuminate\Queue\Events\JobFailed;
use Illuminate\Queue\Events\JobProcessed;
use Illuminate\Support\Facades\Event;
use Laravel\Pulse\Facades\Pulse;
 
public function boot(): void
{
    Event::listen([JobProcessed::class, JobFailed::class], fn () => Pulse::ingest());
}

Laravel Nightwatch

Laravel Nightwatch  does not work on Lambda. The laravel/nightwatch package sends its data to the Nightwatch agent (php artisan nightwatch:agent), a long-running process that listens on 127.0.0.1:2407 (the NIGHTWATCH_INGEST_URI variable). Lambda cannot run that process next to your application.

Without an agent, the package records nothing and logs no error. Disable it on Lambda with NIGHTWATCH_ENABLED: false in provider.environment, or remove the package.

To monitor the application, see Monitoring: Bref Cloud, CloudWatch, and error tracking with Sentry.

Laravel Horizon

Laravel Horizon  does not work on Lambda: it only manages Redis queues, and its horizon command is a long-running process that supervises the queue workers. On Lambda, use SQS queues, which invoke a worker function for each job: see Laravel Queues.

Laravel Reverb

A Laravel Reverb  server is a long-running process that cannot run on Lambda. Laravel broadcasting and Laravel Echo work with API Gateway WebSockets instead: see WebSockets, which also explains when to run a Reverb server next to Lambda.