Feature [Lambda] Managed PHP runtime (php8.x on AL2023), including Lambda Web Functions
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 25/100
Direção de pesquisa
The request covers a managed PHP runtime for Lambda Web Functions, extensions, container images, and support in SAM, CDK, and the console; it does not name implementation files or tests. Start by reading the Lambda Web Functions and managed runtime documentation to understand the runtime requirements. Done means AWS provides the requested managed PHP runtime and supporting deployment options with patching and deprecation guarantees.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
If you are interested in providing additional feedback, please leave a comment
Description
Add a managed PHP runtime for Lambda Web Functions (for example php8.4 and php8.5 on Amazon Linux 2023, x86_64 and arm64), with the same guarantees as the other managed runtimes: security patches, minor version updates, and a published deprecation schedule.
Lambda Web Functions are a natural fit for PHP. PHP is primarily a web language, and Web Functions run the app as an HTTP server with its own endpoint, many concurrent requests per execution environment, and streaming. There is no API Gateway and no event translation. Modern PHP application servers (FrankenPHP, Laravel Octane, RoadRunner) already work this way: they boot the framework once and serve requests from memory.
Today the only way to run PHP on Web Functions is a custom runtime (provided.al2023) or a container image. Every team has to:
- compile and maintain its own PHP binary and extensions (
intl,pdo_pgsql,gd,redis…) for both architectures; - track PHP, OpenSSL, ICU and libcurl security releases, then rebuild and redeploy every function;
- package and start the HTTP server itself;
- accept larger artifacts and slower cold starts than a managed runtime would give.
What we are asking for
- A managed
php8.xruntime for Lambda Web Functions. Lambda starts a PHP HTTP server (for example FrankenPHP in worker mode, or PHP-FPM behind a managed front) on the port Web Functions expect, so users ship only their application code. - The common extensions included, or offered as documented, AWS-maintained layers.
- Official base images (
public.ecr.aws/lambda/php) for Web Functions container deployments. - Support in SAM, CDK and the console, and Lambda-managed runtime patching.
Additional context
We maintain Arco, an open-source CLI that deploys Laravel to Lambda Web Functions using FrankenPHP and Laravel Octane on provided.al2023. Measurements from building our own runtime:
- a full PHP runtime with common extensions is ~95 MB unpacked;
- a minimal runtime for Laravel is ~32.5 MB (~9.6 MB gzipped);
- adding
intlalone brings it to ~70 MB, because the ICU data is ~37 MB.
Most of this work (compiling PHP, choosing extensions, keeping native libraries patched for two architectures) is the same for every PHP user, so it belongs in a managed runtime. We are happy to share build details, test preview versions, and give feedback.
Related projects: FrankenPHP, Laravel Octane, Bref.
- Linguagem predominante
- Sem dados de linguagem
- Estrelas
- 199
- Forks
- 5
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de aws/aws-lambda-roadmap
-
Feature-Lambda SnapStart support for larger ephemeral storageTalvez já em andamento @prerna-aws assumiu há 3 dias. Aberta
aws/aws-lambda-roadmap#122 · 1 responsável ·
-
Feature- Lambda Dev Sandbox to accelerate local developmentTalvez já em andamento @prerna-aws assumiu há 3 dias. AbertaLambda/Developer Experience
aws/aws-lambda-roadmap#121 · 1 responsável ·
-
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 30/100
aws/aws-lambda-roadmap#120 · 3 comentários · 2 reações ·
-
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 25/100
aws/aws-lambda-roadmap#119 · 45 reações ·
-
[Lambda Web Functions] Mutable region set on an endpoint, plus per-region health-based routingAbertaLambda/Developer Experience Lambda/Web Functions
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 6/100
aws/aws-lambda-roadmap#118 · 3 comentários · 2 reações ·
Todas as issues de aws/aws-lambda-roadmap
Issues semelhantes
-
bug ready-for-agent
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 73/100
PhyberApex/kuroshiro#1687 ·
Mantenedores costumam responder em até 1 dia
-
Provider test fails on official OpenAI preset: chat probe sends max_tokens, rejected by newer modelsAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 1 dia
-
general_error() logs every 4xx response at ERROR level, including expected 400, 404 and 409 outcomesAbertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
awslabs/visual-asset-management-system#935 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100
Mantenedores costumam responder em até 1 dia
-
vim.filetype.match() prefixes a URL buffer name with the cwd before passing it to filetype functionsAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 73/100
Mantenedores costumam responder em até 1 dia