actix_lambda

Crates.ioactix_lambda
lib.rsactix_lambda
version0.2.0
sourcesrc
created_at2019-04-20 12:45:53.334025
updated_at2020-01-01 13:49:56.310308
descriptionRuns your actix-web app as a lambda app that will respond to Application Load Balancer requests
homepagehttps://github.com/palfrey/actix_lambda
repositoryhttps://github.com/palfrey/actix_lambda
max_upload_size
id129092
size57,990
Tom Parker-Shemilt (palfrey)

documentation

README

actix_lambda

Build Status Crates.io MSRV: 1.39.0

Helper libraries for running/testing Actix servers under AWS Lambda

Currently, it just consists of a simple helper function run that will run the entire app as a lambda function, and lambda_test which will feed in a single Application Load Balancer event into the Lambda app.

Usage

use actix_web::{http::Method, HttpRequest, HttpResponse, web};

fn root_handler(request: HttpRequest) -> HttpResponse {
    return HttpResponse::Ok().body("Hello world");
}

fn config(cfg: &mut web::ServiceConfig) {
     cfg.route("/", web::get().to(root_handler));
     // More route handlers
}

fn main() {
    actix_lambda::run(config);
}

#[test]
fn lambda_test() {
    actix_lambda::test::lambda_test(main);
}

In addition to the Rust code, there's also some Python work with CloudFormation and Troposphere to enable building stacks with this. To deploy this do the following:

  1. Have a CLI-configured AWS account
  2. rustup target add x86_64-unknown-linux-musl
  3. brew install filosottile/musl-cross/musl-cross (or do Linux-equivalent steps to get a Musl cross-compiler)
  4. mkdir .cargo && echo '[target.x86_64-unknown-linux-musl]\nlinker = "x86_64-linux-musl-gcc"' > .cargo/config
  5. cargo build --release --target x86_64-unknown-linux-musl
  6. cd <copy of the helpers directory from here>
  7. pip install -r requirements.txt
  8. python cf.py <path to your app's root>
    • This will make a CloudFormation stack named after your app, and then do some custom configuration of the TargetGroup and Listener for the ALB to workaround an upstream bug

You should now be able to run your app from the URL that the script spat out.

TODO

Commit count: 47

cargo fmt