Aside from hitting all the buzzwords in the title, this is a short (?) exploration of setting up X-Ray to understand the behaviour and performance of a fully serverless integration application on AWS.
Rather than building environments by hand from a checklist, turn the process into an automated and repeatable process. This is Infrastructure as Code.
In this post we’re pick up where we left off in the Continuous Delivery article, and cover Continuous Deployment.
This is the first part of many items in our DevOps 101 blog series. We’re going to break down the what, why, and the how of modern DevOps practices. Today, we’re starting with Continuous Delivery.
Following on from Part 1 in our intro to AWS Amplify series, in Part 2 we will create the skeleton of our new Amplify application and host it in a repository.
Our new series of articles see us walk through the process of building out a web application using AWS Amplify. It will be a typical todo application written in React and Node JS and we’ll use the Amplify CLI to configure and deploy it into both a test and production environment.
Let’s look at adding Python to your cloud development toolbox to increase reliability and dependability of your development and operations practices.
A strategy to perform re-producible deployment from any computer.
An introduction to deploying an autoscaled Jenkins cluster on AWS ECS using code all the way down.
