Operations | Monitoring | ITSM | DevOps | Cloud

This blog is the third in a four-part series about how Puppet can help government agencies meet compliance and security requirements. Read the second post here. Government agency IT departments know that migrating applications to the cloud can improve efficiency, increase visibility, and reduce costs. They also recognize the value in keeping some operation resources on-premises.

We know that everyone’s code story may be a little different, but speedier repos are something everyone can get behind. No matter where your developer adventures take you, it is important to keep all your code, configuration, and media assets together, and never leave a file behind. That is why we have been working on a lot of performance improvements for Git LFS users and have added Bitbucket Workspace support for Bitbucket Server users!

In this episode, Jason chats with Aaron Clark, Director of Developer Advocacy at the Royal Bank of Canada. Aaron shares what it was like starting out as a developer at RBC and working in early cloud development, and then transitioning to his role as a developer advocate. Jason and Aaron talk about the value applying open source principles within organizations, or “innersource.” Their time ends with a discussion on continuing education and how to keep learning.

Data center and cloud migrations often require changing IP addresses of your servers and application end points. These changes require careful planning and precise execution in order to minimize downtime. Typically, this is executed by manually searching your DNS server’s configuration for each server that is migrating.

Migrating your DNS to a cloud-based service like Amazon’s Route53 service can be a daunting task. With dns-tools, you can test your DNS records before and after the migration to ensure that everything made it across in one piece. If you are migrating from a BIND DNS server, see our blog post here. Follow these four steps to migrate from a Windows DNS Active-Directory integrated server to Route53.