Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Feature [Lambda] Managed PHP runtime (php8.x on AL2023), including Lambda Web Functions

未关闭
  • 哪里不对？
#123 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
aws, laravel, php
领域
backend, cloud

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

  1. A managed php8.x runtime 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.
  2. The common extensions included, or offered as documented, AWS-maintained layers.
  3. Official base images (public.ecr.aws/lambda/php) for Web Functions container deployments.
  4. 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 intl alone 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.

主要语言
没有语言数据
星标
199
派生
5
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

aws/aws-lambda-roadmap 的其他 Issue

查看 aws/aws-lambda-roadmap 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。