South Jordan, UT, USA
Dec 4, 2018 | By Mark Siebert
AWS Lambda can use stream based services as invocation sources, essentially making your Lambda function a consumer of those streams. Stream sources include Kinesis Streams and DynamoDB streams. When you allow streams to invoke your Lambda function, Lambda will emit a CloudWatch metric called IteratorAge. In this post, we discuss what this metric is and how to fix it if it’s too high.
Nov 27, 2018 | By Mark Siebert
Since Amazon released Lambda in late 2014, the notion of serverless applications and function-as-a-service has steadily gained steam. Being able to focus on application code and simplifying infrastructure management is alluring, but traditional monitoring methods are no longer applicable. With less visibility, it becomes even more important to take advantage of the available monitoring methods. In this post, we discuss those monitoring methods, CloudWatch Metrics and CloudWatch Logs.
Nov 20, 2018 | By Keilan Jackson
When administering your Kubernetes cluster, you will likely run into a situation where you need to remove pods from one of your nodes. You may need to debug issues with the node itself, upgrade the node, or simply scale down your cluster. Removing pods from a node is not very difficult, however there are specific steps you should take to minimize disruption for your application.
Nov 15, 2018 | By Matthew Barlocker
I set out to find a credit mechanism or hard-coded limit in packets per second in AWS EC2. After all my findings set out in this series so far, I had one more test to perform around t2.unlimited. I wanted to see how “unlimited” it is and the difference it makes in packet throughput on capable instance types. This post is about my findings.
Nov 13, 2018 | By Matthew Barlocker
I don’t know what to say about this post… I found something weird while investigating PPS on EC2. It seems to correlate with CPU credits on t1/t2/t3 instances, but is consistently inconsistent in presentation. It only shows up when you track the stats yourself, because Cloudwatch doesn’t show the 1-second granularity needed to see these numbers.