updates. Two new function configuration files

Author: devlinbd2

doc_source/access-control-identity-based.md

@@ -20,6 +20,11 @@ AWS managed policies grant permission to API actions without restricting the Lam
 
 ## Function development<a name="permissions-user-function"></a>
 
+Use identity\-based policies to allow users to perform operations on Lambda functions\. 
+
+**Note**  
+For a function defined as a container image, the user permission to access the image MUST be configured in the Amazon Elastic Container Registry For an example, see [Amazon ECR permissions\.](configuration-images.md#configuration-images-permissions)
+
 The following shows an example of a permissions policy with limited scope\. It allows a user to create and manage Lambda functions named with a designated prefix \(`intern-`\), and configured with a designated execution role\.
 
 **Example Function development policy**  

doc_source/configuration-console.md

@@ -18,7 +18,7 @@ Environment variables are not evaluated prior to the function invocation\. Any v
 
 ## Configuring environment variables<a name="configuration-envvars-config"></a>
 
-You define environment variables on the unpublished version of your function\. When you publish a version, the environment variables are locked for that version along with other [version\-specific configuration](configuration-console.md)\. 
+You define environment variables on the unpublished version of your function\. When you publish a version, the environment variables are locked for that version along with other [version\-specific configuration](configuration-function-common.md)\. 
 
 You create an environment variable on your function by defining a key and a value\. Your function uses the name of the key to retrieve the value of environment variable\.
 

doc_source/configuration-envvars.md

@@ -0,0 +1,161 @@
+# Configuring Lambda function options<a name="configuration-function-common"></a>
+
+After you create a function, you can configure additional capabilities for the function, such as triggers, network acccess, and file system access\. You can also adjust resources associated with the function, such as memory and concurrency\. These configurations apply to functions defined as \.zip file archives and to functions defined as container images\.
+
+You can also create and edit test events to test your function using the console\.
+
+For function configuration best practices, see [Function configuration](best-practices.md#function-configuration)\.
+
+**Topics**
++ [Function versions](#configuration-function-latest)
++ [Using the function overview](#configuration-functions-designer)
++ [Configuring functions \(console\)](#configuration-common-summary)
++ [Configuring functions \(API\)](#configuration-function-api)
++ [Configuring function memory \(console\)](#configuration-memory-console)
++ [Accepting function memory recommendations \(console\)](#configuration-memory-optimization-accept)
++ [Configuring triggers \(console\)](#configuration-common-triggers)
++ [Testing functions \(console\)](#configuration-common-test)
+
+## Function versions<a name="configuration-function-latest"></a>
+
+A function has an unpublished version, and can have published versions and aliases\. By default, the console displays configuration information for the unpublished version of the function\. You change the unpublished version when you update your function's code and configuration\. 
+
+A published version is a snapshot of your function code and configuration that can't be changed \(except for a few configuration items relevant to a function version, such as provisioned concurrency\)\. 
+
+## Using the function overview<a name="configuration-functions-designer"></a>
+
+The **Function overview** shows a visualization of your function and its upstream and downstream resources\. You can use it to jump to trigger and destination configuration\. You can use it to jump to layer configuration for functions defined as \.zip file archives\.
+
+![\[The Lambda function overview, with no configured triggers or destinations.\]](http://docs.aws.amazon.com/lambda/latest/dg/images/console-designer.png)
+
+## Configuring functions \(console\)<a name="configuration-common-summary"></a>
+
+For most function configurations, you can change the settings only for the unpublished version of a function\. In the console, the function **configuration** tab provides the following sections:
++ **General configuration** – Configure [memory](#configuration-memory-console) or opt in to the [AWS Compute Optimizer](#configuration-memory-optimization-accept)\. You can also configure function timeout and the execution role\.
++ **Triggers** – Configure [triggers](#configuration-common-triggers)\.
++ **Permissions** – Configure the execution role and other [permissions](lambda-permissions.md)\.
++ **Destinations** – Configure [destinations](invocation-async.md#invocation-async-destinations) for asynchronous invocations \.
++ **Environment variables** – Key\-value pairs that Lambda sets in the execution environment\. To extend your function's configuration outside of code, [use environment variables](configuration-envvars.md)\. 
++ **Tags** – Key\-value pairs that Lambda attaches to your function resource\. [Use tags](configuration-tags.md) to organize Lambda functions into groups for cost reporting and filtering in the Lambda console\.
+
+  Tags apply to the entire function, including all versions and aliases\.
++ **Virtual private cloud \(VPC\)** – If your function needs network access to resources that are not available over the internet, [configure it to connect to a virtual private cloud \(VPC\)](configuration-vpc.md)\.
++ **Monitoring and operations tools** – configure CloudWatch and other monitoring tools\.
++ **Concurrency** – [Reserve concurrency for a function](configuration-concurrency.md) to set the maximum number of simultaneous executions for a function\. Provision concurrency to ensure that a function can scale without fluctuations in latency\. 
+
+  Reserved concurrency applies to the entire function, including all versions and aliases\.
++ **Asynchronous invocation** – [Configure error handling behavior](invocation-async.md) to reduce the number of retries that Lambda attempts, or the amount of time that unprocessed events stay queued before Lambda discards them\. [Configure a dead\-letter queue](invocation-async.md#dlq) to retain discarded events\.
+
+  You can configure on a function, version, or alias\.
++ **Code signing** – If your function needs network access to resources that are not available over the internet, [configure it to connect to a virtual private cloud \(VPC\)](configuration-vpc.md)\.
++ **Database proxies** – [Create a database proxy](configuration-database.md) for functions that use an Amazon RDS DB instance or cluster\.
++ **File systems** – Connect your function to a [file system](configuration-filesystem.md)\.
+
+The console provides separate tabs to configure aliases and versions: 
++ **Aliases** – An alias is a named resource that maps to a function version\. You can change an alias to map to a different function version\.
++ **Versions** – Lambda assigns a new version number each time you publish your function\. For more information about managing versions, see [Lambda function versions](configuration-versions.md)\.
+
+You can configure the following items for a published function version:
++ Triggers
++ Destinations
++ Provisioned concurrency
++ Asynchronous invocation
++ Database proxies
+
+## Configuring functions \(API\)<a name="configuration-function-api"></a>
+
+To configure functions with the Lambda API, use the following actions:
++ [UpdateFunctionCode](API_UpdateFunctionCode.md) – Update the function's code\.
++ [UpdateFunctionConfiguration](API_UpdateFunctionConfiguration.md) – Update version\-specific settings\.
++ [TagResource](API_TagResource.md) – Tag a function\.
++ [AddPermission](API_AddPermission.md) – Modify the [resource\-based policy](access-control-resource-based.md) of a function, version, or alias\.
++ [PutFunctionConcurrency](API_PutFunctionConcurrency.md) – Configure a function's reserved concurrency\.
++ [PublishVersion](API_PublishVersion.md) – Create an immutable version with the current code and configuration\.
++ [CreateAlias](API_CreateAlias.md) – Create aliases for function versions\.
++ [PutFunctionEventInvokeConfig](https://docs.aws.amazon.com/lambda/latest/dg/API_PutFunctionEventInvokeConfig.html) – Configure error handling for asynchronous invocation\.
+
+## Configuring function memory \(console\)<a name="configuration-memory-console"></a>
+
+Lambda allocates CPU power in proportion to the amount of memory configured\. *Memory* is the amount of memory available to your Lambda function at runtime\. You can increase or decrease the memory and CPU power allocated to your function using the **Memory \(MB\)** setting\. To configure the memory for your function, set a value between 128 MB and 10,240 MB in 1\-MB increments\. At 1,769 MB, a function has the equivalent of one vCPU \(one vCPU\-second of credits per second\)\.
+
+You can configure the memory of your function in the Lambda console\.
+
+**To update the memory of a function**
+
+1. Open the [Functions page](https://console.aws.amazon.com/lambda/home#/functions) on the Lambda console\.
+
+1. Choose a function\.
+
+1. On the function configuration page, on the **General configuration** pane, choose **Edit**\.
+
+1. For **Memory \(MB\)**, set a value from 128 MB to 10,240 MB\.
+
+1. Choose **Save**\.
+
+## Accepting function memory recommendations \(console\)<a name="configuration-memory-optimization-accept"></a>
+
+If you have administrator permissions in AWS Identity and Access Management \(IAM\), you can opt in to receive Lambda function memory setting recommendations from AWS Compute Optimizer\. For instructions on opting in to memory recommendations for your account or organization, see [Opting in your account](https://docs.aws.amazon.com/compute-optimizer/latest/ug/getting-started.html#account-opt-in) in the *AWS Compute Optimizer User Guide*\.
+
+When you've opted in and your [Lambda function meets Compute Optimizer requirements](https://docs.aws.amazon.com/compute-optimizer/latest/ug/requirements.html#requirements-lambda-functions), you can view and accept function memory recommendations from Compute Optimizer in the Lambda console\.
+
+**To accept a function memory recommendation**
+
+1. Open the [Functions page](https://console.aws.amazon.com/lambda/home#/functions) on the Lambda console\.
+
+1. Choose a function\.
+
+1. On the function configuration page, on the **General configuration** pane, choose **Edit**\.
+
+1. Under **Memory \(MB\)**, in the memory alert, choose **Update**\.
+
+1. Choose **Save**\.
+
+## Configuring triggers \(console\)<a name="configuration-common-triggers"></a>
+
+You can configure other AWS services to trigger your function each time a specified event occurs\.
+
+For details about how services trigger Lambda functions, see [Using AWS Lambda with other services](lambda-services.md)\.
+
+**To add a trigger to your function\.**
+
+1. Open the [Functions page](https://console.aws.amazon.com/lambda/home#/functions) on the Lambda console\.
+
+1. Choose the function to update\.
+
+1. Under **Function overview**, choose **Add trigger**\.
+
+1. From the drop\-down list of triggers, choose a trigger\. The console displays additional configuration fields required for this trigger\.
+
+1. Choose **Add**\.
+
+## Testing functions \(console\)<a name="configuration-common-test"></a>
+
+You can create test events for your function from the **Test** tab\.
+
+**To create a test event**
+
+1. Open the [Functions page](https://console.aws.amazon.com/lambda/home#/functions) on the Lambda console\.
+
+1. Choose the function to test, and choose **Test**\.
+
+1. Under **Test event**, select **New event**\.
+
+1. Select a **Template**\.
+
+1. For **Name**, enter a name for the test\. In the text entry box, enter the JSON test event\.
+
+1. Choose **Save changes**\.
+
+Saved test events are also available from the **Code** tab, under the **Test** menu\. After you create one or more test events, you can invoke your function using one of your tests as an event\.
+
+**To test the function**
+
+1. Open the [Functions page](https://console.aws.amazon.com/lambda/home#/functions) on the Lambda console\.
+
+1. Choose the function to test, and choose **Test**\.
+
+1. Under **Test event**, select **Saved events** and select the event you want to use\.
+
+1. Choose **Test**\.
+
+1. Expand the **Execution result** panel to display details about the test\.