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.
Now I’m sure this is not the case for everyone but for me personally, I like watching video tutorials on subjects that I need help with. I spent a good amount of time searching for these tutorials and while there might be a lot more of them out there I believe these are some of the best and easiest tutorials to follow but nevertheless, I’d like to keep this list updated so if you have any suggestions please let me know.
Software engineering is a skilled task; those who obtain the experience and credentials necessary to become engineers know this, as do their employers. Engineers have an overarching goal of using these skills to construct experiences that enable end-users to complete a task successfully and they hope to provide enjoyment and comfort along the way. Anyone who has written software used by a decent number of people knows how daunting this task is.
Since Lambda added SQS as an event source, there has been a misconception that SQS is now a “push-based” service. This seems true from the perspective of your function because you no longer have to poll SQS yourself. However, SQS itself hasn’t changed – it is still very much a “poll-based” service. The difference is that the Lambda service is managing the pollers (and paying for them!) on your behalf.
If you have anything to do with the world of cloud computing or even programming for that matter, then I’m sure you’ve heard of different terms being tossed around such as “serverless computing” or “containers,” and even “monolithic architectures.” A lot of people who understand such computing methods can have a bad habit of using these terms without leaving any explanation as to what they are.
Stackery is now available on the Amazon Web Services (AWS) Marketplace! This is great news for development teams excited by the prospect of building and modernizing applications using AWS Lambda, DynamoDB, Kinesis, API Gateway, Fargate, and the rest of the growing menu of serverless capabilities. AWS teams can start their serverless journeys with prescriptive and flexible tooling that extends AWS tools and services with less friction in the purchasing process.
AWS Lambda is one of AWS’s most popular cloud services. It allows serverless applications to be built by dividing up an application into functions that can be triggered by changes in your system. Since they are critical to the health of your application, properly monitoring Lambda functions is a top priority for most teams. In this blog post, we will go over how Blue Matador monitors Lambda functions automatically and without configuration. We will cover the following topics:
