503 Errors on Livewire Update During S3 File Uploads (Laravel Vapor + Filament)
4️⃣v4
Hello,
We are experiencing 503 (Service Unavailable) errors during file uploads in our application.
Architecture:
Laravel application deployed on Laravel Vapor (AWS Lambda)
FilamentPHP using Livewire
Livewire temporary uploads configured to use S3
Files stored on AWS S3
During uploads, the request fails at:
POST /livewire/update
→ 503 (Service Unavailable)
The failure occurs on the Livewire update endpoint (our Vapor app), not directly on S3. The upload appears to complete on the frontend before this request fails. It's happening with big files for example 2 GB.
We would like clarification on whether this could be caused by Lambda timeouts, memory limits, API Gateway constraints, or concurrency limits in our Vapor environment.
Thank you.
We are experiencing 503 (Service Unavailable) errors during file uploads in our application.
Architecture:
Laravel application deployed on Laravel Vapor (AWS Lambda)
FilamentPHP using Livewire
Livewire temporary uploads configured to use S3
Files stored on AWS S3
During uploads, the request fails at:
POST /livewire/update
→ 503 (Service Unavailable)
The failure occurs on the Livewire update endpoint (our Vapor app), not directly on S3. The upload appears to complete on the frontend before this request fails. It's happening with big files for example 2 GB.
We would like clarification on whether this could be caused by Lambda timeouts, memory limits, API Gateway constraints, or concurrency limits in our Vapor environment.
Thank you.
