#94 Flask api Deployment with Lambda

[mylescorrea]

Fixes #94

What was changed?

I added a serverless.yml file in the root of the repository so I could see if the 'serverless deploy' command could work with our flask.

Why was it changed?

I am starting to work on deployment so we first need to test in AWS lambda is possible with our program.

How was it changed?

I added the serverless.yml code with the necessary inputs but I am still trying look at which packages are necessary and which are not since lambda limits the size the program could offer. This is still a work in progress as I have not been able to run it yet because I still need to check if the flask app works with AWS lambda.

Not shown in the code but I am attempting/researching using something called zappa that could potentially simplify the process of deploying to AWS lambda from Flask.

I also finished the lambda lab but it seems like I will not be doing any of what its taught me at least for this sprint so far.

[kate-holdener]

I thought the plan was to first figure out if our application back-end is suitable for lambda deployment (since lambda has restrictions on the max unzipped size of the application code). It seems like a waste of time to be building serverless.yml file without understanding if we can even deploy this application as lambda.

[Chirag2x]

@mylescorrea even I was waiting for updates on package size since lambda can only handle 250 MB. We first wanted to look if we could pack our dependencies and projects into constraints as per we discuss.

[mylescorrea]

@kate-holdener @Chirag2x My bad I thought the way to check if the application back end is suitable was to try and run serverless deploy without necessary packages. I simply checked the size right now and it says the application back end has a size of 630 MB.