The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Ten years ago, still young in my career building software things, I got my first taste of DevOps. We didn’t call it that back then but for the first time I had to worry about how my software would be delivered to the world.
Back in 2016, AWS extended the resource ID length from 8 characters to 17 characters. Back then, this change applied to EC2 instances, EBS snapshots, EBS volumes, and EC2 instance reservation IDs. Now they’re doing it again with the remainder of EC2 resource types.
Providing users with the best possible software is always the number one priority. But doing so in a fast-paced, ever-changing technology landscape isn’t a simple task. Learn fundamental deployment methods for continuous delivery.
Different cloud environments can prove to be more fruitful for different teams, based on size, budget, or specific needs. A deeper understanding of each cloud deployment model will allow you to make the most informed decision. Get a crash course on hybrid cloud, community cloud, private cloud, and public cloud models.
This small release introduces custom stages, stage-level configuration overrides, instant rollbacks and a few other refinements for Up the serverless deployment tool.
Over the years “DevOps” has become quite the buzzword. It’s been used to describe culture changes, automation, change management, continuous delivery… essentially, a culture where dev and ops collaborate to build a faster, more reliable release pipeline.
In our previous posts, I showed you how to copy your DB and Aurora snapshots to ensure they are preserved beyond the lifetime of your RDS instance. However, those copies were simply second copies in the same region as the original. In this post, I’ll show you how to copy your RDS snapshots to a second region for extra protection. Please note that I will restrict this post to unencrypted snapshots. Copying encrypted snapshots is more involved, so I’ll show that in a separate post.