list manager sample app

Author: mwunderl

doc_source/applications-tutorial.md

@@ -140,7 +140,7 @@ To add a DynamoDB table to the application, define an `AWS::Serverless::SimpleTa
            ReadCapacityUnits: 1
            WriteCapacityUnits: 1
      helloFromLambdaFunction:
-       Type: AWS::Serverless::Function
+       Type: [AWS::Serverless::Function](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-function.html)
        Properties:
          CodeUri: ./
          Handler: src/handlers/hello-from-lambda.helloFromLambdaHandler
@@ -229,7 +229,7 @@ Next, update the function code to use the table\. The following code uses the Dy
    ```
    ...
      helloFromLambdaFunction:
-       Type: AWS::Serverless::Function
+       Type: [AWS::Serverless::Function](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-function.html)
        Properties:
          CodeUri: ./
          Handler: src/handlers/index.handler

doc_source/best-practices.md

@@ -1,14 +1,14 @@
-# Best Practices for Working with AWS Lambda Functions<a name="best-practices"></a>
+# Best practices for working with AWS Lambda functions<a name="best-practices"></a>
 
 The following are recommended best practices for using AWS Lambda:
 
 **Topics**
-+ [Function Code](#function-code)
-+ [Function Configuration](#function-configuration)
-+ [Alarming and Metrics](#alarming-metrics)
-+ [Stream Event Invokes](#stream-events)
++ [Function code](#function-code)
++ [Function configuration](#function-configuration)
++ [Metrics and alarms](#alarming-metrics)
++ [Working with streams](#stream-events)
 
-## Function Code<a name="function-code"></a>
+## Function code<a name="function-code"></a>
 + **Separate the Lambda handler from your core logic\.** This allows you to make a more unit\-testable function\. In Node\.js this may look like: 
 
   ```
@@ -34,7 +34,7 @@ The following are recommended best practices for using AWS Lambda:
 + **Minimize the complexity of your dependencies\.** Prefer simpler frameworks that load quickly on [execution context](runtimes-context.md) startup\. For example, prefer simpler Java dependency injection \(IoC\) frameworks like [Dagger](https://google.github.io/dagger/) or [Guice](https://github.com/google/guice), over more complex ones like [Spring Framework](https://github.com/spring-projects/spring-framework)\. 
 + **Avoid using recursive code** in your Lambda function, wherein the function automatically calls itself until some arbitrary criteria is met\. This could lead to unintended volume of function invocations and escalated costs\. If you do accidentally do so, set the function concurrent execution limit to `0` immediately to throttle all invocations to the function, while you update the code\.
 
-## Function Configuration<a name="function-configuration"></a>
+## Function configuration<a name="function-configuration"></a>
 + **Performance testing your Lambda function** is a crucial part in ensuring you pick the optimum memory size configuration\. Any increase in memory size triggers an equivalent increase in CPU available to your function\. The memory usage for your function is determined per\-invoke and can be viewed in [AWS CloudWatch Logs](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatchLogs.html)\. On each invoke a `REPORT:` entry will be made, as shown below: 
 
   ```
@@ -50,11 +50,11 @@ The following are recommended best practices for using AWS Lambda:
   + 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\.
 
-## Alarming and Metrics<a name="alarming-metrics"></a>
+## Metrics and alarms<a name="alarming-metrics"></a>
 + **Use [Working with AWS Lambda function metrics](monitoring-metrics.md) and [ CloudWatch Alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html)** instead of creating or updating a metric from within your Lambda function code\. It's a much more efficient way to track the health of your Lambda functions, allowing you to catch issues early in the development process\. For instance, you can configure an alarm based on the expected duration of your Lambda function execution time in order to address any bottlenecks or latencies attributable to your function code\.
 + **Leverage your logging library and [AWS Lambda Metrics and Dimensions](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/lam-metricscollected.html)** to catch app errors \(e\.g\. ERR, ERROR, WARNING, etc\.\) 
 
-## Stream Event Invokes<a name="stream-events"></a>
+## Working with streams<a name="stream-events"></a>
 + **Test with different batch and record sizes **so that the polling frequency of each event source is tuned to how quickly your function is able to complete its task\. [BatchSize](API_CreateEventSourceMapping.md#SSS-CreateEventSourceMapping-request-BatchSize) controls the maximum number of records that can be sent to your function with each invoke\. A larger batch size can often more efficiently absorb the invoke overhead across a larger set of records, increasing your throughput\.
 
   By default, Lambda invokes your function as soon as records are available in the stream\. If the batch it reads from the stream only has one record in it, Lambda only sends one record to the function\. To avoid invoking the function with a small number of records, you can tell the event source to buffer records for up to 5 minutes by configuring a *batch window*\. Before invoking the function, Lambda continues to read records from the stream until it has gathered a full batch, or until the batch window expires\.

doc_source/build-pipeline.md

@@ -131,7 +131,7 @@ Transform: AWS::Serverless-2016-10-31
 Description: Outputs the time
 Resources:
   TimeFunction:
-    Type: AWS::Serverless::Function
+    Type: [AWS::Serverless::Function](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-function.html)
     Properties:
       Handler: index.handler
       Runtime: nodejs10.x

doc_source/configuration-console.md

@@ -55,4 +55,4 @@ For example, to update a function's memory setting with the AWS CLI, use the `up
 $ aws lambda update-function-configuration --function-name my-function --memory-size 256
 ```
 
-For function configuration best practices, see [Function Configuration](best-practices.md#function-configuration)\.
+For function configuration best practices, see [Function configuration](best-practices.md#function-configuration)\.

doc_source/csharp-tracing.md

@@ -105,7 +105,7 @@ To enable active tracing on an `AWS::Lambda::Function` resource in an AWS CloudF
 ```
 Resources:
   function:
-    Type: AWS::Lambda::Function
+    Type: [AWS::Lambda::Function](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-lambda-function.html)
     Properties:
       TracingConfig: 
         Mode: Active
@@ -119,7 +119,7 @@ For an AWS Serverless Application Model \(AWS SAM\) `AWS::Serverless::Function`
 ```
 Resources:
   function:
-    Type: AWS::Serverless::Function
+    Type: [AWS::Serverless::Function](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-function.html)
     Properties:
       Tracing: Active
       ...

doc_source/deploying-lambda-apps.md

@@ -13,4 +13,4 @@ The [AWS CLI](gettingstarted-tools.md#gettingstarted-tools-awscli) and [SAM CLI]
 + [Creating an application with continuous delivery in the Lambda console](applications-tutorial.md)
 + [Rolling deployments for Lambda functions](lambda-rolling-deployments.md)
 + [Common Lambda application types and use cases](applications-usecases.md)
-+ [Best Practices for Working with AWS Lambda Functions](best-practices.md)
++ [Best practices for working with AWS Lambda functions](best-practices.md)

doc_source/golang-tracing.md

@@ -81,7 +81,7 @@ To enable active tracing on an `AWS::Lambda::Function` resource in an AWS CloudF
 ```
 Resources:
   function:
-    Type: AWS::Lambda::Function
+    Type: [AWS::Lambda::Function](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-lambda-function.html)
     Properties:
       TracingConfig: 
         Mode: Active
@@ -95,7 +95,7 @@ For an AWS Serverless Application Model \(AWS SAM\) `AWS::Serverless::Function`
 ```
 Resources:
   function:
-    Type: AWS::Serverless::Function
+    Type: [AWS::Serverless::Function](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-function.html)
     Properties:
       Tracing: Active
       ...

doc_source/index.md

@@ -60,7 +60,7 @@ Amazon's trademarks and trade dress may not be used in
    + [Creating an application with continuous delivery in the Lambda console](applications-tutorial.md)
    + [Rolling deployments for Lambda functions](lambda-rolling-deployments.md)
    + [Common Lambda application types and use cases](applications-usecases.md)
-   + [Best Practices for Working with AWS Lambda Functions](best-practices.md)
+   + [Best practices for working with AWS Lambda functions](best-practices.md)
 + [Using AWS Lambda with other services](lambda-services.md)
    + [Using AWS Lambda with Alexa](services-alexa.md)
    + [Using AWS Lambda with Amazon API Gateway](services-apigateway.md)
@@ -119,6 +119,7 @@ Amazon's trademarks and trade dress may not be used in
 + [Lambda sample applications](lambda-samples.md)
    + [Blank function sample application for AWS Lambda](samples-blank.md)
    + [Error processor sample application for AWS Lambda](samples-errorprocessor.md)
+   + [List manager sample application for AWS Lambda](samples-listmanager.md)
 + [Building Lambda functions with Node.js](lambda-nodejs.md)
    + [AWS Lambda function handler in Node.js](nodejs-handler.md)
    + [AWS Lambda deployment package in Node.js](nodejs-package.md)

doc_source/java-package.md

@@ -264,7 +264,7 @@ Transform: 'AWS::Serverless-2016-10-31'
 Description: An AWS Lambda application that calls the Lambda API.
 Resources:
   function:
-    Type: AWS::Serverless::Function
+    Type: [AWS::Serverless::Function](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-function.html)
     Properties:
       CodeUri: build/distributions/java-basic.zip
       Handler: example.Handler

doc_source/java-tracing.md

@@ -88,7 +88,7 @@ To enable active tracing on an `AWS::Lambda::Function` resource in an AWS CloudF
 ```
 Resources:
   function:
-    Type: AWS::Lambda::Function
+    Type: [AWS::Lambda::Function](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-lambda-function.html)
     Properties:
       TracingConfig: 
         Mode: Active
@@ -102,7 +102,7 @@ For an AWS Serverless Application Model \(AWS SAM\) `AWS::Serverless::Function`
 ```
 Resources:
   function:
-    Type: AWS::Serverless::Function
+    Type: [AWS::Serverless::Function](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-function.html)
     Properties:
       Tracing: Active
       ...
@@ -119,15 +119,15 @@ The following example shows an `AWS::Serverless::LayerVersion` resource that sto
 ```
 Resources:
   function:
-    Type: AWS::Serverless::Function
+    Type: [AWS::Serverless::Function](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-function.html)
     Properties:
       CodeUri: build/distributions/blank-java.zip
       Tracing: Active
       Layers:
         - !Ref libs
       ...
   libs:
-    Type: AWS::Serverless::LayerVersion
+    Type: [AWS::Serverless::LayerVersion](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-layerversion.html)
     Properties:
       LayerName: blank-java-lib
       Description: Dependencies for the blank-java sample app.