regular update for Lambda docs on github

Author: spaethp

doc_source/API_Invoke.md

@@ -30,7 +30,8 @@ The request requires the following URI parameters\.
 
  ** [ClientContext](#API_Invoke_RequestSyntax) **   <a name="SSS-Invoke-request-ClientContext"></a>
 Using the `ClientContext` you can pass client\-specific information to the Lambda function you are invoking\. You can then process the client information in your Lambda function as you choose through the context variable\. For an example of a `ClientContext` JSON, see [PutEvents](https://docs.aws.amazon.com/mobileanalytics/latest/ug/PutEvents.html) in the *Amazon Mobile Analytics API Reference and User Guide*\.  
-The ClientContext JSON must be base64\-encoded and has a maximum size of 3583 bytes\.
+The ClientContext JSON must be base64\-encoded and has a maximum size of 3583 bytes\.  
+ `ClientContext` information is returned only if you use the synchronous \(`RequestResponse`\) invocation type\.
 
  ** [FunctionName](#API_Invoke_RequestSyntax) **   <a name="SSS-Invoke-request-FunctionName"></a>
 The Lambda function name\.  

doc_source/API_ListFunctions.md

@@ -33,7 +33,7 @@ The region from which the functions are replicated\. For example, if you specify
 Pattern: `ALL|[a-z]{2}(-gov)?-[a-z]+-\d{1}` 
 
  ** [MaxItems](#API_ListFunctions_RequestSyntax) **   <a name="SSS-ListFunctions-request-MaxItems"></a>
-Optional integer\. Specifies the maximum number of AWS Lambda functions to return in response\. This parameter value must be greater than 0\.  
+Optional integer\. Specifies the maximum number of AWS Lambda functions to return in response\. This parameter value must be greater than 0\. The absolute maximum of AWS Lambda functions that can be returned is 50\.  
 Valid Range: Minimum value of 1\. Maximum value of 10000\.
 
 ## Request Body<a name="API_ListFunctions_RequestBody"></a>

doc_source/aliases-intro.md

@@ -1,6 +1,6 @@
 # Introduction to AWS Lambda Aliases<a name="aliases-intro"></a>
 
-You can create one or more aliases for your Lambda function\. An* AWS Lambda alias* is like a pointer to a specific Lambda function version\. For more information about versioning, see [Introduction to AWS Lambda Versioning](versioning-intro.md)\. 
+You can create one or more aliases for your Lambda function\. An AWS Lambda alias is like a pointer to a specific Lambda function version\. For more information about versioning, see [Introduction to AWS Lambda Versioning](versioning-intro.md)\. 
 
 By using aliases, you can access the Lambda function an alias is pointing to \(for example, to invoke the function\) without the caller having to know the specific version the alias is pointing to\.
 
@@ -32,7 +32,7 @@ You can access the function using either the function ARN or the alias ARN\.
   arn:aws:lambda:aws-region:acct-id:function:helloworld:DEV
   ```
 
-AWS Lambda provides the following API operations for you to create and manages aliases:
+AWS Lambda provides the following API operations for you to create and manage aliases:
 + [CreateAlias](API_CreateAlias.md)
 + [UpdateAlias](API_UpdateAlias.md)
 + [GetAlias](API_GetAlias.md)

doc_source/best-practices.md

@@ -46,7 +46,7 @@ The following are recommended best practices for using AWS Lambda:
 + **Use most\-restrictive permissions when setting IAM policies\.** Understand the resources and operations your Lambda function needs, and limit the execution role to these permissions\. For more information, see [Authentication and Access Control for AWS Lambda](lambda-auth-and-access-control.md)\. 
 + **Be familiar with [AWS Lambda Limits](limits.md)\.** Payload size, file descriptors and /tmp space are often overlooked when determining runtime resource limits\. 
 + **Delete Lambda functions that you are no longer using\.** By doing so, the unused functions won't needlessly count against your deployment package size limit\.
-+ **If you are using Amazon Simple Queue Service** as an event source, make sure the value of the function's expected execution time does not exceed the [Visibility Timeout](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html) value on the queue\. This applies both [CreateFunction](API_CreateFunction.md) and [UpdateFunctionConfiguration](API_UpdateFunctionConfiguration.md)\. 
++ **If you are using Amazon Simple Queue Service** as an event source, make sure the value of the function's expected execution time does not exceed the [Visibility Timeout](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html) value on the queue\. This applies both to [CreateFunction](API_CreateFunction.md) and [UpdateFunctionConfiguration](API_UpdateFunctionConfiguration.md)\. 
   + In the case of **CreateFunction**, AWS Lambda will fail the function creation process\.
   + In the case of **UpdateFunctionConfiguration**, it could result in duplicate invocations of the function\.
 

doc_source/build-pipeline.md

@@ -150,7 +150,7 @@ To set up your repository, do the following:
       });
   };
   ```
-+ Add a *samTemplate\.yaml* file, containing the content following\. This is4 the SAM template that defines the resources in your application\. This SAM template defines a Lambda function that is triggered by API Gateway\. Note that the `runtime` parameter uses `nodejs6.10` but you can also specify `nodejs8.10`\. For more information about AWS SAM see [AWS Serverless Application Model](https://github.com/awslabs/serverless-application-model)\.
++ Add a *samTemplate\.yaml* file, containing the content following\. This is for the SAM template that defines the resources in your application\. This SAM template defines a Lambda function that is triggered by API Gateway\. Note that the `runtime` parameter uses `nodejs6.10` but you can also specify `nodejs8.10`\. For more information about AWS SAM see [AWS Serverless Application Model](https://github.com/awslabs/serverless-application-model)\.
 
   ```
   AWSTemplateFormatVersion: '2010-09-09'
@@ -175,12 +175,12 @@ To set up your repository, do the following:
   + Run the `Package` command to prepare your deployment package for subsequent deployment steps in your pipeline\. For more information on the package command, see [Uploading Local Artifacts to an S3 Bucket](http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-cli-package.html)
 
     ```
-    version: 0.1
+    version: 0.2
     phases:
       install:
         commands:
           - npm install time
-          - aws cloudformation package --template-file samTemplate.yaml --s3-bucket bucket-name 
+          - aws cloudformation package --template-file samTemplate.yaml --kms-key-id kms-key-id --s3-bucket bucket-name 
                                        --output-template-file outputSamTemplate.yaml
     artifacts:
       type: zip

doc_source/getting-started.md

@@ -5,7 +5,7 @@ In this section, we introduce you to the fundamental concepts of a typical Lambd
 ## Building Blocks of a Lambda\-based Application<a name="lambda-application-fundamentals"></a>
 + **Lambda function: **The foundation, it is comprised of your custom code and any dependent libraries\. For more information, see [Lambda Functions](lambda-introduction-function.md)\.
 + **Event source: ** An AWS service, such as Amazon SNS, or a custom service, that triggers your function and executes its logic\. For more information, see [Event Source Mapping](invocation-options.md#intro-invocation-modes)\.
-+ **Downstream resources: **An AWS service, such DynamoDB tables or Amazon S3 buckets, that your Lambda function calls once it is triggered\. 
++ **Downstream resources: **An AWS service, such as DynamoDB tables or Amazon S3 buckets, that your Lambda function calls once it is triggered\. 
 + **Log streams: **While Lambda automatically monitors your function invocations and reports metrics to CloudWatch, you can annotate your function code with custom logging statements that allow you to analyze the execution flow and performance of your Lambda function to ensure it's working properly\.
 + **AWS SAM: **A model to define [serverless applications](https://aws.amazon.com/serverless)\. AWS SAM is natively supported by AWS CloudFormation and defines simplified syntax for expressing serverless resources\. For more information, see [Using the AWS Serverless Application Model \(AWS SAM\)](serverless_app.md)
 

doc_source/history.md

@@ -47,8 +47,8 @@ The following table describes the important changes in each release of the *AWS
 | Content reorganization | The reorganized content now provides the following: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/lambda/latest/dg/history.html)  | December 9, 2015  | 
 |  AWS Lambda runtime has been updated\.   |   AWS Lambda runtime has been updated with the following SDK and Linux kernel versions in this release: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/lambda/latest/dg/history.html) For more information, see [Lambda Execution Environment and Available Libraries](current-supported-versions.md)\.  | November 4, 2015 | 
 |  Versioning support, Python for developing code for Lambda functions, scheduled events, and increase in execution time   |   AWS Lambda introduces the following features in this release\. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/lambda/latest/dg/history.html)  | October 08, 2015 | 
-|  Two new walkthroughs   |   The following new walkthroughs are added\. They both use Java Lambda function\.   [Tutorial: Using AWS Lambda with Amazon DynamoDB](with-ddb-example.md)    [Using AWS Lambda as Mobile Application Backend \(Custom Event Source: Android\)](with-on-demand-custom-android.md)   | August 27, 2015 | 
-|  Support for DynamoDB Streams   |   DynamoDB Streams is now generally available and you can use it in all the regions where DynamoDB is available\. You can enable DynamoDB Streams for your table and use a Lambda function as a trigger for the table\. Triggers are custom actions you take in response to updates made to the DynamoDB table\. For an example walkthrough, see  [Tutorial: Using AWS Lambda with Amazon DynamoDB](with-ddb-example.md) \. | July 14, 2015 | 
+|  Two new walkthroughs   |   The following new walkthroughs are added\. They both use Java Lambda function\.   [Tutorial: Using AWS Lambda with Amazon DynamoDB ](with-ddb-example.md)    [Using AWS Lambda as Mobile Application Backend \(Custom Event Source: Android\)](with-on-demand-custom-android.md)   | August 27, 2015 | 
+|  Support for DynamoDB Streams   |   DynamoDB Streams is now generally available and you can use it in all the regions where DynamoDB is available\. You can enable DynamoDB Streams for your table and use a Lambda function as a trigger for the table\. Triggers are custom actions you take in response to updates made to the DynamoDB table\. For an example walkthrough, see  [Tutorial: Using AWS Lambda with Amazon DynamoDB ](with-ddb-example.md) \. | July 14, 2015 | 
 |   AWS Lambda now supports invoking Lambda functions with REST\-compatible clients\.   |  Until now, to invoke your Lambda function from your web, mobile, or IoT application you needed the AWS SDKs \(for example, AWS SDK for Java, AWS SDK for Android, or AWS SDK for iOS\)\. Now, AWS Lambda supports invoking a Lambda function with REST\-compatible clients through a customized API that you can create using Amazon API Gateway\. You can send requests to your Lambda function endpoint URL\. You can configure security on the endpoint to allow open access, leverage AWS Identity and Access Management \(IAM\) to authorize access, or use API keys to meter access to your Lambda functions by others\.  For an example Getting Started exercise, see  [Using AWS Lambda with Amazon API Gateway \(On\-Demand Over HTTPS\)](with-on-demand-https.md)\.  For more information about the Amazon API Gateway, see [https://aws\.amazon\.com/api\-gateway/](https://aws.amazon.com/api-gateway/)\.   | July 09, 2015 | 
 |   The AWS Lambda console now provides blueprints to easily create Lambda functions and test them\.   |  AWS Lambda console provides a set of *blueprints*\. Each blueprint provides a sample event source configuration and sample code for your Lambda function that you can use to easily create Lambda\-based applications\. All of the AWS Lambda Getting Started exercises now use the blueprints\. For more information, see [Getting Started](getting-started.md)\.   | In this release  | 
 |  AWS Lambda now supports Java to author your Lambda functions\.   |  You can now author Lambda code in Java\. For more information, see  [Programming Model](programming-model-v2.md)\.  | June 15, 2015 | 

doc_source/limits.md

@@ -81,7 +81,7 @@ The following table lists service limits for deploying a Lambda function\.
 | --- | --- | 
 | Lambda function deployment package size \(compressed \.zip/\.jar file\) | 50 MB | 
 | Total size of all the deployment packages that can be uploaded per region | 75 GB | 
-| Size of code/dependencies that you can zip into a deployment package \(uncompressed \.zip/\.jar size\)\. Each Lambda function receives an additional 500MB of non\-persistent disk space in its own `/tmp` directory\. The `/tmp` directory can be used for loading additional resources like dependency libraries or data sets during function initialization\.  | 250 MB | 
+| Size of code/dependencies that you can zip into a deployment package \(uncompressed \.zip/\.jar size\)\. Each Lambda function receives an additional 512MB of non\-persistent disk space in its own `/tmp` directory\. The `/tmp` directory can be used for loading additional resources like dependency libraries or data sets during function initialization\.  | 250 MB | 
 | Total size of environment variables set | 4 KB | 
 
 **Note**  

doc_source/python-context-object.md

@@ -75,15 +75,15 @@ The name of the CloudWatch log group where you can find logs written by your Lam
 
 **log\_stream\_name**  
  The name of the CloudWatch log stream where you can find logs written by your Lambda function\. The log stream may or may not change for each invocation of the Lambda function\.  
-The value is null if your Lambda function is unable to create a log stream, which can happen if the execution role that grants necessary permissions to the Lambda function does not include permissions for the CloudWatch Logs actions\.
+The value is none if your Lambda function is unable to create a log stream, which can happen if the execution role that grants necessary permissions to the Lambda function does not include permissions for the CloudWatch Logs actions\.
 
 **identity**  
-Information about the Amazon Cognito identity provider when invoked through the AWS Mobile SDK\. It can be null\.  
+Information about the Amazon Cognito identity provider when invoked through the AWS Mobile SDK\. It can be none\.  
 + **identity\.cognito\_identity\_id**
 + **identity\.cognito\_identity\_pool\_id**
 
 **client\_context**  
-Information about the client application and device when invoked through the AWS Mobile SDK\. It can be null\.  
+Information about the client application and device when invoked through the AWS Mobile SDK\. It can be none\.  
 + **client\_context\.client\.installation\_id**
 + **client\_context\.client\.app\_title**
 + **client\_context\.client\.app\_version\_name**

doc_source/retries-on-errors.md

@@ -24,9 +24,9 @@ If any of these failures occur, your function will throw an exception\. How the
 + **Poll\-based \(or pull model\) event sources that are stream\-based**: These consist of Kinesis Data Streams or DynamoDB\. When a Lambda function invocation fails, AWS Lambda attempts to process the erring batch of records until the time the data expires, which can be up to seven days\. 
 
   The exception is treated as blocking, and AWS Lambda will not read any new records from the shard until the failed batch of records either expires or is processed successfully\. This ensures that AWS Lambda processes the stream events in order\.
-+ **Poll\-based event sources that are not stream\-based:** This consists of Amazon Simple Queue Service\. If you configure an Amazon SQS queue as an event source, AWS Lambda will poll a batch of records in the queue and invoke your Lambda function\. If it fails, AWS Lambda will continue to process other messages in the batch\. Meanwhile, AWS Lambda will continue to retry processing the failed message until one of the following happens: 
-  + **The message is ultimately invoked successfully:** In this case, the message is removed from the queue\.
-  + **The message retention period expires:** In this case, the message is either discarded or if you have configured an [Amazon SQS Dead Letter Queue](http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-dead-letter-queue.html), the failure information will be directed there for you to analyze\. 
++ **Poll\-based event sources that are not stream\-based:** This consists of Amazon Simple Queue Service\. If you configure an Amazon SQS queue as an event source, AWS Lambda will poll a batch of records in the queue and invoke your Lambda function\. If the invocation fails or times out, the message will be returned to the queue and will be available for invocation once the [Visibility Timeout](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html) period expires\. \(Visibility timeouts are a period of time during which Amazon Simple Queue Service prevents other consumers from receiving and processing the message\)\.
+
+   This process will continue until either the message is invoked successfully, in which case it is removed from the queue, or the message retention period expires\. In this case, the message is either discarded or if you have configured an [Amazon SQS Dead Letter Queue](http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-dead-letter-queue.html), the failure information will be directed there for you to analyze\. 
 
 If you don't require ordered processing of events, the advantage of using Amazon SQS queues is that AWS Lambda will continue to process new messages, regardless of a failed invocation of a previous message\. In other words, processing of new messages will not be blocked\.