mirror of
https://github.com/nickpoida/og-aws.git
synced 2025-02-13 02:12:02 +00:00
add lambda failure case, /tmp storage limit.
This commit is contained in:
parent
223357916f
commit
0301570e63
2 changed files with 5 additions and 3 deletions
|
@ -57,6 +57,7 @@ Please help if you can. See the [contribution guidelines](CONTRIBUTING.md) for n
|
|||
* [Patrick McDavid (ehippy)](https://github.com/ehippy) — [1+](https://github.com/open-guides/og-aws/commits?author=ehippy)/[1+](https://github.com/open-guides/og-aws/issues?q=author%3Aehippy)
|
||||
* [Elliott Spira (em0ney)](https://github.com/em0ney) — [5+](https://github.com/open-guides/og-aws/commits?author=em0ney)/[3+](https://github.com/open-guides/og-aws/issues?q=author%3Aem0ney)
|
||||
* [esell (esell)](https://github.com/esell) — [5+](https://github.com/open-guides/og-aws/commits?author=esell)/[1+](https://github.com/open-guides/og-aws/issues?q=author%3Aesell)
|
||||
* [Gabe Abinante (gabinante)](https://github.com/gabinante) — [1+](https://github.com/open-guides/og-aws/commits?author=gabinante)
|
||||
* [Greg Leeds (gleeds)](https://github.com/gleeds) — [2+](https://github.com/open-guides/og-aws/commits?author=gleeds)/[1+](https://github.com/open-guides/og-aws/issues?q=author%3Agleeds)
|
||||
* [Glynn Forrest (glynnforrest)](https://github.com/glynnforrest) — [1+](https://github.com/open-guides/og-aws/commits?author=glynnforrest)/[1+](https://github.com/open-guides/og-aws/issues?q=author%3Aglynnforrest)
|
||||
* [Dmitry Golyshev (golyshev)](https://github.com/golyshev)
|
||||
|
@ -123,4 +124,4 @@ Please let the project leads know of any errors or omissions on this list.
|
|||
|
||||
|
||||
|
||||
(This file was auto-generated by [ghizmo assemble-authors](https://github.com/jlevy/ghizmo).)
|
||||
(This file was auto-generated by [ghizmo assemble-authors](https://github.com/jlevy/ghizmo).)
|
||||
|
|
|
@ -332,7 +332,7 @@ It’s important to know the maturity of each AWS product. Here is a mostly comp
|
|||
|------------------------------------------------------------------------------------------------------------|------------------|-------------------------------------------------------------------------------|:-----------:|:---------------:|:-----------------:|
|
||||
| 🐥[Lex](https://aws.amazon.com/releasenotes/Amazon-Lex?browse=1) | 2016-11 | Preview | | | |
|
||||
| 🐥[Polly](https://aws.amazon.com/releasenotes/Amazon-Polly?browse=1) | 2016-11 | General |✓ | | |
|
||||
| 🐥[Rekognition](https://aws.amazon.com/releasenotes/Amazon-Rekognition?browse=1) | 2016-11 | General |✓ | | |
|
||||
| 🐥[Rekognition](https://aws.amazon.com/releasenotes/Amazon-Rekognition?browse=1) | 2016-11 | General |✓ | | |
|
||||
| 🐥[Athena](http://docs.aws.amazon.com/athena/latest/ug/what-is.html) | 2016-11 | General |✓ | | |
|
||||
| 🐥[Batch](http://docs.aws.amazon.com/batch/latest/userguide/what-is-batch.html) | 2016-11 | General |✓ | | |
|
||||
| 🐥[Database Migration Service](https://aws.amazon.com/releasenotes/AWS-Database-Migration-Service?browse=1) | 2016-03 | General | | ✓ | ✓ |
|
||||
|
@ -1349,11 +1349,12 @@ Lambda
|
|||
- 🔸Managing lots of Lambda functions is a workflow challenge, and tooling to manage Lambda deployments is still immature.
|
||||
- 🔸AWS’ official workflow around managing function [versioning and aliases](https://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases.html) is painful.
|
||||
- 🔸 While adding/removing S3 buckets as triggers for Lambda function, this error may occur: "There was an error creating the trigger: Configuration is ambiguously defined. Cannot have overlapping suffixes in two rules if the prefixes are overlapping for the same event type." In this case, you can manually remove the Lambda event in the "Events" tab in the "Properties" section of the S3 bucket.
|
||||
- When using DynamoDB as a trigger for your Lambda functions, this error may occur: "PROBLEM: internal Lambda error. Please contact Lambda customer support." This usually just means that Lambda can't detect anything in the DynamoDB stream within the last 48 hours. If the issue persists, deleting and recreating your trigger may help.
|
||||
- 🔸 Lambda has several [**resource limits**](http://docs.aws.amazon.com/lambda/latest/dg/limits.html) as of 2017-06:
|
||||
- A **6MB** request or response payload size.
|
||||
- A **50 MB** limit on the compressed .zip/.jar file deployment package size.
|
||||
- A **250 MB** limit on the code/dependencies in the package before compression.
|
||||
|
||||
- A **512 MB** limit on local storage in /tmp
|
||||
|
||||
### Lambda Code Samples
|
||||
|
||||
|
|
Loading…
Reference in a new issue