fixes, PowerShell runtime, chapter structure

Author: mwunderl

doc_source/access-control-identity-based.md

@@ -50,7 +50,7 @@ The AWS Lambda console provides an integrated environment for you to create and
 
 ## AWS Managed \(Predefined\) Policies for AWS Lambda<a name="access-policy-examples-aws-managed"></a>
 
-AWS addresses many common use cases by providing standalone IAM policies that are created and administered by AWS\. Managed policies grant necessary permissions for common use cases so you can avoid having to investigate what permissions are needed\. For more information, see [AWS Managed Policies](http://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*\.
+AWS addresses many common use cases by providing standalone IAM policies that are created and administered by AWS\. Managed policies grant necessary permissions for common use cases so you can avoid having to investigate what permissions are needed\. For more information, see [AWS Managed Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*\.
 
 The following AWS managed policies, which you can attach to users in your account, are specific to AWS Lambda and are grouped by use case scenario:
 + **AWSLambdaReadOnlyAccess** – Grants read\-only access to AWS Lambda resources\. Note that this policy doesn't grant permission for the `lambda:InvokeFunction` action\. If you want a user to invoke a Lambda function, you can also attach the `AWSLambdaRole` AWS managed policy\.
@@ -72,7 +72,7 @@ You can use the console to verify the effects of each policy as you attach the p
 
 We recommend that you use two browser windows: one to create the user and grant permissions, and the other to sign in to the AWS Management Console using the user's credentials and verify permissions as you grant them to the user\.
 
- For examples that show how to create an IAM role that you can use as an execution role for your Lambda function, see [Creating IAM Roles](http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create.html) in the *IAM User Guide*\.
+ For examples that show how to create an IAM role that you can use as an execution role for your Lambda function, see [Creating IAM Roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create.html) in the *IAM User Guide*\.
 
 **Topics**
 + [Step 1: Create an IAM User](#console-permissions-list-functions)
@@ -86,7 +86,7 @@ We recommend that you use two browser windows: one to create the user and grant
 
 First, you need to create an IAM user, add the user to an IAM group with administrative permissions, and then grant administrative permissions to the IAM user that you created\. You can then access AWS using a special URL and that IAM user's credentials\. 
 
-For instructions, see [Creating Your First IAM User and Administrators Group](http://docs.aws.amazon.com/IAM/latest/UserGuide/getting-started_create-admin-group.html) in the *IAM User Guide*\. 
+For instructions, see [Creating Your First IAM User and Administrators Group](https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-started_create-admin-group.html) in the *IAM User Guide*\. 
 
 ### Step 2: Allow a User to List Lambda Functions<a name="console-permissions-list-functions1"></a>
 

doc_source/access-control-overview.md

@@ -3,7 +3,7 @@
 Every AWS resource is owned by an AWS account, and permissions to create or access a resource are governed by permissions policies\. An account administrator can attach permissions policies to IAM identities \(that is, users, groups, and roles\), and some services \(such as AWS Lambda\) also support attaching permissions policies to resources\.
 
 **Note**  
-An *account administrator* \(or administrator user\) is a user with administrator privileges\. For more information, see [IAM Best Practices](http://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*\.
+An *account administrator* \(or administrator user\) is a user with administrator privileges\. For more information, see [IAM Best Practices](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*\.
 
 When granting permissions, you decide who is getting the permissions, the resources they get permissions for, and the specific actions that you want to allow on those resources\.
 
@@ -46,7 +46,7 @@ A *resource owner* is the AWS account that created the resource\. That is, the r
 A *permissions policy* describes who has access to what\. The following section explains the available options for creating permissions policies\.
 
 **Note**  
-This section discusses using IAM in the context of AWS Lambda\. It doesn't provide detailed information about the IAM service\. For complete IAM documentation, see [What Is IAM?](http://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html) in the *IAM User Guide*\. For information about IAM policy syntax and descriptions, see [AWS IAM Policy Reference](http://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies.html) in the *IAM User Guide*\.
+This section discusses using IAM in the context of AWS Lambda\. It doesn't provide detailed information about the IAM service\. For complete IAM documentation, see [What Is IAM?](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html) in the *IAM User Guide*\. For information about IAM policy syntax and descriptions, see [AWS IAM Policy Reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies.html) in the *IAM User Guide*\.
 
 Policies attached to an IAM identity are referred to as *identity\-based* policies \(IAM polices\) and policies attached to a resource are referred to as *resource\-based* policies\. AWS Lambda supports both identity\-based \(IAM policies\) and resource\-based policies\.
 
@@ -66,7 +66,7 @@ You can attach policies to IAM identities\. For example, you can do the followin
 
   1. Account B administrator can then delegate permissions to assume the role to any users in Account B\. Doing this allows users in Account B to create or access resources in Account A\. The principal in the trust policy can also be an AWS service principal if you want to grant an AWS service permissions to assume the role\.
 
-   For more information about using IAM to delegate permissions, see [Access Management](http://docs.aws.amazon.com/IAM/latest/UserGuide/access.html) in the *IAM User Guide*\. 
+   For more information about using IAM to delegate permissions, see [Access Management](https://docs.aws.amazon.com/IAM/latest/UserGuide/access.html) in the *IAM User Guide*\. 
 
 The following is an example policy that grants permissions for the `lambda:ListFunctions` action on all resources\. In the current implementation, Lambda doesn't support identifying specific resources using the resource ARNs \(also referred to as resource\-level permissions\) for some of the API actions, so you must specify a wildcard character \(\*\)\.
 
@@ -86,7 +86,7 @@ The following is an example policy that grants permissions for the `lambda:ListF
 }
 ```
 
-For more information about using identity\-based policies with Lambda, see [Using Identity\-Based Policies \(IAM Policies\) for AWS Lambda](access-control-identity-based.md)\. For more information about users, groups, roles, and permissions, see [Identities \(Users, Groups, and Roles\)](http://docs.aws.amazon.com/IAM/latest/UserGuide/id.html) in the *IAM User Guide*\. 
+For more information about using identity\-based policies with Lambda, see [Using Identity\-Based Policies \(IAM Policies\) for AWS Lambda](access-control-identity-based.md)\. For more information about users, groups, roles, and permissions, see [Identities \(Users, Groups, and Roles\)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id.html) in the *IAM User Guide*\. 
 
 ### Resource\-Based Policies \(Lambda Function Policies\)<a name="access-control-manage-access-resource-based"></a>
 
@@ -124,7 +124,7 @@ The following is an example Lambda function policy that has one statement\. The
 }
 ```
 
-For more information about using resource\-based policies with Lambda, see [Using Resource\-Based Policies for AWS Lambda \(Lambda Function Policies\)](access-control-resource-based.md)\. For additional information about using IAM roles \(identity\-based policies\) as opposed to resource\-based policies, see [How IAM Roles Differ from Resource\-based Policies](http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_compare-resource-policies.html) in the *IAM User Guide*\.
+For more information about using resource\-based policies with Lambda, see [Using Resource\-Based Policies for AWS Lambda \(Lambda Function Policies\)](access-control-resource-based.md)\. For additional information about using IAM roles \(identity\-based policies\) as opposed to resource\-based policies, see [How IAM Roles Differ from Resource\-based Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_compare-resource-policies.html) in the *IAM User Guide*\.
 
 ## Specifying Policy Elements: Actions, Effects, Resources, and Principals<a name="access-control-specify-lambda-actions"></a>
 
@@ -136,12 +136,12 @@ The following are the most basic policy elements:
 + **Effect** – You specify the effect when the user requests the specific action—this can be either allow or deny\. If you don't explicitly grant access to \(allow\) a resource, access is implicitly denied\. You can also explicitly deny access to a resource, which you might do to make sure that a user cannot access it, even if a different policy grants access\.
 + **Principal** – In identity\-based policies \(IAM policies\), the user that the policy is attached to is the implicit principal\. For resource\-based policies, you specify the user, account, service, or other entity that you want to receive permissions \(applies to resource\-based policies only\)\. 
 
-To learn more about IAM policy syntax and descriptions, see [AWS IAM Policy Reference](http://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies.html) in the *IAM User Guide*\.
+To learn more about IAM policy syntax and descriptions, see [AWS IAM Policy Reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies.html) in the *IAM User Guide*\.
 
 For a table showing all of the AWS Lambda API actions and the resources that they apply to, see [Lambda API Permissions: Actions, Resources, and Conditions Reference](lambda-api-permissions-ref.md)\. 
 
 ## Specifying Conditions in a Policy<a name="specifying-conditions"></a>
 
-When you grant permissions, you can use the IAM policy language to specify the conditions when a policy should take effect\. For example, you might want a policy to be applied only after a specific date\. For more information about specifying conditions in a policy language, see [Condition](http://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html#Condition) in the *IAM User Guide*\.
+When you grant permissions, you can use the IAM policy language to specify the conditions when a policy should take effect\. For example, you might want a policy to be applied only after a specific date\. For more information about specifying conditions in a policy language, see [Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html#Condition) in the *IAM User Guide*\.
 
-To express conditions, you use predefined condition keys\. There are no condition keys specific to Lambda\. However, there are AWS\-wide condition keys that you can use as appropriate\. For a complete list of AWS\-wide keys, see [Available Keys for Conditions](http://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html#AvailableKeys) in the *IAM User Guide*\.
+To express conditions, you use predefined condition keys\. There are no condition keys specific to Lambda\. However, there are AWS\-wide condition keys that you can use as appropriate\. For a complete list of AWS\-wide keys, see [Available Keys for Conditions](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html#AvailableKeys) in the *IAM User Guide*\.

doc_source/accessing-resources.md

@@ -1,4 +1,4 @@
-# Accessing Resources from a Lambda Function<a name="accessing-resources"></a>
+# Accessing AWS Resources from a Lambda Function<a name="accessing-resources"></a>
 
 Lambda does not enforce any restrictions on your function logic – if you can code for it, you can run it within a Lambda function\. As part of your function, you may need to call other APIs, or access other AWS services like databases\. 
 
@@ -7,7 +7,6 @@ Lambda does not enforce any restrictions on your function logic – if you can c
 To access other AWS services, you can use the AWS SDK \([Node\.js](https://aws.amazon.com/sdk-for-node-js/), [Java](https://aws.amazon.com/sdk-for-java/), [Python](https://aws.amazon.com/sdk-for-python/), [C\#\)](https://aws.amazon.com/sdk-for-net/) or [Go](https://aws.amazon.com/sdk-for-go/), AWS Lambda will automatically set the credentials required by the SDK to those of the IAM role associated with your function – you do not need to take any additional steps\. For example, here’s sample code using the Python SDK for accessing an S3 object\.:
 
 ```
-                
 import boto3
 import botocore
 
@@ -39,6 +38,6 @@ By default, your service or API must be accessible over the public internet for
 AWS Lambda runs your function code securely within a VPC by default\. However, to enable your Lambda function to access resources inside your private VPC, you must provide additional VPC\-specific configuration information that includes VPC subnet IDs and security group IDs\. AWS Lambda uses this information to set up elastic network interfaces \(ENIs\) that enable your function to connect securely to other resources within your private VPC\. 
 
 **Important**  
-AWS Lambda does not support connecting to resources within Dedicated Tenancy VPCs\. For more information, see [Dedicated VPCs](http://docs.aws.amazon.com/vpc/latest/userguide/dedicated-instance.html)\. 
+AWS Lambda does not support connecting to resources within Dedicated Tenancy VPCs\. For more information, see [Dedicated VPCs](https://docs.aws.amazon.com/vpc/latest/userguide/dedicated-instance.html)\. 
 
 To learn how to configure a Lambda function to access resources within a VPC, see [Configuring a Lambda Function to Access Resources in an Amazon VPC](vpc.md)

doc_source/admin-lambda-apps.md

@@ -3,7 +3,12 @@
 AWS Lambda integrates with many of the administration tools that AWS offers, including AWS tagging, AWS CloudTrail, and AWS IAM\. The sections below offer guidance on how to manage your Lambda\-based applications, including organizing your Lambda based applications using tags, auditing activity on your AWS using CloudTrail, and introduce you to the AWS Security Model for how to secure your Lambda\-based applications\. We also discuss an administration task unique to AWS Lambda, which is managing the concurrent execution behavior of a Lambda function\.
 
 The sections below offer guidance on how to organize and track your Lambda function invocations and introduce you to the AWS Security Model for how to secure your Lambda\-based applications:
-+ [Tagging Lambda Functions](tagging.md)
-+ [Logging AWS Lambda API Calls with AWS CloudTrail](logging-using-cloudtrail.md)
+
+**Topics**
 + [Authentication and Access Control for AWS Lambda](lambda-auth-and-access-control.md)
-+ [Managing Concurrency](concurrent-executions.md)
++ [Logging AWS Lambda API Calls with AWS CloudTrail](logging-using-cloudtrail.md)
++ [Tagging Lambda Functions](tagging.md)
++ [Managing Concurrency](concurrent-executions.md)
++ [Best Practices for Working with AWS Lambda Functions](best-practices.md)
++ [Runtime Support Policy](runtime-support-policy.md)
++ [AWS Lambda Limits](limits.md)