You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 2, 2020. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+54Lines changed: 54 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@ If a layer is already published to Lambda (same layer name, SHA256 digest, and s
16
16
-[Install](#install)
17
17
+[Binaries](#binaries)
18
18
+[From Source](#from-source)
19
+
-[Permissions](#permissions)
19
20
-[Example](#example)
20
21
-[License Summary](#license-summary)
21
22
@@ -52,6 +53,59 @@ $ make
52
53
$ ./bin/local/img2lambda --help
53
54
```
54
55
56
+
## Permissions
57
+
58
+
No credentials are required for dry-runs of the img2lambda tool. When publishing layers to Lambda, img2lambda will look for credentials in the following order (using the default provider chain in the AWS SDK for Go).
59
+
60
+
1. Environment variables.
61
+
1. Shared credentials file.
62
+
1. If running on Amazon ECS (with task role) or AWS CodeBuild, IAM role from the container credentials endpoint.
63
+
1. If running on an Amazon EC2 instance, IAM role for Amazon EC2.
64
+
65
+
The credentials must have the following permissions:
0 commit comments