https://github.com/gemisis/python-package-creator
Got tired of having to spin up EC2 instances for creating python package archives for AWS Lambda, so here's a Lambda function to do so for me/you!
https://github.com/gemisis/python-package-creator
aws aws-lambda aws-s3 lambda
Last synced: 28 days ago
JSON representation
Got tired of having to spin up EC2 instances for creating python package archives for AWS Lambda, so here's a Lambda function to do so for me/you!
- Host: GitHub
- URL: https://github.com/gemisis/python-package-creator
- Owner: GEMISIS
- License: mit
- Created: 2019-02-18T06:24:43.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2019-02-18T06:47:26.000Z (over 7 years ago)
- Last Synced: 2025-01-22T14:32:14.330Z (over 1 year ago)
- Topics: aws, aws-lambda, aws-s3, lambda
- Language: Python
- Size: 1.17 MB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# python-package-creator
Got tired of having to spin up EC2 instances for creating python package archives for AWS Lambda, so here's a Lambda function to do so for me/you!
# Deploying
To deploy, first setup an S3 bucket and ensure that your Lambda function can upload public files with the ACL settings (Permissions -> Public access settings -> Disable both **'Block new public ACLs and uploading public objects (Recommended)'** and **'Remove public access granted through public ACLs (Recommended)'**). This ensures that you can make the files publically available. If you don't want them to be public, simply remove the **ExtraArgs** supplied to the **s3.upload_file** method in **lambda_function.py**.
Next, create a Lambda function and upload the zip archive of this repository to it. Add two environment variables: **bucket_name** with a value of the previously created S3 bucket's name, and **bucket_url** with a value of the URL that files can be downloaded from (can be gibberish if you disabled public downloads previously). Next, make sure your IAM Role for this Lambda function has permission to use the **PutObject** and **PutObjectAcl** Actions on your S3 bucket (you only need the **PutObject** permission if you don't allow public uploads). Finally, add an API Gateway trigger to your Lambda function and ensure that it allows POST requests to your Lambda function.
You should finally be all set to go!
# Testing
You can test your setup by doing the following from a terminal window:
```
curl -d '{"packages": ["Pillow"]}' -H "Content-Type: application/json" -X POST lambda_endpoint
```
Make sure to replace **lambda_endpoint** with your Lambda's endpoint.