enable rss feeds for document history page, plus some minor doc updates

mark-hirayama · mark-hirayama · commit d1136cf4c021 · 2018-07-09T16:02:44.000Z
diff --git a/doc_source/API_AliasRoutingConfiguration.md b/doc_source/API_AliasRoutingConfiguration.md
@@ -1,6 +1,6 @@
 # AliasRoutingConfiguration<a name="API_AliasRoutingConfiguration"></a>
 
-The parent object that implements what percentage of traffic will invoke each function version\. For more information, see [Traffic Shifting Using Aliases](lambda-traffic-shifting-using-aliases.md)\.
+The parent object that implements what percentage of traffic will invoke each function version\. For more information, see [Traffic Shifting Using Aliases](lambda-traffic-shifting-using-aliases.md)\. The maximum number of stream records that can be sent to your Lambda function for a single invocation\. ng\-using\-aliases"/>\.
 
 ## Contents<a name="API_AliasRoutingConfiguration_Contents"></a>
 
diff --git a/doc_source/API_CreateFunction.md b/doc_source/API_CreateFunction.md
@@ -120,7 +120,7 @@ The runtime environment for the Lambda function you are uploading\.
 To use the Python runtime v3\.6, set the value to "python3\.6"\. To use the Python runtime v2\.7, set the value to "python2\.7"\. To use the Node\.js runtime v8\.10, set the value to "nodejs8\.10"\. To use Node\.js runtime version v6\.10, set the value to "nodejs6\.10"\. To use the \.NET Core runtime v1\.0, set the value to "dotnetcore1\.0"\. To use the \.NET Core runtime v2\.0, set the value to "dotnetcore2\.0"\.  
 Node v0\.10\.42 and node v4\.3 are currently marked as deprecated\. You must migrate existing functions to the newer Node\.js runtime versions available on AWS Lambda \(nodejs8\.10, nodejs6\.10\) as soon as possible\. Failure to do so will result in an invalid parameter error being returned\. Note that you will have to follow this procedure for each region that contains functions written in the Node v0\.10\.42 runtime\.
 Type: String  
-Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x`   
+Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | nodejs8.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x`   
 Required: Yes
 
  ** [Tags](#API_CreateFunction_RequestSyntax) **   <a name="SSS-CreateFunction-request-Tags"></a>
@@ -264,7 +264,7 @@ Pattern: `arn:aws:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\-_/]+`
  ** [Runtime](#API_CreateFunction_ResponseSyntax) **   <a name="SSS-CreateFunction-response-Runtime"></a>
 The runtime environment for the Lambda function\.  
 Type: String  
-Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x` 
+Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | nodejs8.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x` 
 
  ** [Timeout](#API_CreateFunction_ResponseSyntax) **   <a name="SSS-CreateFunction-response-Timeout"></a>
 The function execution time at which Lambda should terminate the function\. Because the execution time has cost implications, we recommend you set this value based on your expected execution time\. The default is 3 seconds\.  
diff --git a/doc_source/API_FunctionConfiguration.md b/doc_source/API_FunctionConfiguration.md
@@ -87,7 +87,7 @@ Required: No
  **Runtime**   <a name="SSS-Type-FunctionConfiguration-Runtime"></a>
 The runtime environment for the Lambda function\.  
 Type: String  
-Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x`   
+Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | nodejs8.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x`   
 Required: No
 
  **Timeout**   <a name="SSS-Type-FunctionConfiguration-Timeout"></a>
diff --git a/doc_source/API_GetFunctionConfiguration.md b/doc_source/API_GetFunctionConfiguration.md
@@ -152,7 +152,7 @@ Pattern: `arn:aws:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\-_/]+`
  ** [Runtime](#API_GetFunctionConfiguration_ResponseSyntax) **   <a name="SSS-GetFunctionConfiguration-response-Runtime"></a>
 The runtime environment for the Lambda function\.  
 Type: String  
-Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x` 
+Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | nodejs8.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x` 
 
  ** [Timeout](#API_GetFunctionConfiguration_ResponseSyntax) **   <a name="SSS-GetFunctionConfiguration-response-Timeout"></a>
 The function execution time at which Lambda should terminate the function\. Because the execution time has cost implications, we recommend you set this value based on your expected execution time\. The default is 3 seconds\.  
diff --git a/doc_source/API_Invoke.md b/doc_source/API_Invoke.md
@@ -2,7 +2,11 @@
 
 Invokes a specific Lambda function\. For an example, see [Create the Lambda Function and Test It Manually](https://docs.aws.amazon.com/lambda/latest/dg/with-dynamodb-create-function.html#with-dbb-invoke-manually)\. 
 
-If you are using the versioning feature, you can invoke the specific function version by providing function version or alias name that is pointing to the function version using the `Qualifier` parameter in the request\. If you don't provide the `Qualifier` parameter, the `$LATEST` version of the Lambda function is invoked\. Invocations occur at least once in response to an event and functions must be idempotent to handle this\. For information about the versioning feature, see [AWS Lambda Function Versioning and Aliases](https://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases.html)\. 
+If you are using the versioning feature, you can invoke the specific function version by providing function version or alias name that is pointing to the function version using the `Qualifier` parameter in the request\. If you don't provide the `Qualifier` parameter, the `$LATEST` version of the Lambda function is invoked\.
+
+ If you use the `RequestResponse` \(synchronous\) invocation option, the function will be invoked only once\. If you use the `Event` \(asynchronous\) invocation option, the function will be invoked at least once in response to an event and the function must be idempotent to handle this\.
+
+ For information about the versioning feature, see [AWS Lambda Function Versioning and Aliases](https://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases.html)\. 
 
 This operation requires permission for the `lambda:InvokeFunction` action\.
 
diff --git a/doc_source/API_PublishVersion.md b/doc_source/API_PublishVersion.md
@@ -164,7 +164,7 @@ Pattern: `arn:aws:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\-_/]+`
  ** [Runtime](#API_PublishVersion_ResponseSyntax) **   <a name="SSS-PublishVersion-response-Runtime"></a>
 The runtime environment for the Lambda function\.  
 Type: String  
-Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x` 
+Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | nodejs8.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x` 
 
  ** [Timeout](#API_PublishVersion_ResponseSyntax) **   <a name="SSS-PublishVersion-response-Timeout"></a>
 The function execution time at which Lambda should terminate the function\. Because the execution time has cost implications, we recommend you set this value based on your expected execution time\. The default is 3 seconds\.  
diff --git a/doc_source/API_UpdateEventSourceMapping.md b/doc_source/API_UpdateEventSourceMapping.md
@@ -33,7 +33,7 @@ The event source mapping identifier\.
 The request accepts the following data in JSON format\.
 
  ** [BatchSize](#API_UpdateEventSourceMapping_RequestSyntax) **   <a name="SSS-UpdateEventSourceMapping-request-BatchSize"></a>
-The maximum number of stream records that can be sent to your Lambda function for a single invocation\.  
+The maximum number of stream records that can be sent to your Lambda function for a single invocation\. If you are using an SQS queue as an event source, the maximum value is 10\.  
 Type: Integer  
 Valid Range: Minimum value of 1\. Maximum value of 10000\.  
 Required: No
diff --git a/doc_source/API_UpdateFunctionCode.md b/doc_source/API_UpdateFunctionCode.md
@@ -196,7 +196,7 @@ Pattern: `arn:aws:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\-_/]+`
  ** [Runtime](#API_UpdateFunctionCode_ResponseSyntax) **   <a name="SSS-UpdateFunctionCode-response-Runtime"></a>
 The runtime environment for the Lambda function\.  
 Type: String  
-Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x` 
+Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | nodejs8.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x` 
 
  ** [Timeout](#API_UpdateFunctionCode_ResponseSyntax) **   <a name="SSS-UpdateFunctionCode-response-Timeout"></a>
 The function execution time at which Lambda should terminate the function\. Because the execution time has cost implications, we recommend you set this value based on your expected execution time\. The default is 3 seconds\.  
diff --git a/doc_source/API_UpdateFunctionConfiguration.md b/doc_source/API_UpdateFunctionConfiguration.md
@@ -104,7 +104,7 @@ The runtime environment for the Lambda function\.
 To use the Python runtime v3\.6, set the value to "python3\.6"\. To use the Python runtime v2\.7, set the value to "python2\.7"\. To use the Node\.js runtime v8\.10, set the value to "nodejs8 \.10"\. To use the Node\.js runtime v6\.10, set the value to "nodejs6\.10"\. To use the \.NET Core runtime v1\.0, set the value to "dotnetcore1\.0"\. To use the \.NET Core runtime v2\.0, set the value to "dotnetcore2\.0"\.  
 Node v0\.10\.42 and node v4\.3 are currently marked as deprecated\. You must migrate existing functions to the newer Node\.js runtime versions available on AWS Lambda \(nodejs6\.10 or nodejs8\.10\) as soon as possible\. Failure to do so will result in an invalid parameter error being returned\. Note that you will have to follow this procedure for each region that contains functions written in the Node v0\.10\.42 runtime\.
 Type: String  
-Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x`   
+Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | nodejs8.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x`   
 Required: No
 
  ** [Timeout](#API_UpdateFunctionConfiguration_RequestSyntax) **   <a name="SSS-UpdateFunctionConfiguration-request-Timeout"></a>
@@ -243,7 +243,7 @@ Pattern: `arn:aws:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\-_/]+`
  ** [Runtime](#API_UpdateFunctionConfiguration_ResponseSyntax) **   <a name="SSS-UpdateFunctionConfiguration-response-Runtime"></a>
 The runtime environment for the Lambda function\.  
 Type: String  
-Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x` 
+Valid Values:` nodejs | nodejs4.3 | nodejs6.10 | nodejs8.10 | java8 | python2.7 | python3.6 | dotnetcore1.0 | dotnetcore2.0 | nodejs4.3-edge | go1.x` 
 
  ** [Timeout](#API_UpdateFunctionConfiguration_ResponseSyntax) **   <a name="SSS-UpdateFunctionConfiguration-response-Timeout"></a>
 The function execution time at which Lambda should terminate the function\. Because the execution time has cost implications, we recommend you set this value based on your expected execution time\. The default is 3 seconds\.  
diff --git a/doc_source/create-deployment-pkg-zip-java.md b/doc_source/create-deployment-pkg-zip-java.md
@@ -118,7 +118,7 @@ task buildZip(type: Zip) {
     from compileJava
     from processResources              
     into('lib') {
-        from configurations.runtime
+        from configurations.compile.Classpath
     }           
 }
 
diff --git a/doc_source/history.md b/doc_source/history.md
@@ -1,16 +1,22 @@
 # Document History<a name="history"></a>
 
-The following table describes the important changes to the *AWS Lambda Developer Guide*\. 
-
-**Relevant Dates to this History:**
+The following table describes the important changes to the *AWS Lambda Developer Guide* after May 2018\. For notification about updates to this documentation, you can subscribe to an RSS feed\.
 + **Current product version**: 2015\-03\-31
-+ **Last documentation update**: June 28, 2018
++ **Last documentation update**: July 5, 2018
+
+| Change | Description | Date | 
+| --- |--- |--- |
+| Updates now available over RSS | You can now subscribe to an RSS feed to receive notifications to the *AWS Lambda Developer Guide*\. | July 5, 2018 | 
+| Support for Amazon SQS as event source | AWS Lambda now supports Amazon Simple Queue Service \(Amazon SQS\) as an event source\. For more information, see [Invoking Lambda Functions](http://docs.aws.amazon.com/lambda/latest/dg/invoking-lambda-functions.html)\. | June 28, 2018 | 
+| China \(Ningxia\) Region | AWS Lambda is now available in the China \(Ningxia\) Region\. For more information about Lambda regions and endpoints, see [Regions and Endpoints](http://docs.aws.amazon.com/general/latest/gr/rande.html#lambda_region) in the *AWS General Reference*\. | June 28, 2018 | 
+
+## Earlier Updates<a name="history-earlier-updates"></a>
+
+The following table describes the important changes in each release of the *AWS Lambda Developer Guide* before June 2018\.
 
 
 | Change | Description | Date | 
 | --- | --- | --- | 
-| Support for Amazon SQS as event source |  AWS Lambda now supports Amazon Simple Queue Service as an event source\. For more information, see [Invoking Lambda Functions](invoking-lambda-functions.md)\.  | June 28, 2018 | 
-| China \(Ningxia\) Region  |  AWS Lambda is now available in the China \(Ningxia\) Region\. For more information about Lambda regions and endpoints, see [Regions and Endpoints](http://docs.aws.amazon.com/general/latest/gr/rande.html#lambda_region) in the *AWS General Reference*\.  | June 28, 2018 | 
 | Runtime support for Node\.js runtime 8\.10 |  AWS Lambda now supports Node\.js runtime version 8\.10\. For more information, see [Programming Model\(Node\.js\)](programming-model.md)\.  | April 2, 2018 | 
 | Function and alias revision IDs |  AWS Lambda now supports revision IDs on your function versions and aliases\. You can use these IDs to track and apply conditional updates when you are updating your function version or alias resources\.  | January 25, 2018 | 
 | Runtime support for Go and \.NET 2\.0  |  AWS Lambda has added runtime support for Go and \.NET 2\.0\. For more information, see [Programming Model for Authoring Lambda Functions in Go](go-programming-model.md) and [Programming Model for Authoring Lambda Functions in C\#](dotnet-programming-model.md)\.  | January 15, 2018 | 
diff --git a/doc_source/monitoring-functions.md b/doc_source/monitoring-functions.md
@@ -13,7 +13,7 @@ If your Lambda function code is executing, but you don't see any log data being
 
 ## AWS Lambda Troubleshooting Scenarios<a name="monitoring-functions-troubleshooting"></a>
 
- This sections describes examples of how to monitor and troubleshoot your Lambda functions using the logging and monitoring capabilities of CloudWatch\. 
+ This section describes examples of how to monitor and troubleshoot your Lambda functions using the logging and monitoring capabilities of CloudWatch\. 
 
 ### Troubleshooting Scenario 1: Lambda Function Not Working as Expected<a name="monitoring-functions-troubleshooting-one"></a>
 
diff --git a/doc_source/retries-on-errors.md b/doc_source/retries-on-errors.md
@@ -23,9 +23,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 stream until the failed batch of records either expires or is processed successfully\. This ensures that AWS Lambda processes the stream events in order\.
+  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 successfuly:** In this case, the message is removed from the queue\.
+  + **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\. 
 
 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\. 
diff --git a/doc_source/scaling.md b/doc_source/scaling.md
diff --git a/doc_source/troubleshooting.md b/doc_source/troubleshooting.md
diff --git a/doc_source/tutorial-scheduled-events-schedule-expressions.md b/doc_source/tutorial-scheduled-events-schedule-expressions.md
diff --git a/doc_source/vpc-rds-create-rds-mysql.md b/doc_source/vpc-rds-create-rds-mysql.md
diff --git a/doc_source/with-sqs-create-execution-role.md b/doc_source/with-sqs-create-execution-role.md

Original file line number	Diff line number	Diff line change
`@@ -118,7 +118,7 @@ task buildZip(type: Zip) {`
`118`	`118`	`from compileJava`
`119`	`119`	`from processResources`
`120`	`120`	`into('lib') {`
`121`		`- from configurations.runtime`
	`121`	`+ from configurations.compile.Classpath`
`122`	`122`	`}`
`123`	`123`	`}`
`124`	`124`