Lambda docs (#264)

* Add aws.md and s3 example

Signed-off-by: Seif Lotfy <seif.lotfy@gmail.com>

* minor fix
This commit is contained in:
Seif Lotfy سيف لطفي
2016-11-11 19:40:22 +01:00
committed by C Cirello
parent 0cc946d937
commit ba65220127
7 changed files with 211 additions and 3 deletions

View File

@@ -36,8 +36,7 @@ Assuming you have a lambda with the following arn `arn:aws:lambda:us-west-2:1231
fnctl lambda aws-import arn:aws:lambda:us-west-2:123141564251:function:my-function us-east-1 user/my-function
```
will import the function code from the region `us-east-1` to a directory called `./my-function`. It will
then create a docker image called `my-function`.
will import the function code from the region `us-east-1` to a directory called `./user/my-function`. Inside the directory you will find the `function.yml`, `Dockerfile`, and all the files needed for running the function.
Using Lambda with Docker Hub and IronFunctions requires that the Docker image be
named `<Docker Hub username>/<image name>`. This is used to uniquely identify
@@ -47,4 +46,10 @@ name>` as the image name with `aws-import` to create a correctly named image.
If you only want to download the code, pass the `--download-only` flag. The
`--profile` flag is available similar to the `aws` tool to help
you tweak the settings on a command level. Finally, you can import a different version of your lambda function than the latest one
by passing `--version <version>.`
by passing `--version <version>.`
You can then publish the imported lambda as follows:
```
./fnctl publish -d ./user/my-function
````
Now the function can be reached via ```http://$HOSTNAME/r/user/my-function```