Periodic update

Author: alivest

doc_source/access-control-identity-based.md

@@ -170,7 +170,7 @@ The permissions in the policy are organized into statements based on the [resour
 
 This policy allows a user to get started with Lambda, without putting other users' resources at risk\. It doesn't allow a user to configure a function to be triggered by or call other AWS services, which requires broader IAM permissions\. It also doesn't include permission to services that don't support limited\-scope policies, like CloudWatch and X\-Ray\. Use the read\-only policies for these services to give the user access to metrics and trace data\.
 
-When you configure triggers for your function, you need access to use the AWS service that invokes your function\. For example, to configure an Amazon S3 trigger, you need permission to use the Amazon S3 actions that manage bucket notifications\. Many of these permissions are included in the **AWSLambdaFullAccess** managed policy\. Example policies are available in this guide's [GitHub repository](https://github.com/awsdocs/aws-lambda-developer-guide/tree/main/iam-policies)\.
+When you configure triggers for your function, you need access to use the AWS service that invokes your function\. For example, to configure an Amazon S3 trigger, you need permission to use the Amazon S3 actions that manage bucket notifications\. Many of these permissions are included in the **AWSLambdaFullAccess** managed policy\. Example policies are available in this guide's [GitHub repository](https://github.com/awsdocs/aws-lambda-developer-guide/tree/master/iam-policies)\.
 
 ## Layer development and use<a name="permissions-user-layer"></a>
 

doc_source/access-control-resource-based.md

@@ -10,9 +10,9 @@ For Lambda functions, you can [grant an account permission](#permissions-resourc
 
 1. Choose a function\.
 
-1. Choose **Permissions**\.
+1. Choose **Configuration** and then choose **Permissions**\.
 
-1. The resource\-based policy shows the permissions that are applied when another account or AWS service attempts to access the function\. The following example shows a statement that allows Amazon S3 to invoke a function named `my-function` for a bucket named `my-bucket` in account `123456789012`\.  
+1. Scroll down to **Resource\-based policy** and then choose **View policy document**\. The resource\-based policy shows the permissions that are applied when another account or AWS service attempts to access the function\. The following example shows a statement that allows Amazon S3 to invoke a function named `my-function` for a bucket named `my-bucket` in account `123456789012`\.  
 **Example Resource\-based policy**  
 
    ```
@@ -22,7 +22,7 @@ For Lambda functions, you can [grant an account permission](#permissions-resourc
        "Statement": [
            {
                "Sid": "lambda-allow-s3-my-function",
-               "Effect": "Allow",  
+               "Effect": "Allow",
                "Principal": {
                  "Service": "s3.amazonaws.com"
                },
@@ -31,12 +31,12 @@ For Lambda functions, you can [grant an account permission](#permissions-resourc
                "Condition": {
                  "StringEquals": {
                    "AWS:SourceAccount": "123456789012"
-                 },  
+                 },
                  "ArnLike": {
-                   "AWS:SourceArn": "arn:aws:s3:::my-bucket"   
+                   "AWS:SourceArn": "arn:aws:s3:::my-bucket"
                  }
-               } 
-           } 
+               }
+           }
         ]
    }
    ```

doc_source/configuration-aliases.md

@@ -6,10 +6,9 @@ You can create one or more aliases for your Lambda function\. A Lambda alias is
 
 1. Open the [Functions page](https://console.aws.amazon.com/lambda/home#/functions) on the Lambda console\.
 
-1. Choose the name of a function\.
+1. Choose a function\.
 
-1. On the function configuration page, choose **Actions**, **Create alias**\.  
-![\[Image NOT FOUND\]](http://docs.aws.amazon.com/lambda/latest/dg/images/version-actions.png)
+1. Choose **Aliases** and then choose **Create alias**\.
 
 1. On the **Create alias** page, do the following:
 
@@ -23,8 +22,6 @@ You can create one or more aliases for your Lambda function\. A Lambda alias is
 
    1. Choose **Save**\.
 
-To view the aliases that are currently defined for a function, on the function configuration page, choose **Qualifiers**, and then choose the **Aliases** tab\.
-
 ## Managing aliases with the Lambda API<a name="versioning-aliases-api"></a>
 
 To create an alias using the AWS Command Line Interface \(AWS CLI\), use the [https://awscli.amazonaws.com/v2/documentation/api/latest/reference/lambda/create-alias.html](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/lambda/create-alias.html) command\.
@@ -84,14 +81,14 @@ You can point an alias to a maximum of two Lambda function versions\. The versio
 + Both versions must be published\. The alias cannot point to `$LATEST`\.
 
 **To configure routing on an alias**
+**Note**  
+Verify that the function has at least two published versions\. To create additional versions, follow the instructions in [Lambda function versions](configuration-versions.md)\.
 
 1. Open the [Functions page](https://console.aws.amazon.com/lambda/home#/functions) on the Lambda console\.
 
-1. Choose the name of a function\.
-
-1. Verify that the function has at least two published versions\. On the function configuration page, choose **Qualifiers**, and then choose the **Versions** tab to display the list of versions\. To create additional versions, follow the instructions in [Lambda function versions](configuration-versions.md)\.
+1. Choose a function\.
 
-1. Choose **Actions**, **Create alias**\.
+1. Choose **Aliases** and then choose **Create alias**\.
 
 1. On the **Create alias** page, do the following:
 
@@ -130,7 +127,7 @@ aws lambda update-alias --name routing-alias --function-name my-function  \
 To route all traffic to version 2, use the `update-alias` command to change the `function-version` property to point the alias to version 2\. The command also resets the routing configuration\.
 
 ```
-aws lambda update-alias --name routing-alias --function-name my-function  \ 
+aws lambda update-alias --name routing-alias --function-name my-function  \
 --function-version 2 --routing-config AdditionalVersionWeights={}
 ```
 

doc_source/configuration-concurrency.md

@@ -36,6 +36,8 @@ To manage reserved concurrency settings for a function, use the Lambda console\.
 
 1. Choose a function\.
 
+1. Choose **Configuration** and then choose **Concurrency**\. 
+
 1. Under **Concurrency**, choose **Edit**\. 
 
 1. Choose **Reserve concurrency**\. Enter the amount of concurrency to reserve for the function\.
@@ -70,7 +72,9 @@ To manage provisioned concurrency settings for a version or alias, use the Lambd
 
 1. Choose a function\.
 
-1. Under **Provisioned concurrency configurations**, choose **Add**\.
+1. Choose **Configuration** and then choose **Concurrency**\. 
+
+1. Under **Provisioned concurrency configurations**, choose **Add configuration**\.
 
 1. Choose an alias or version\.
 

doc_source/configuration-console.md

@@ -2,18 +2,18 @@
 
 You can use the Lambda console to configure function settings, add triggers and destinations, and update and test your code\.
 
-To manage a function, open the Lambda console [Functions page](https://console.aws.amazon.com/lambda/home#/functions) and choose a function\. Under **Aliases**, choose `Latest`\. The function designer is near the top of the page\.
+To manage a function, open the Lambda console [Functions page](https://console.aws.amazon.com/lambda/home#/functions) and choose a function\.
 
-![\[The function designer in the AWS Lambda console.\]](http://docs.aws.amazon.com/lambda/latest/dg/images/console-designer.png)
+![\[The function overview in the AWS Lambda console.\]](http://docs.aws.amazon.com/lambda/latest/dg/images/console-designer.png)
 
-The designer shows an overview of your function and its upstream and downstream resources\. 
+The function overview shows a visualization of your function and its upstream and downstream resources\. 
 
 You can use it to configure triggers, layers, and destinations\.
 + **Triggers** – Triggers are services and resources that you have configured to invoke your function\. Choose **Add trigger** to create a Lambda [event source mapping](invocation-eventsourcemapping.md) or to configure a trigger in another service that the Lambda console integrates with\. For details about these services and others, see [Using AWS Lambda with other services](lambda-services.md)\.
 + **Layers** – Choose the **Layers** node to add [layers](configuration-layers.md) to your application\. A layer is a \.zip file archive that contains libraries, a custom runtime, or other dependencies\.
 + **Destinations** – Add a destination to your function to send details about invocation results to another service\. You can send invocation records when your function is invoked [asynchronously](invocation-async.md), or by an [event source mapping](invocation-eventsourcemapping.md) that reads from a stream\.
 
-With the `Latest` function version selected, you can modify the following settings\.
+By default you are working with the `Latest` function version\. You can modify the following settings in this version:
 
 **Function settings**
 + **Code** – The code and dependencies of your function\. For scripting languages, you can edit your function code in the embedded [editor](code-editor.md)\. To add libraries, or for languages that the editor doesn't support, or to create a function deployed as a container image, upload a [deployment package](gettingstarted-package.md)\. If your deployment package is larger than 50 MB, choose **Upload a file from Amazon S3**\.

doc_source/configuration-database.md

@@ -8,6 +8,8 @@ You can use the Lambda console to create an Amazon RDS Proxy database proxy for
 
 1. Choose a function\.
 
+1. Choose **Configuration** and then choose **Database proxies**\.
+
 1. Choose **Add database proxy**\.
 
 1. Configure the following options\.
@@ -46,7 +48,7 @@ You can create a database proxy that uses the function's IAM credentials for aut
 
 The Lambda console adds the required permission \(`rds-db:connect`\) to the execution role\. You can then use the AWS SDK to generate a token that allows it to connect to the proxy\. The following example shows how to configure a database connection with the `mysql2` library in Node\.js\.
 
-**Example [dbadmin/index\-iam\.js](https://github.com/awsdocs/aws-lambda-developer-guide/blob/main/sample-apps/rds-mysql/dbadmin/index-iam.js) – AWS SDK signer**  
+**Example [dbadmin/index\-iam\.js](https://github.com/awsdocs/aws-lambda-developer-guide/blob/master/sample-apps/rds-mysql/dbadmin/index-iam.js) – AWS SDK signer**  
 
 ```
 const signer = new AWS.RDS.Signer({
@@ -82,4 +84,4 @@ Sample applications that demonstrate the use of Lambda with an Amazon RDS databa
 
   [ ![\[The processor function processes Kinesis events and stores the events in a MySQL database.\]](http://docs.aws.amazon.com/lambda/latest/dg/images/sample-listmanager.png)](https://github.com/awsdocs/aws-lambda-developer-guide/tree/main/sample-apps/list-manager)
 
-To use the sample applications, follow the instructions in the GitHub repository: [RDS MySQL](https://github.com/awsdocs/aws-lambda-developer-guide/blob/main/sample-apps/rds-mysql/README.md), [List Manager](https://github.com/awsdocs/aws-lambda-developer-guide/blob/main/sample-apps/list-manager/README.md)\.
+To use the sample applications, follow the instructions in the GitHub repository: [RDS MySQL](https://github.com/awsdocs/aws-lambda-developer-guide/blob/master/sample-apps/rds-mysql/README.md), [List Manager](https://github.com/awsdocs/aws-lambda-developer-guide/blob/master/sample-apps/list-manager/README.md)\.

doc_source/configuration-envvars.md

@@ -13,7 +13,9 @@ You set environment variables on the unpublished version of your function by spe
 
 1. Choose a function\.
 
-1. Under **Environment variables**, choose **Edit**\.
+1. Choose **Code** if it is not already selected\.
+
+1. Scroll down\. Under **Environment variables**, choose **Edit**\.
 
 1. Choose **Add environment variable**\.
 
@@ -155,7 +157,9 @@ When you provide the key, only users in your account with access to the key can
 
 1. Choose a function\.
 
-1. Under **Environment variables**, choose **Edit**\.
+1. Choose **Code** if it is not already selected\.
+
+1. Scroll down\. Under **Environment variables**, choose **Edit**\.
 
 1. Expand **Encryption configuration**\.
 
@@ -206,7 +210,9 @@ You can also encrypt environment variable values on the client side before sendi
 
 1. Choose a function\.
 
-1. Under **Environment variables**, choose **Edit**\.
+1. Choose **Code** if it is not already selected\.
+
+1. Scroll down\. Under **Environment variables**, choose **Edit**\.
 
 1. Expand **Encryption configuration**\.
 

doc_source/configuration-filesystem.md

@@ -13,6 +13,8 @@ If your function is not already connected to a VPC, see [Configuring a Lambda fu
 
 1. Choose a function\.
 
+1. Choose **Configuration** and then choose **File systems**\.
+
 1. Under **File system**, choose **Add file system**\.
 
 1. Configure the following properties:

doc_source/configuration-layers.md

@@ -5,7 +5,7 @@ You can configure your Lambda function to pull in additional code and content in
 **Note**  
 Functions defined as container images do not support layers\. When you build a container image, you can package your preferred runtimes and dependencies as a part of the image\.
 
-Layers let you keep your deployment package small, which makes development easier\. You can avoid errors that can occur when you install and package dependencies with your function code\. For Node\.js, Python, and Ruby functions, you can [develop your function code in the Lambda console](code-editor.md) as long as you keep your deployment package under 3 MB\.
+Layers let you keep your deployment package small, which makes development easier\. You can avoid errors that can occur when you install and package dependencies with your function code\. For Node\.js, Python, and Ruby functions, you can [develop your function code in the Lambda console](code-editor.md) as long as you keep your deployment package under 3 MB \(and each code file under `512 KB`\)\.
 
 **Note**  
 A function can use up to five layers at a time\. The total unzipped size of the function and all layers can't exceed the unzipped deployment package size limit of 250 MB\. For more information, see [Lambda quotas](gettingstarted-limits.md)\.
@@ -200,53 +200,76 @@ When you delete a layer version, you can no longer configure functions to use it
 
 ## Include library dependencies in a layer<a name="configuration-layers-path"></a>
 
-You can move runtime dependencies out of your Lambda function code by placing them in a layer\. Lambda runtimes include paths in the `/opt` directory to ensure that your function code has access to libraries that are included in layers\.
-
-To include libraries in a layer, place them in one of the folders that your runtime supports, or modify that path variable for your language\.
-+ **Node\.js** – `nodejs/node_modules`, `nodejs/node8/node_modules` \(`NODE_PATH`\)  
-**Example AWS X\-Ray SDK for Node\.js**  
-
-  ```
-  xray-sdk.zip
-  └ nodejs/node_modules/aws-xray-sdk
-  ```
-+ **Python** – `python`, `python/lib/python3.8/site-packages` \(site directories\)  
-**Example Pillow**  
-
-  ```
-  pillow.zip
-  │ python/PIL
-  └ python/Pillow-5.3.0.dist-info
-  ```
-+ **Ruby** – `ruby/gems/2.5.0` \(`GEM_PATH`\), `ruby/lib` \(`RUBYLIB`\)  
-**Example JSON**  
-
-  ```
-  json.zip
-  └ ruby/gems/2.5.0/
-                 | build_info
-                 | cache
-                 | doc
-                 | extensions
-                 | gems
-                 | └ json-2.1.0
-                 └ specifications
-                   └ json-2.1.0.gemspec
-  ```
-+ **Java** – `java/lib` \(classpath\)  
-**Example Jackson**  
-
-  ```
-  jackson.zip
-  └ java/lib/jackson-core-2.2.3.jar
-  ```
-+ **All** – `bin` \(`PATH`\), `lib` \(`LD_LIBRARY_PATH`\)  
-**Example JQ**  
-
-  ```
-  jq.zip
-  └ bin/jq
-  ```
+You can move runtime dependencies out of your Lambda function by placing them in a layer\. Each Lambda runtime includes the paths to specific folders in the `/opt` directory\. Define the same folder structure in your layer \.zip archive to ensure that your function code has access to the libraries in that layer\.
+
+To include libraries in a layer, place them in one of the folders that your runtime supports, or modify that path variable for your language\. The following table lists the folder paths that each runtime supports\. 
+
+
+**Layer paths for each Lambda runtime**  
+[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/lambda/latest/dg/configuration-layers.html)
+
+The following examples show how you can structure the folders for your layer\.
+
+------
+#### [ Node\.js ]
+
+**Example file structure for AWS X\-Ray SDK**  
+
+```
+xray-sdk.zip
+└ nodejs/node_modules/aws-xray-sdk
+```
+
+------
+#### [ Python ]
+
+**Example file structure for the Pillow library**  
+
+```
+pillow.zip
+│ python/PIL
+└ python/Pillow-5.3.0.dist-info
+```
+
+------
+#### [ Ruby ]
+
+**Example file structure for JSON gem**  
+
+```
+json.zip
+└ ruby/gems/2.5.0/
+               | build_info
+               | cache
+               | doc
+               | extensions
+               | gems
+               | └ json-2.1.0
+               └ specifications
+                 └ json-2.1.0.gemspec
+```
+
+------
+#### [ Java ]
+
+**Example file structure for Jackson jar file**  
+
+```
+jackson.zip
+└ java/lib/jackson-core-2.2.3.jar
+```
+
+------
+#### [ All ]
+
+**Example file structure for JQ library**  
+
+```
+jq.zip
+└ bin/jq
+```
+
+------
 
 For more information about path settings in the Lambda execution environment, see [Runtime environment variables](configuration-envvars.md#configuration-envvars-runtime)\.
 
@@ -275,7 +298,7 @@ For more examples, see [Granting layer access to other accounts](access-control-
 
 To automate the creation and mapping of layers in your application, use AWS SAM in your AWS CloudFormation templates\. The `AWS::Serverless::LayerVersion` resource type creates a layer version that you can reference from your Lambda function configuration\.
 
-**Example [blank\-nodejs/template\.yml](https://github.com/awsdocs/aws-lambda-developer-guide/blob/main/sample-apps/blank-nodejs/template.yml) – Serverless resources**  
+**Example [blank\-nodejs/template\.yml](https://github.com/awsdocs/aws-lambda-developer-guide/blob/master/sample-apps/blank-nodejs/template.yml) – Serverless resources**  
 
 ```
 AWSTemplateFormatVersion: '2010-09-09'

doc_source/configuration-tags.md

@@ -8,6 +8,8 @@ You can tag Lambda functions to organize them by owner, project or department\.
 
 1. Choose a function\.
 
+1. Choose **Configuration** and then choose **Tags**\.
+
 1. Under **Tags**, choose **Manage tags**\.
 
 1. Enter a key and value\. To add additional tags, choose **Add new tag**\.  

doc_source/configuration-versions.md

@@ -14,20 +14,14 @@ You can change the function code and settings only on the unpublished version of
 
 1. Open the [Functions page](https://console.aws.amazon.com/lambda/home#/functions) on the Lambda console\.
 
-1. Choose the name of the function that you want to publish\.
+1. Choose a function and then choose **Versions**\.
 
-1. On the function configuration page, choose **Actions**, **Publish new version**\.
+1. On the versions configuration page, choose **Publish new version**\.
 
 1. \(Optional\) Enter a version description\.
 
 1. Choose **Publish**\.
 
-After you publish the first version of a function, the Lambda console displays a dropdown list of the available versions\. The **Designer** panel displays a version qualifier at the end of the function name\.
-
-![\[Image NOT FOUND\]](http://docs.aws.amazon.com/lambda/latest/dg/images/version-1-created.png)
-
-To view the current versions of a function, on the function configuration page, choose **Qualifiers**, and then choose the **Versions** tab to see a list of versions for the function\. If you haven't published a new version of the function, the list only displays the `$LATEST` version\.
-
 ## Managing versions with the Lambda API<a name="versioning-versions-api"></a>
 
 To publish a version of a function, use the [PublishVersion](API_PublishVersion.md) API operation\.