From a2af54dac66a9a195d86a2c9c26150f9a6ee4367 Mon Sep 17 00:00:00 2001
From: Vesa Vilhonen <vesa@vilhonen.com>
Date: Sun, 17 Nov 2019 12:58:03 +0200
Subject: [PATCH] instructions on using via cargo aws-lambda

---
 README.md | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/README.md b/README.md
index f8e3197..c15cd50 100644
--- a/README.md
+++ b/README.md
@@ -54,6 +54,29 @@ $ docker run --rm \
     softprops/lambda-rust
 ```
 
+## 🤸🤸 usage via cargo aws-lambda subcommand
+
+If you want to set up ad hoc lambda functions or have another reason to not to go with full blown devops orchestration tools,
+there's a cargo subcommand to compile your code into a zip file and deploy it to an existing function. This comes with only
+rust and docker as dependencies.
+
+Setup
+```sh
+$ cargo install cargo-aws-lambda
+```
+
+To compile and deploy in your project directory
+```sh
+$ cargo aws-lambda {your aws function's full ARN} {your-binary-name}
+```
+
+To list all options 
+```sh
+$ cargo aws-lambda --help
+```
+
+More instructions can be found [here](https://github.com/vvilhonen/cargo-aws-lambda).
+
 ## 🔬 local testing
 
 Once you've built a Rust lambda function artifact, the `provided` runtime expects