Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit ba29cdd

Browse filesBrowse files
devlinbd2devlinbd2
committed
Documentation updates
1 parent 3aa52ed commit ba29cdd
Copy full SHA for ba29cdd
Expand file treeCollapse file tree

27 files changed

+326
-246
lines changed

‎doc_source/access-control-identity-based.md

Copy file name to clipboardExpand all lines: doc_source/access-control-identity-based.md
+1-19Lines changed: 1 addition & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -78,15 +78,6 @@ The following shows an example of a permissions policy with limited scope\. It a
7878
],
7979
"Resource": "arn:aws:iam::*:role/intern-lambda-execution-role"
8080
},
81-
{
82-
"Sid": "ViewExecutionRolePolicies",
83-
"Effect": "Allow",
84-
"Action": [
85-
"iam:GetPolicy",
86-
"iam:GetPolicyVersion"
87-
],
88-
"Resource": "arn:aws:iam::aws:policy/*"
89-
},
9081
{
9182
"Sid": "ViewLogs",
9283
"Effect": "Allow",
@@ -150,15 +141,6 @@ The permissions in the policy are organized into statements based on the [resour
150141
],
151142
"Resource": "arn:aws:iam::*:role/intern-lambda-execution-role"
152143
```
153-
+ `ViewExecutionRolePolicies` – View the AWS managed policies that are attached to the execution role\. This lets you view the function's permissions in the console, but doesn't include permission to view policies that were created by other users in the account\.
154-
155-
```
156-
"Action": [
157-
"iam:GetPolicy",
158-
"iam:GetPolicyVersion"
159-
],
160-
"Resource": "arn:aws:iam::accountNumber:policy/*"
161-
```
162144
+ `ViewLogs` – Use CloudWatch Logs to view logs for functions that are prefixed with `intern-`\.
163145

164146
```
@@ -243,4 +225,4 @@ For more information, see [IAM roles](https://docs.aws.amazon.com/IAM/latest/Use
243225

244226
You can use condition keys for VPC settings to provide additional permission controls for your Lambda functions\. For example, you can enforce that all Lambda functions in your organization are connected to a VPC\. You can also specify the subnets and security groups that the functions are allowed to use, or are denied from using\.
245227

246-
For more information, see [Using IAM condition keys for VPC settings](configuration-vpc.md#vpc-conditions)\.
228+
For more information, see [Using IAM condition keys for VPC settings](configuration-vpc.md#vpc-conditions)\.

‎doc_source/configuration-images.md

Copy file name to clipboardExpand all lines: doc_source/configuration-images.md
+3-2Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ When you deploy code as a container image to a Lambda function, the image underg
3535

3636
## Update the user permissions<a name="configuration-images-permissions"></a>
3737

38-
Make sure that the permissions for the AWS Identity and Access Management \(IAM\) user or role that creates the function contain the AWS managed policies `GetRepositoryPolicy` and `SetRepositoryPolicy`\.
38+
Make sure that the permissions for the AWS Identity and Access Management \(IAM\) user or role that creates the function contain the AWS managed policies `GetRepositoryPolicy`, `SetRepositoryPolicy`, and `InitiateLayerUpload`\.
3939

4040
For example, use the IAM console to create a role with the following policy:
4141

@@ -48,7 +48,8 @@ For example, use the IAM console to create a role with the following policy:
4848
"Effect": "Allow",
4949
"Action": [
5050
"ecr:SetRepositoryPolicy",
51-
"ecr:GetRepositoryPolicy"
51+
"ecr:GetRepositoryPolicy",
52+
"ecr:InitiateLayerUpload"
5253
],
5354
"Resource": "arn:aws:ecr:<region>:<account>:repository/<repo name>/"
5455
}

‎doc_source/configuration-layers.md

Copy file name to clipboardExpand all lines: doc_source/configuration-layers.md
+101-66Lines changed: 101 additions & 66 deletions
Large diffs are not rendered by default.

‎doc_source/csharp-image.md

Copy file name to clipboardExpand all lines: doc_source/csharp-image.md
+6Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,12 @@ Docker Hub repository: amazon/aws\-lambda\-dotnet
2323

2424
Amazon ECR repository: gallery\.ecr\.aws/lambda/dotnet
2525

26+
## Using a \.NET base image<a name="csharp-image-instructions"></a>
27+
28+
For instructions on how to use a \.NET base image, choose the **usage** tab on [AWS Lambda base images for \.NET](https://gallery.ecr.aws/lambda/dotnet) in the *Amazon ECR repository*\.
29+
30+
The instructions are also available on [AWS Lambda base images for \.NET](https://hub.docker.com/r/amazon/aws-lambda-dotnet) in the *Docker Hub repository*\.
31+
2632
## \.NET runtime interface clients<a name="csharp-image-clients"></a>
2733

2834
Download the \.NET runtime interface client from the [AWS Lambda for \.NET Core](https://github.com/aws/aws-lambda-dotnet) repository on GitHub\.

‎doc_source/deploying-lambda-apps.md

Copy file name to clipboardExpand all lines: doc_source/deploying-lambda-apps.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@ An AWS Lambda application is a combination of Lambda functions, event sources, a
44

55
The [AWS Serverless Application Repository](https://docs.aws.amazon.com/serverlessrepo/latest/devguide/) provides a collection of Lambda applications that you can deploy in your account with a few clicks\. The repository includes both ready\-to\-use applications and samples that you can use as a starting point for your own projects\. You can also submit your own projects for inclusion\.
66

7-
[AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-whatis-concepts.html) enables you to create a template that defines your application's resources and lets you manage the application as a *stack*\. You can more safely add or modify resources in your application stack\. If any part of an update fails, AWS CloudFormation automatically rolls back to the previous configuration\. With AWS CloudFormation parameters, you can create multiple environments for your application from the same template\. [AWS SAM](gettingstarted-tools.md#gettingstarted-tools-awssam) extends AWS CloudFormation with a simplified syntax focused on Lambda application development\.
7+
[AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-whatis-concepts.html) enables you to create a template that defines your application's resources and lets you manage the application as a *stack*\. You can more safely add or modify resources in your application stack\. If any part of an update fails, AWS CloudFormation automatically rolls back to the previous configuration\. With AWS CloudFormation parameters, you can create multiple environments for your application from the same template\. [AWS SAM](lambda-settingup.md#lambda-settingup-awssam) extends AWS CloudFormation with a simplified syntax focused on Lambda application development\.
88

9-
The [AWS CLI](gettingstarted-tools.md#gettingstarted-tools-awscli) and [SAM CLI](gettingstarted-tools.md#gettingstarted-tools-samcli) are command line tools for managing Lambda application stacks\. In addition to commands for managing application stacks with the AWS CloudFormation API, the AWS CLI supports higher\-level commands that simplify tasks like uploading deployment packages and updating templates\. The AWS SAM CLI provides additional functionality, including validating templates and testing locally\.
9+
The [AWS CLI](lambda-settingup.md#lambda-settingup-awscli) and [SAM CLI](lambda-settingup.md#lambda-settingup-samcli) are command line tools for managing Lambda application stacks\. In addition to commands for managing application stacks with the AWS CloudFormation API, the AWS CLI supports higher\-level commands that simplify tasks like uploading deployment packages and updating templates\. The AWS SAM CLI provides additional functionality, including validating templates and testing locally\.
1010

1111
When creating an application, you can create its Git repository using either CodeCommit or an AWS CodeStar connection to GitHub\. CodeCommit enables you to use the IAM console to manage SSH keys and HTTP credentials for your users\. AWS CodeStar connections enables you to connect to your GitHub account\. For more information about connections, see [What are connections?](https://docs.aws.amazon.com/dtconsole/latest/userguide/welcome-connections.html) in the *Developer Tools console User Guide*\.
1212

‎doc_source/getting-started-create-function.md

Copy file name to clipboardExpand all lines: doc_source/getting-started-create-function.md
+16-17Lines changed: 16 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -24,29 +24,27 @@ In this getting started exercise, you create a Node\.js Lambda function using th
2424

2525
1. For **Function name**, enter **my\-function**\.
2626

27-
1. For **Runtime**, confirm that **Node\.js 14\.x** is selected\. (Note that AWS Lambda natively supports Java, Go, PowerShell, Node.js, C#, Python, and Ruby code, and provides a Runtime API which allows you to use any additional programming languages to author your functions.)
27+
1. For **Runtime**, confirm that **Node\.js 14\.x** is selected\. Note that Lambda provides runtimes for \.NET \(PowerShell,C\#\) Go, Java, Node\.js, Python, and Ruby\.
2828

2929
1. Choose **Create function**\.
3030

3131
Lambda creates a Node\.js function and an [execution role](lambda-intro-execution-role.md) that grants the function permission to upload logs\. The Lambda function assumes the execution role when you invoke your function, and uses the execution role to create credentials for the AWS SDK and to read data from event sources\.
3232

3333
### Use the function overview<a name="get-started-designer"></a>
3434

35-
The **Function overview** shows a visualization of your function and its upstream and downstream resources\. You can use it to jump to trigger, destination, and layer configuration\.
35+
The **Function overview** shows a visualization of your function, including any triggers, destinations, and layer that you have configured for the function\.
3636

37-
![\[A Lambda function with an Amazon S3 trigger and an Amazon EventBridge destination.\]](http://docs.aws.amazon.com/lambda/latest/dg/images/console-designer.png)
37+
![\[A Lambda function with no triggers, destinations or layers.\]](http://docs.aws.amazon.com/lambda/latest/dg/images/console-designer.png)
3838

3939
### Invoke the Lambda function<a name="get-started-invoke-manually"></a>
4040

4141
Invoke your Lambda function using the sample event data provided in the console\.
4242

4343
**To invoke a function**
4444

45-
1. In the console, open the file with the lambda function. For this Node\.js app, it's called index\.js.
46-
47-
1. Click on the orange **Test** button to create a new test event. Each user can create up to 10 test events per function\. Those test events are not available to other users\.
45+
1. After selecting your function, choose the **Test** tab\.
4846

49-
1. Enter an **Event name** and note the following sample event template:
47+
1. In the **Test event** section, choose **New event**\. In **Template**, leave the default **hello\-world** option\. Enter a **Name** for this test and note the following sample event template:
5048

5149
```
5250
{
@@ -56,15 +54,16 @@ Invoke your Lambda function using the sample event data provided in the console\
5654
}
5755
```
5856

59-
1. Choose **Create**, and then choose **Test** again to run the function\.
57+
1. Choose **Save changes**, and then choose **Test**\. Each user can create up to 10 test events per function\. Those test events are not available to other users\.
6058

6159
Lambda runs your function on your behalf\. The function handler receives and then processes the sample event\.
6260

6361
1. Upon successful completion, view the results in the console\.
64-
+ The **Execution results** tab shows the execution status as **succeeded**\. Here you will also see **Function Logs**\.
62+
+ The **Execution result** shows the execution status as **succeeded**\. To view the function execution results, expand **Details**\. Note that the **logs** link opens the **Log groups** page in the CloudWatch console\.
63+
+ The **Summary** section shows the key information reported in the **Log output** section \(the *REPORT* line in the execution log\)\.
64+
+ The **Log output** section shows the log that Lambda generates for each invocation\. The function writes these logs to CloudWatch\. The Lambda console shows these logs for your convenience\. Choose **Click here** to add logs to the CloudWatch log group and open the **Log groups** page in the CloudWatch console\.
6565

66-
1. To make changes to your lambda function, edit the `index.js` file, and choose **Deploy**\. This will store those changes in S3. Then, choose **Test** again to run the function.
67-
66+
1. Run the function \(choose **Test**\) a few more times to gather some metrics that you can view in the next step\.
6867

6968
1. Choose the **Monitor** tab\. This page shows graphs for the metrics that Lambda sends to CloudWatch\.
7069
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/lambda/latest/dg/images/metrics-functions-list.png)
@@ -232,7 +231,7 @@ In the following commands, replace `123456789012` with your AWS account ID\.
232231
233232
### Update the user permissions<a name="gettingstarted-images-permissions"></a>
234233
235-
Make sure that the permissions for the IAM user or role that creates the function contain the AWS managed policies `GetRepositoryPolicy` and `SetRepositoryPolicy`\. For information about access policies, see [ Access Management](https://docs.aws.amazon.com/IAM/latest/UserGuide/access.html) in the *IAM User Guide*
234+
Make sure that the permissions for the IAM user or role that creates the function contain the AWS managed policies `GetRepositoryPolicy`, `SetRepositoryPolicy`, and `InitiateLayerUpload`\. For information about access policies, see [ Access Management](https://docs.aws.amazon.com/IAM/latest/UserGuide/access.html) in the *IAM User Guide*
236235
237236
For example, use the IAM console to create a role with the following policy:
238237
@@ -243,7 +242,7 @@ For example, use the IAM console to create a role with the following policy:
243242
{
244243
"Sid": "VisualEditor0",
245244
"Effect": "Allow",
246-
"Action": ["ecr:SetRepositoryPolicy","ecr:GetRepositoryPolicy"],
245+
"Action": ["ecr:SetRepositoryPolicy","ecr:GetRepositoryPolicy", "ecr:InitiateLayerUpload],
247246
"Resource": "arn:aws:ecr:<region>:<account>:repository/<repo name>/"
248247
}
249248
]
@@ -280,7 +279,7 @@ Invoke your Lambda function using the sample event data provided in the console\
280279
281280
1. After selecting your function, choose the **Test** tab\.
282281
283-
1. In the **Test event** section, choose **New event**\. In **Template**, leave the default **hello\-world** option\. Enter an **Name** and note the following sample event template:
282+
1. In the **Test event** section, choose **New event**\. In **Template**, leave the default **hello\-world** option\. Enter a **Name** for this test and note the following sample event template:
284283
285284
```
286285
{
@@ -290,7 +289,7 @@ Invoke your Lambda function using the sample event data provided in the console\
290289
}
291290
```
292291
293-
1. Choose **Create event**, and then choose **Invoke**\. Each user can create up to 10 test events per function\. Those test events are not available to other users\.
292+
1. Choose **Save changes**, and then choose **Test**\. Each user can create up to 10 test events per function\. Those test events are not available to other users\.
294293
295294
Lambda runs your function on your behalf\. The function handler receives and then processes the sample event\.
296295
@@ -299,9 +298,9 @@ Invoke your Lambda function using the sample event data provided in the console\
299298
+ The **Summary** section shows the key information reported in the **Log output** section \(the *REPORT* line in the execution log\)\.
300299
+ The **Log output** section shows the log that Lambda generates for each invocation\. The function writes these logs to CloudWatch\. The Lambda console shows these logs for your convenience\. Choose **Click here** to add logs to the CloudWatch log group and open the **Log groups** page in the CloudWatch console\.
301300
302-
1. Run the function \(choose **Invoke**\) a few more times to gather some metrics that you can view in the next step\.
301+
1. Run the function \(choose **Test**\) a few more times to gather some metrics that you can view in the next step\.
303302
304-
1. Near the top of the page, choose the **Monitoring** tab\. This page shows graphs for the metrics that Lambda sends to CloudWatch\.
303+
1. Choose the **Monitor** tab\. This page shows graphs for the metrics that Lambda sends to CloudWatch\.
305304
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/lambda/latest/dg/images/metrics-functions-list.png)
306305
307306
For more information on these graphs, see [Monitoring functions in the AWS Lambda console](monitoring-functions-access-metrics.md)\.

‎doc_source/getting-started.md

Copy file name to clipboardExpand all lines: doc_source/getting-started.md
-1Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,5 +19,4 @@ You deploy your function code to Lambda using a deployment package\. Lambda supp
1919
+ [Lambda concepts](gettingstarted-concepts.md)
2020
+ [Lambda features](gettingstarted-features.md)
2121
+ [Lambda deployment packages](gettingstarted-package.md)
22-
+ [Tools for working with Lambda](gettingstarted-tools.md)
2322
+ [Lambda quotas](gettingstarted-limits.md)

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.