Data center automation is expected to rapidly change the data center industry. Look at any data center industry publication, website, or event and there will be plenty of content predicting what data center automation is going to look like. Data center professionals are curious on how automation is going to change their jobs and data center management. The truth is that we already know.

Amazon Elastic Kubernetes Service (EKS) is a managed container service designed to deploy and scale cloud-based or on-premise Kubernetes applications. AWS released EKS Blueprints to provide customers with a framework for creating internal development platforms on EKS.

When your service is undergoing performance issues, it is essential to address them in a timely and frictionless manner. With access to more telemetry and insights, the APM Service Page provides a comprehensive overview of your service and helps you quickly drill down under the hood to diagnose and investigate issues.

Another post inspired by our weekly internal enablement office hours [should we open this up to the public?] and a few conversations at DevOps Days Atlanta, talking about the experience with Kubernetes can reverberate some sighs. Though in our weekly enablement office hours, the blunt question was asked “well why is Kubernetes so difficult?”. Industry thought leaders would state that Kubernetes is a platform to build other platforms.

So you’ve just been tasked with creating a Terraform Provider (or maybe upgrading an existing one). As you do your research to prepare for the project, you slowly begin to realize, “well this looks like I’ll just be developing a Terraform specific wrapper for a client of my API.” It’s not particularly difficult, but it seems tedious. Is there a better way to build this? Maybe something that can be modular and automated? A way that’s actually stimulating to implement?

Before continuous integration was invented, developers had to work on code separately before merging it into the end product. This technique had a high chance of error. If something was left out, it took time to determine the problem. Furthermore, communication between team members became difficult as the project grew. The larger the project, the more developers, engineers, and project owners were supposed to be faithful to each other’s schedules.

Containers are great for developers, but containers are also an excellent way to create reproducible, secure, and portable applications. Applications can be deployed reliably and migrated to multiple computing environments quickly using containers. It could be the developer's laptop to the testing environment or staging to the production environment. To use Dockers, Kubernetes, etc., it has been necessary to build containers.