IT Modernization and DevOps News Week in Review
Fun Fact: Four years ago this past week — on June 6, 2014 to be exact — the first commit of what would become the public repository for Kubernetes was checked in. And with that, we kick off our DevOps news coverage this week with the announcement that Amazon EKS is now generally available.
Announced at re:Invent, Amazon Elastic Container Service for Kubernetes is now available for use in production form. According to data from the Cloud Native Computing Foundation, AWS is the leading environment for Kubernetes, with 57% of all companies who run Kubernetes choosing to do so on AWS. According to Amazon, Amazon EKS simplifies the process of building, securing, operating, and maintaining Kubernetes clusters, and brings the benefits of container-based computing to organizations that want to focus on building applications instead of setting up a Kubernetes cluster from scratch.
In support of Amazon’s announcement, HashiCorp announced that HashiCorp Terraform will offer day-zero support of AWS EKS. Terraform operators can now create and manage EKS clusters as a part of their AWS configurations without having to change their current workflow. According to HashiCorp, creating an EKS cluster will be incredibly easy with Terraform, requiring a single resource aws_eks_cluster in the Terraform AWS provider.
In that vein, our engineers were glad to see that the Kubernetes Bench for Security is a Go application that checks whether Kubernetes is deployed according to security best practices was added to Github. The kube-bench is a Go application checks whether Kubernetes is deployed securely by running the checks documented in the CIS Kubernetes Benchmark. Tests are configured with YAML files, making this tool easy to update as test specifications evolve.
Speaking of making sure that things are deployed correctly, Flux7 announced this week that it is now conducting Free AWS Well-Architected Reviews to Assess for Workload Health.
In other Amazon news, lower prices were unveiled for AWS Config Rules, effective immediately. AWS Config enables operators to assess, audit, and evaluate the configurations of AWS resources. The new tiered pricing model decreases costs based on the number of active Config Rules per region across AWS accounts.
Our consultants were also interested to see the AWS CloudFormation custom resource that Chuck Meyer shared that allows operators to deploy StackSets from within a CloudFormation template. Now our engineers can write AWS CloudFormation templates for StackSets as well.
Last, our DevOps team of engineers also enjoyed these two thought provoking articles on how to Build a blockchain analytic solution with AWS Lambda, Amazon Kinesis, and Amazon Athena by Jonathan Shapiro-Ward and How to create custom alerts with Amazon Macie by Jeremy Haynes on the AWS blog this week.
DevOps Adoption Series
The AWS consulting team continues its DevOps blog series on DevOps adoption, starting with a discussion of what motivates organizations to begin an IT modernization project. We last featured The Best Cloud Migration Path: Lift and Shift, Replatform or Refactor? Subscribe to our DevOps blog to make sure you get the whole series.