Running Your PHP Site on AWS Lambda
summary
Shows how to run real PHP apps on AWS Lambda layers with the Bref runtime, AWS SAM CLI deployment, API Gateway custom domains and S3 presigned uploads; demonstrates a working Symfony site with sessions moved to a database, assets on a CDN, and console invocations via a Lambda console function. Reveals limits: 250 MB unzipped, 1,000 concurrent default, cold starts up to ~11s on low memory but sub-20ms warm responses; build/deploy scripts and cache warming make it practical.
AI-written summary · about
chapters (36)
- 0:00Intro
- 0:56Why use AWS Lambda
- 2:17The anatomy of AWS Lambda
- 5:31The goal of AWS Lambda
- 6:11What does Bref do
- 6:59What does Sam do
- 9:38How to test locally
- 10:19Fixing an error
- 14:21Cloud Formation
- 17:34Custom Domain Names
- 20:32Recap
- 21:29Fully featured websites
- 22:37Converting to Lambda
- 24:32Exception
- 25:23PDOException
- 26:45Database Connection
- 28:25Deploy
- 32:41Migration
- 34:51Console
- 35:38Migrations
- 37:10Uploading
- 38:52JavaScript
- 39:47Upload Kitty
- 41:04Cold Start
- 42:25Pingdom
- 42:47PHP Lambda
- 43:23Performance benchmarks
- 44:24What about microservices
- 44:46Create a PHP function
- 45:15How do I roll my own
- 45:48MySQL
- 47:18Blackfyre
- 47:47AWS Billing Console
- 48:38What are we working on
- 49:11Join us
- 49:34Questions
related talks
39mServerless PHP applications with Bref
58mPHP on Lambda with Custom Runtimes
34mRunning Symfony on AWS Lambda
44mServerless PHP applications with Bref
01h 03mServerless PHP: how does it really work?
49mPractical Experience Using AWS Lambda in High-Load PHP Applications
50mServerless PHP applications with Bref
02h 08mGoing serverless with PHP and Bref.sh