Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#123 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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 はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

aws/aws-lambda-roadmap のほかの issue

aws/aws-lambda-roadmap の issue をすべて見る

似ている issue

Backend & API Design の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。