Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#123 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
aws, laravel, php
Bereich
backend, cloud

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Keine Sprachdaten
Sterne
199
Forks
5
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus aws/aws-lambda-roadmap

Alle Issues in aws/aws-lambda-roadmap

Ähnliche Issues

Weitere Issues zu Backend & API Design

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.