PHPackages                             vognev/laravel-serverless-aws - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Framework](/categories/framework)
4. /
5. vognev/laravel-serverless-aws

ActiveLibrary[Framework](/categories/framework)

vognev/laravel-serverless-aws
=============================

Laravel/Serverless for AWS Lambda

v0.0.1(6y ago)06MITPHPPHP >=7.2.0

Since Sep 25Pushed 6y agoCompare

[ Source](https://github.com/vognev/laravel-serverless-aws)[ Packagist](https://packagist.org/packages/vognev/laravel-serverless-aws)[ RSS](/packages/vognev-laravel-serverless-aws/feed)WikiDiscussions master Synced today

READMEChangelogDependencies (4)Versions (2)Used By (0)

laravel-serverless-aws
======================

[](#laravel-serverless-aws)

Package's aim is to provide a possibility to deploy Laravel application as an [AWS Lambda](https://aws.amazon.com/lambda/) function.

Installation
------------

[](#installation)

Package can be installed into existing project using composer:

`composer require vognev/laravel-serverless-aws`

But this is rather a helper to build custom php runtime to be run in AWS environment; for fully operational setup you should also install [serverless framework](https://serverless.com/) globally:

`npm install -g serverless`

It will provide binary named `sls` (`serverless`), which will be used for deployments.

Also, you need `docker` and have an `aws-cli` utility installed and configured:

`aws configure`

Initialization
--------------

[](#initialization)

Run `php artisan serverless:install` command.

It will publish:

#### config/serverless.php

[](#configserverlessphp)

This is a configuration file, where you can tweak package's behaviour. Apart from being able to define where to store package's data, it's aim is to configure which php modules (since lambda runtime size is limited) should be included in runtime.

#### storage/serverless

[](#storageserverless)

On default all runtime-related assets will be published here. Inside of this location you can find `context` and `runtime` folders, holding docker's context to build a runtime, and unpacked php runtime respectively.

#### .php.conf.d

[](#phpconfd)

In this folder you can tweak php modules options, or add your own `.ini` configs.

#### serverless.yml

[](#serverlessyml)

Project description for serverless framework used for deployment.

#### docker-compose.serverless.yml

[](#docker-composeserverlessyml)

Standalone and sample docker-compose stack aimed to mock production environment and suitable for local development.

Building Runtime
----------------

[](#building-runtime)

AWS Lambda function consists of several `layers`. We're going to build `runtime` layer (providing php binary).

Runtime is built using docker and context seen in `storage/serverless/context` directory. Build process will produce `php` binary with several `.so` modules configured to be invoked from `/opt/` (the place where lambda layer will be unpacked) in portable manner (in order to not depend on missing shared libraries in AWS environment)

See [Custom AWS Lambda Runtimes](https://docs.aws.amazon.com/en_us/lambda/latest/dg/runtimes-custom.html) for more details.

In Dockerfile you can find several stages:

- sources - to fetch and unpack php (and other) sources
- builder - which will build unpacked sources
- bundler - will make portable php distribution under /opt

Once context is published, you can add it to VCS and tweak to fit your needs. One aspect of tweaking is just update the list of php modules (config/serverless.php) to build (available ones can be found in storage/serverless/context/php-modules.sh). Also, nothing can stop you from building additional `pecl` modules, changing PHP version or even rewriting whole Dockerfile.

When done, run `php artisan serverless:runtime` and find it built under `storage/serverless/runtime`.

Hint: you can speed up build by usind Docker-in-Docker (dind) using `tmpfs` for storage, we do not need any persistence from it:

```
docker run --name dind -d --tmpfs=/var/lib/docker --privileged -p 2375:2375 \
  --entrypoint dockerd docker:dind --host tcp://0.0.0.0:2375
DOCKER_HOST=127.0.0.1:2375 php artisan serverless:runtime

```

Serverless Configuration
------------------------

[](#serverless-configuration)

Deployment is configured by tweaking `serverless.yml` options.

#### Service name

[](#service-name)

Key `service` names your project in AWS.

```
service: workbench
```

#### Provider

[](#provider)

`provider.name` is always equal to `aws`, since we're deploying to AWS Lambda.

`provider.region` holds region name to deploy function to.

`provider.runtime` is always equal to `privided`, since we're building own php runtime (php is not available on AWS).

```
provider:
  name: aws
  region: eu-central-1
  runtime: provided
```

#### Environment Variables

[](#environment-variables)

AWS Lambda filesystem is read-only (except `/tmp`), so, for Laravel, we should update various writeable paths to point to location inside of it. On initialization, function's bootstrap script will create these folders, so we just tweak them via environment variables.

Also, it is not guaranteed that different requests will be handled by same function instance, so, session also should be persisted in external storage or in cookies only.

These variables should be set as early as possible, so we cannot depend on `.env` variables and injecting them into function process instead.

```
provider:
  environment:
    LOG_CHANNEL: stderr
    SESSION_DRIVER: cookie
    APP_PACKAGES_CACHE: /tmp/packages.php
    APP_SERVICES_CACHE: /tmp/services.php
    APP_CONFIG_CACHE: /tmp/config.php
    APP_ROUTES_CACHE: /tmp/routes.php
    APP_EVENTS_CACHE: /tmp/events.php
```

#### Layers

[](#layers)

Here we're telling Serverless Framework, that we're going to use our custom-build `runtime` and specifying it's location.

```
layers:
  runtime:
    retain: false
    package:
      artifact: storage/serverless/runtime.zip
```

#### Include/Exclude

[](#includeexclude)

Here you can tell which paths (using glob expressions) to include or exclude in final function layer.

```
package:
  include:
    - tests/TestCase.php
  exclude:
    - .idea/**
    - storage/**
    - node_modules/**
    - bootstrap/cache/**
    - tests/**
```

#### Website function

[](#website-function)

This function serving http entrypoint of project, so, we have to define http events for it, and then Serverless will create [function api gateway](https://docs.aws.amazon.com/lambda/latest/dg/with-on-demand-https-example.html) for us.

Note: we're also composing function from the source code itself, and custom php runtime we're building (using `layers` key of yml)

```
functions:
  website:
    handler: website
    memorySize: 128
    timeout: 30
    events:
      - http: 'ANY /'
      - http: 'ANY /{proxy+}'
    layers:
      - { Ref: RuntimeLambdaLayer }
```

### Artisan function

[](#artisan-function)

This function serving cli entrypoint of project. Here we already defining [CloudWatch Events](https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/WhatIsCloudWatchEvents.html) trigger which will fire Laravel's schedule command.

```
  artisan:
    handler: artisan
    memorySize: 128
    timeout: 900
    events:
      - schedule:
          rate: rate(1 minute)
          input:
            - 'schedule:run'
            - '--no-ansi'
            - '-n'
          enabled: true
    layers:
      - { Ref: RuntimeLambdaLayer }
```

### SQS Queue

[](#sqs-queue)

In order to be able to run and schedule queued jobs by app, it is possible to configure [SQS Queue](https://aws.amazon.com/sqs/) for app. Serverless Framework will not create it for you, so, you should create it manually using AWS Management Console.

Next, you should ensure that sqs queue configuration is including `token` parameter, so update your `config/queue.php` file accordingly:

```
return [
  'sqs' => [
     'token' => env('AWS_SESSION_TOKEN')
  ]
];
```

Then, require aws-sdk for php (`composer require aws/aws-sdk-php`), so you'll have working SQS Queue Driver, and, configure it using environment variables section of `serverless.yml`:

```
provider:
  environment:
    QUEUE_CONNECTION: sqs
    SQS_PREFIX: https://sqs..amazonaws.com//
    SQS_QUEUE:
```

and define SQS trigger for `artisan` function:

```
functions:
  artisan:
    events:
      - sqs:
          arn: arn:aws:sqs:::
          enabled: true
          batchSize: 1
```

At this point, Role of function will prevent it from sendind messages into queue; so, once you have deployed your function, go to [IAM](https://console.aws.amazon.com/iam/home), find the Role associated with your function, and edit it's policy to include SQS.SendMessage action.

Deployment
==========

[](#deployment)

After steps above are done, you can deploy your project into AWS using `sls deploy` command.

###  Health Score

20

—

LowBetter than 14% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity4

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity43

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Unknown

Total

1

Last Release

2421d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/679032?v=4)[vognev](/maintainers/vognev)[@vognev](https://github.com/vognev)

---

Top Contributors

[![vognev](https://avatars.githubusercontent.com/u/679032?v=4)](https://github.com/vognev "vognev (3 commits)")

---

Tags

laravelserverlesslambda

### Embed Badge

![Health badge](/badges/vognev-laravel-serverless-aws/health.svg)

```
[![Health](https://phpackages.com/badges/vognev-laravel-serverless-aws/health.svg)](https://phpackages.com/packages/vognev-laravel-serverless-aws)
```

###  Alternatives

[bref/laravel-bridge

An advanced Laravel integration for Bref, including Octane support.

3384.1M11](/packages/bref-laravel-bridge)[hemp/presenter

Easy Model Presenters in Laravel

247592.6k1](/packages/hemp-presenter)[rahulalam31/laravel-abuse-ip

Block ip address of all spammer's around the world.

27431.5k](/packages/rahulalam31-laravel-abuse-ip)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)