Since it was released in 2015, the Serverless Framework has become the community-favorite way to manage and deploy serverless applications in the cloud. Similar to Terraform and CloudFormation, it lets you express infrastructure as code, making it easy to share and version-control your entire serverless environment.

Seed is a fully managed CI/CD pipeline for Serverless Framework applications. In one of our previous posts we looked at how to build a CI/CD pipeline for Serverless apps on AWS with CircleCI. Today, we’ll look at how to do the same with Travis CI. The purpose of these posts is to dive deep into real-world CI/CD setups, something which most of the tutorials out there skip. We’ll try to illustrate how to set up something similar to Seed but using Travis CI instead.

Did you know that CloudFormation tags don’t automatically propagate to some resource types? Chief among these are CloudWatch log groups, which means you can’t include them in your cost monitoring (via cost allocation tags) among other things. The only way to tag CloudWatch log groups right now is via API calls. You can do this with the AWS SDK, or using the AWS CLI. This is hugely inconvenient!

School’s out for… Autumn? That’s right, while you were avoiding the back-to-school rush at Office Depot, cutting the crusts off PB&Js, and taking the layers out of mothballs (confession: I have never seen let alone used a single mothball), Serverless Summer School began winding down and is now over for the season. Until next year, school-themed Stackery livestreams!

Observability is a common challenge for serverless applications and we believe Lumigo is perfectly positioned to help you tackle this problem. As such, I’m pleased to announce that we have published a new Serverless framework plugin to make it even easier for you to get started.

Cost is a big reason many dev teams are transitioning to serverless. However, there are still some ways costs can creep up on you in serverless apps. The biggest culprit I’ve found in my own experience is the VPC resource. Because adding a VPC to a serverless stack is ridiculously easy in Stackery, I’ve sometimes gotten carried away. I’d deploy a stack with a VPC for testing, then quickly forget about it.