AWS re:Invent 2019 is over. It was huge but simple math tells me there’s at least a 95% chance* you…
This was to be my first OWASP AppSec day so I was unsure of what to expect. I'm pleased to report that it turned out to be one of the best security-related conferences I've attended.
In this post I'm going to explain why I think frontend developers need to start building their own servers, and why GraphQL is a great way to do it. In doing so, you'll see that this is about more than just technology. It's about culture as well.
This is the story of an investigation that I was recently involved in at a client. It took over a week to resolve, involved networking acronyms that seemed to increase in length each day (MTU...ICMP...PMTUD?!), and wound up with us learning all about a rather scary-sounding concept: black-hole connections.
In part 1 of this tutorial, we briefly looked at the concept of canary deployments, and installed Jenkins and Prometheus on an EKS-based Kubernetes cluster. In this part, we will setup Spinnaker using AWS S3 as its backend. After enabling canary deployment functionality we'll set up a canary pipeline to test our basic service.
In this two-part post, I'm going to explore the setup of Spinnaker on AWS EKS to do canary deployments. Our end goal will be to deploy an extremely simple golang web service that will test for increased latency post-deployment, and rollback the deployment if we exceed a certain threshold.
Trivia behind Shine's BigQuery Challenge theme "Burn Baby Burn" at GCP Sydney Summit 2019
Learn how to take the next steps into Infrastructure as Code, using python and Google's Cloud Deployment Manager.
The year was 1997. The Red Hot Chili Peppers were musing on love and the motions of amusement park rides,…