Previous Serverless Version 0.5.x VS examples

Github | Website

i deployed a lambda and http api gateway using a serverless.com (sls) template as a start. I get the following error when it processes a specific request:

Have you tried serverless.com ? It lets you have infrastructure as code.

- With Lambda, you manage creating and building the container yourself, as well as updating the Lambda function code. There are tools out there such as sst or serverless.com which help streamline this.

If you'd like to use Lambda, usually you need to engineer FOR it, from day one, you don't (often) get to choose some other framework and shoehorn it into Lambda and Serverless. There's some great frameworks to help deploy code into Lambda easily and create REST endpoints for things, one such frameworks is serverless.com that helps easily deploy to it, but it lacks a framework for doing REST that also supports local emulation (as easily). For that, I recommend a framework by AWS called Chalice. This is an amazing REST framework that runs a proxy that works locally and deploys exactly the same on Lambda, it is Python however.

I use serverless.com for AWS stuff.

After knocking out a README with a set of goals and a list of TODOs to check off as I made progress, I spent about 10 hours over a weekend trying to get something to work. I used serverless for making Lambda easier, Github Actions for the deploy pipeline and store my credentials; and sadly I rolled my own access_token refresh logic because I couldn't find a helper that just did that for me! wtf!?

Does everyone who uses Workers just use wrangler cli and the cloudflare console UI for everything or is anyone using other tools like serverless framework (https://serverless.com) instead? Looks like they added some support for cloudflare but haven't tried it yet.

To create a new Serverless service you can run the sls create command and pass a template as a parameter. You can see a list of template examples in the official sls repository. As I write this post, there isn’t a Django template available in this list. Therefore, we are going to create a serverless.yml file in the root directory of our project and manually write the code we need in it.

Here's an example that deploys a node lambda along with an api gateway with very minimal configuration (check out the serverless.yml).

serverless --template-url=https://github.com/serverless/examples/tree/v3/aws-node-scheduled-cron

If you are using Serverless Framework, it becomes slightly less obvious because these are logs being created for your function automatically. They are not defined in your Serverless.yml file. Let's run through an example using a simple HTTP serverless function source code: https://github.com/serverless/examples/tree/v3/aws-node-http-api.

Check this out

Here we’re still using the same Todo list example the folks at the Serverless Framework created as our codebase. But with some variations so that it more cleanly supports automated testing and the CICD toolchain used — AWS CodePipeline.

The lambda function was simple, convert this function into a Python function, then connect to a redshift database and do a table dump. Just enough to get a base going and eventually add more business logic to make it more complex. I completed the function exactly as requested and it ran successfully. Me "not being able to code out of a wet paper bag" was not the problem. I was literally 1 day late from Friday with the feature request and got cut on Tuesday.

Let’s consider a small application that uses two runtimes and provides two functions. This example will use Python and Node targeting AWS, but the concepts will be broadly applicable in other circumstances. The full the project files can be found here

I can’t wait to see what the serverless community builds with Ruby! When you make your first (or fifth) Ruby app, please do submit it to our Examples Repo and share it with the community.

You can find the full example project that we’ve been using in this GitHub repo. The easiest way to experiment with the project is to clone the repo and deploy it from your machine using npm run deploy.