AWS re:Invent, the biggest cloud-computing event of the year, ended on Friday and left behind a slew of exciting new features and products for building serverless applications. Let’s summarize what was announced and how those updates can be significant for you.

In the following tutorial you can learn how to implement container security as code. You probably have a CI/CD pipeline to automatically rebuild your container images. What if you could define your container security as code, push it into a Git repository to version control changes and then enforce your policy in your container orchestration tool like Docker or Kubernetes using Sysdig Secure?

Yet another Re:Invent has concluded, leaving behind a trail of announcements, new features, and vendor swag (how many T-shirts can we possibly own?). Security was a hot topic at this year’s conference; so much so that it was mentioned in-depth within the first 10 minutes of Andy Jassy’s keynote and numerous times afterwards, as well as during Werner Vogel’s keynote the following day.

We've launched a fresh now look for the Oh Dear! homepage and a lot of tweaks to the overall look & feel of the public facing pages of our site. Allow us to show those changes in more detail!

This week was very exciting at AWS re:Invent. There were many, many new services announced. One new service that was announced is called AWS Transfer for SFTP. AWS Transfer for SFTP allows you to setup a managed SFTP server which will upload and download files to Amazon S3, using the SFTP protocol. This is a great way to transfer files in to and out of Amazon S3 using standard tools.

Lots to catchup on this week after taking a break for Thanksgiving, so let’s dive in! This week we share the video from the ‘Logging is coming to Grafana’ talk, an article on how Stack Overflow tackles monitoring, a shout out from AWS re:Invent 2018, and a plugin preview for Timestream, Amazon’s new TSDB for IoT apps.

LogicMonitor’s CloudWatch Events integration enables you to minimize troubleshooting time by displaying contextual events for your monitored resources alongside performance data. Many routine events, such as deployments, resource provisioning and de-provisioning, or configuration changes, have the potential to impact resource performance. Without being able to see the event in the same context as the performance data, it can be challenging to correlate the two.

When Ruby support on AWS Lambda was announced yesterday, I was so excited about it that I had to try it right away. We've been using Lambda for a while at Honeybadger, and I have longed to be able to write our functions in Ruby. Having played with the new Ruby support for a few hours, I'm feeling confident we'll be spending less time with Node, Go, and Python. :)