fixes. Also, updates to Python SDK versions. Updates for .NET 2.1 phase 1 and 2 deprecation start dates.

Author: devlinbd2

doc_source/.DS_Store

@@ -51,6 +51,10 @@ If the action is successful, the service sends back an HTTP 204 response with an
 One of the parameters in the request is invalid\.  
 HTTP Status Code: 400
 
+ **ResourceConflictException**   
+The resource already exists, or another operation is in progress\.  
+HTTP Status Code: 409
+
  **ResourceNotFoundException**   
 The resource specified in the request does not exist\.  
 HTTP Status Code: 404

doc_source/API_DeleteFunctionEventInvokeConfig.md

@@ -137,6 +137,10 @@ Valid Range: Minimum value of 0\. Maximum value of 2\.
 One of the parameters in the request is invalid\.  
 HTTP Status Code: 400
 
+ **ResourceConflictException**   
+The resource already exists, or another operation is in progress\.  
+HTTP Status Code: 409
+
  **ResourceNotFoundException**   
 The resource specified in the request does not exist\.  
 HTTP Status Code: 404

doc_source/API_PutFunctionEventInvokeConfig.md

@@ -135,6 +135,10 @@ Valid Range: Minimum value of 0\. Maximum value of 2\.
 One of the parameters in the request is invalid\.  
 HTTP Status Code: 400
 
+ **ResourceConflictException**   
+The resource already exists, or another operation is in progress\.  
+HTTP Status Code: 409
+
  **ResourceNotFoundException**   
 The resource specified in the request does not exist\.  
 HTTP Status Code: 404

doc_source/API_UpdateFunctionEventInvokeConfig.md

@@ -33,10 +33,14 @@ The following shows an example of a permissions policy with limited scope\. It a
             "Effect": "Allow", 
             "Action": [
                 "lambda:GetAccountSettings",
-                "lambda:ListFunctions",
-                "lambda:ListTags",
                 "lambda:GetEventSourceMapping",
+                "lambda:GetFunction",
+                "lambda:GetFunctionConfiguration",           
+                "lambda:GetFunctionCodeSigningConfig",
+                "lambda:GetFunctionConcurrency",                
                 "lambda:ListEventSourceMappings",
+                "lambda:ListFunctions",      
+                "lambda:ListTags"
                 "iam:ListRoles"
             ],
             "Resource": "*"
@@ -96,10 +100,14 @@ The permissions in the policy are organized into statements based on the [resour
   ```
               "Action": [
                   "lambda:GetAccountSettings",
-                  "lambda:ListFunctions",
-                  "lambda:ListTags",
                   "lambda:GetEventSourceMapping",
+                  "lambda:GetFunction",
+                  "lambda:GetFunctionConfiguration",           
+                  "lambda:GetFunctionCodeSigningConfig",
+                  "lambda:GetFunctionConcurrency",                
                   "lambda:ListEventSourceMappings",
+                  "lambda:ListFunctions",      
+                  "lambda:ListTags"
                   "iam:ListRoles"
               ],
               "Resource": "*"

doc_source/access-control-identity-based.md

@@ -27,7 +27,7 @@ For Lambda functions, you can [grant an account permission](#permissions-resourc
                  "Service": "s3.amazonaws.com"
                },
                "Action": "lambda:InvokeFunction",
-               "Resource":  "arn:aws:lambda:us-east-2:123456789012:function:my-function”,
+               "Resource":  "arn:aws:lambda:us-east-2:123456789012:function:my-function",
                "Condition": {
                  "StringEquals": {
                    "AWS:SourceAccount": "123456789012"

doc_source/access-control-resource-based.md

@@ -170,9 +170,7 @@ Resources:
       CodeUri: function/.
       Description: Use a file system.
       FileSystemConfigs:
-      - 
-        Arn: !Sub
-          - "arn:aws:elasticfilesystem:eu-central-1:123456789101:access-point/fsap-015cxmplb72b405fd"
+      - Arn: "arn:aws:elasticfilesystem:eu-central-1:123456789101:access-point/fsap-015cxmplb72b405fd"
         LocalMountPath: "/mnt/efs0"
     DependsOn: "MountTarget1"
 ```

doc_source/configuration-filesystem.md

@@ -35,7 +35,7 @@ When you deploy code as a container image to a Lambda function, the image underg
 
 ## Amazon ECR permissions<a name="configuration-images-permissions"></a>
 
-For your function to access the container image in Amazon ECR, you can add `ecr:BatchGetImage` and `ecr:GetDownloadUrlForLayer` permissions to your Amazon ECR repository\. The following example shows the minumum policy:
+For your function to access the container image in Amazon ECR, you can add `ecr:BatchGetImage` and `ecr:GetDownloadUrlForLayer` permissions to your Amazon ECR repository\. The following example shows the minimum policy:
 
 ```
 {

doc_source/configuration-images.md

@@ -10,6 +10,7 @@ You can create layers using the Lambda console, the Lambda API, AWS CloudFormati
 + [Creating layer content](#configuration-layers-upload)
 + [Compiling the \.zip file archive for your layer](#configuration-layers-compile)
 + [Including library dependencies in a layer](#configuration-layers-path)
++ [Language\-specific instructions](#configuration-layers-zip-cli)
 + [Creating a layer](#configuration-layers-create)
 + [Deleting a layer version](#configuration-layers-delete)
 + [Configuring layer permissions](#configuration-layers-permissions)
@@ -19,20 +20,9 @@ You can create layers using the Lambda console, the Lambda API, AWS CloudFormati
 
 When you create a layer, you must bundle all its content into a \.zip file archive\. You upload the \.zip file archive to your layer from Amazon Simple Storage Service \(Amazon S3\) or your local machine\. Lambda extracts the layer contents into the `/opt` directory when setting up the execution environment for the function\.
 
-### Using the AWS CLI<a name="configuration-layers-zip-cli"></a>
-
-You can create and upload a \.zip file for your layer using the Lambda console or the AWS Command Line Interface \(AWS CLI\)\. For language\-specific instructions, see the following topics\.
-+  [Deploy Node\.js Lambda functions with \.zip file archives](nodejs-package.md) 
-+  [Deploy Python Lambda functions with \.zip file archives](python-package.md) 
-+  [Deploy Ruby Lambda functions with \.zip file archives](ruby-package.md) 
-+  [Deploy Java Lambda functions with \.zip or JAR file archives](java-package.md) 
-+  [Deploy Go Lambda functions with \.zip file archives](golang-package.md) 
-+  [Deploy C\# Lambda functions with \.zip file archives](csharp-package.md) 
-+  [Deploy PowerShell Lambda functions with \.zip file archives](powershell-package.md) 
-
 ## Compiling the \.zip file archive for your layer<a name="configuration-layers-compile"></a>
 
-You build your layer code into a \.zip file archive using the same procedure as you would for a function\. If your layer includes any native code libraries, you must compile and build these libraries using a Linux development machine so that the binaries are compatible with [Amazon Linux](lambda-runtimes.md)\. 
+You build your layer code into a \.zip file archive using the same procedure as you would for a function deployment package\. If your layer includes any native code libraries, you must compile and build these libraries using a Linux development machine so that the binaries are compatible with [Amazon Linux](lambda-runtimes.md)\. 
 
 One way to ensure that you package libraries correctly for Lambda is to use [AWS Cloud9](http://aws.amazon.com/cloud9/)\. For more information, see [Using Lambda layers to simplify your development process](http://aws.amazon.com/blogs/compute/using-lambda-layers-to-simplify-your-development-process/) on the AWS Compute Blog\.
 
@@ -111,6 +101,17 @@ jq.zip
 
 For more information about path settings in the Lambda execution environment, see [Defined runtime environment variables](configuration-envvars.md#configuration-envvars-runtime)\.
 
+## Language\-specific instructions<a name="configuration-layers-zip-cli"></a>
+
+ For language\-specific instructions on how to create a \.zip file archive, see the following topics\.
++  [Deploy Node\.js Lambda functions with \.zip file archives](nodejs-package.md) 
++  [Deploy Python Lambda functions with \.zip file archives](python-package.md) 
++  [Deploy Ruby Lambda functions with \.zip file archives](ruby-package.md) 
++  [Deploy Java Lambda functions with \.zip or JAR file archives](java-package.md) 
++  [Deploy Go Lambda functions with \.zip file archives](golang-package.md) 
++  [Deploy C\# Lambda functions with \.zip file archives](csharp-package.md) 
++  [Deploy PowerShell Lambda functions with \.zip file archives](powershell-package.md) 
+
 ## Creating a layer<a name="configuration-layers-create"></a>
 
 You can create new layers using the Lambda console or the Lambda API\.
@@ -234,7 +235,9 @@ Resources:
     Properties:
       LayerName: blank-nodejs-lib
       Description: Dependencies for the blank sample app.
-      ContentUri: lib/.
+      Content:
+        S3Bucket: my-bucket-region-123456789012
+        S3Key: layer.zip
       CompatibleRuntimes:
         - nodejs12.x
 ```

doc_source/configuration-layers.md

@@ -186,7 +186,7 @@ aws lambda invoke   \
           --payload '{"key1": "value1", "key2": "value2", "key3": "value3"}' output.txt
 ```
 
-The cli\-binary\-format option is required if you are using AWS CLI version 2\. You can also configure this option in your [ AWS CLI config file](https://docs.aws.amazon.com/cli/latest/userguide/cliv2-migration.html#cliv2-migration-binaryparam)
+The cli\-binary\-format option is required if you are using AWS CLI version 2\. You can also configure this option in your [ AWS CLI config file](https://docs.aws.amazon.com/cli/latest/userguide/cliv2-migration.html#cliv2-migration-binaryparam)\.
 
 You should see the AWS CLI response in your command prompt: