serverless-haskell-0.8.6: Deploying Haskell code onto AWS Lambda using Serverless

Safe HaskellNone



Tools for running Haskell on AWS Lambda using Serverless.


To deploy a Haskell function on AWS Lambda:

  • Initialise a Serverless project in the same directory as your Stack-enabled package and install the serverless-haskell plugin:

    npm init .
    npm install --save serverless serverless-haskell@x.y.z

    The version of the NPM package to install must match the version of the Haskell package.

  • Create serverless.yml with the following contents:

    service: myservice
      name: aws
      runtime: haskell
        handler: mypackage.mypackage-exe
        # Here, mypackage is the Haskell package name and mypackage-exe is the
        # executable name as defined in the Cabal file
      - serverless-haskell
  • Write your main function using lambdaMain.
  • Use sls deploy to deploy the executable to AWS Lambda.

    The serverless-haskell plugin will build the package using Stack and upload it to AWS together with a JavaScript wrapper to pass the input and output from/to AWS Lambda.

    You can test the function and see the invocation results with sls invoke myfunc.

    To invoke the function locally, use sls invoke local -f myfunc.

API Gateway

This plugin supports handling API Gateway requests. Declare the HTTP events normally in serverless.yml and use APIGateway in the handler to process them.

Serverless Offline can be used for local testing of API Gateway requests.

Additional features

Configuration options are passed to the plugin under haskell key in custom section of serverless.yml.

  • To add flags to stack build, specify them as an array under stackBuildArgs:

          - --pedantic
          - --allow-different-user
  • To start the executable with extra arguments, add them to arguments under the function name:

            - --arg1
            - --arg2
            - arg3
  • Dependent system libraries not present in the AWS Lambda environment will be automatically uploaded along with the executable. Note that while statically linking the executable via Cabal options is possible, it might still require the corresponding glibc version on the AWS environment.
  • Stack's Docker image will be used to match the AWS Lambda Linux environment. To disable this, set docker key to false, but beware that the resulting binary might not have the required libraries to run on Lambda.

        docker: false


lambdaMain Source #


:: (FromJSON event, ToJSON res) 
=> (event -> IO res)

Function to process the event

-> IO () 

Process incoming events from serverless-haskell using a provided function.

The handler receives the input event given to the AWS Lambda function, and its return value is returned from the function.

This is intended to be used as main, for example:

import qualified Data.Aeson as Aeson

import AWSLambda

main = lambdaMain handler

handler :: Aeson.Value -> IO [Int]
handler evt = do
  putStrLn "This should go to logs"
  print evt
  pure [1, 2, 3]

The handler function can receive arbitrary JSON values from custom invocations, or one of the events from the AWSLambda.Events module, such as S3Event:

import AWSLambda.Events.S3Event

handler :: S3Event -> IO ()
handler evt = do
  print $ records evt

If the Lambda function needs to process several types of events, use Alternative to combine several handlers:

import AWSLambda
import AWSLambda.Events.S3Event
import Data.Aeson
import Data.Aeson.Alternative

main = lambdaMain $ handlerS3 `alternative` handlerCustom

handlerS3 :: S3Event -> IO ()
handlerS3 = _

handlerCustom :: Value -> IO ()
handlerCustom = _

When run outside the AWS Lambda environment, the input is read as JSON from the command line, and the result of the execution is printed, also as JSON, to the standard output.