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
Copy file name to clipboardExpand all lines: README.rst
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -165,6 +165,16 @@ value for the environment variable at the time of deployment (instead of hard co
165
165
166
166
This would create environment variables in the lambda instance upon deploy. If your functions don't need environment variables, simply leave this section out of your config.
167
167
168
+
Uploading to S3
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.
0 commit comments