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
Merge branch 'master' of github.com:nficano/python-lambda
* 'master' of github.com:nficano/python-lambda:
Allowing update_function to update runtime
markdown formatting fail
typo
Adding function to deploy using S3 as source
fix exception on invoke when no env vars found in config
Copy file name to clipboardExpand all lines: README.rst
+14-8Lines changed: 14 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -167,14 +167,20 @@ This would create environment variables in the lambda instance upon deploy. If y
167
167
168
168
Uploading to S3
169
169
===============
170
-
You may find that you do not need the toolkit to fully deploy your Lambda or that your code bundle is too large to upload via the API. You can use the `upload` command to send the bundle to an S3 bucket of your choosing.
171
-
Before doing this, you will need to set the following variables in `config.yaml`:
172
-
```
173
-
role: basic_s3_upload
174
-
bucket_name: 'example-bucket'
175
-
s3_key_prefix: 'path/to/file/'
176
-
```
177
-
Your role must have `s3:PutObject` permission on the bucket/key that you specify for the upload to work properly. Once you have that set, you can execute `lambda upload` to initiate the transfer.
170
+
You may find that you do not need the toolkit to fully deploy your Lambda or that your code bundle is too large to upload via the API. You can use the ``upload`` command to send the bundle to an S3 bucket of your choosing.
171
+
Before doing this, you will need to set the following variables in ``config.yaml``:
172
+
173
+
.. code:: yaml
174
+
175
+
role: basic_s3_upload
176
+
bucket_name: 'example-bucket'
177
+
s3_key_prefix: 'path/to/file/'
178
+
179
+
Your role must have ``s3:PutObject`` permission on the bucket/key that you specify for the upload to work properly. Once you have that set, you can execute ``lambda upload`` to initiate the transfer.
180
+
181
+
Deploying via S3
182
+
===============
183
+
You can also choose to use S3 as your source for Lambda deployments. This can be done by issuing ``lambda deploy_s3`` with the same variables/AWS permissions you'd set for executing the ``upload`` command.
0 commit comments