It is spring and that means it’s conference season. Two events this week that caught our attention were the ServiceNow Knowledge Conference and Red Hat Summit, both of which, like clockwork, had several DevOps news announcements worth sharing.
Over the past few months, the DevOps team here at Flux7 has noticed a growing trend among our projects. An increasing number of client assessments result in the use of Terraform by HashiCorp in support of DevOps automation and more specifically, infrastructure as code (IaC). We thought we’d devote today’s blog to why we are becoming heavier Terraform users and its benefits. And, we’ll also share the situations in which we recommend its use to clients, as well as situations where we might recommend the use of both AWS CloudFormation and Terraform.
Amazon Web Services users have been eager to find a simpler method for deploying serverless applications, built using Lambda functions, API gateways, and AWS DynamoDB. As a result, AWS released a new model called the AWS Serverless Application Model (SAM) which makes it easier for customers to deploy their serverless applications using AWS CloudFormation. With this announcement, there are now two serverless frameworks for building serverless architectures -- deploying serverless applications using AWS CloudFormation and using the AWS SAM. However, the new AWS SAM uses CloudFormation natively to deploy, which is a definite plus for AWS users.
We are excited to bring you news today that we at Flux7 have achieved our fifth AWS Service Delivery Partner status, this time as an AWS Management Tools launch partner. (Others include AWS Web Application Firewall (WAF), AWS Service Catalog, Amazon CloudFront and Amazon Aurora.) This is an important recognition as the AWS Service Delivery Program only highlights AWS Consulting Partners who have a track record of success delivering verified customer solutions with specific AWS services. Comprised of AWS CloudFormation, Amazon EC2 Systems Manager, AWS CloudTrail and AWS Config, the AWS management tools collectively enable effective and efficient cloud operations management.
At the recent AWS Summit in Chicago, Amazon introduced CloudFormation StackSets, a new feature to CloudFormation. As heavy users of AWS CloudFormation for implementing infrastructure as code in an automated, consistent way, we are dedicating today’s blog to reviewing the new CloudFormation StackSets. As proponents of DevOps automation,
AWS automation recently got a boost: the company introduced the ability to build an end-to-end release automation workflow that can deploy changes across multiple regions or different AWS accounts. And they subsequently featured an article on their blog on the steps to create a cross region CodePipeline. Today, however, we want to address the other half of this equation -- building cross account pipelines -- and thought it worthwhile to share with you here when and why we would recommend the benefits of this approach.
We are excited to announce today that we have achieved our third AWS Service Delivery Partner status, this time for AWS Service Catalog. (You can view the news release here.) This is an important recognition for the Flux7 team of DevOps consultants as the AWS Service Delivery Program only highlights AWS Consulting Partners who have a track record of success delivering verified customer solutions for specific Amazon Web Services (AWS) products.
We recently worked with a Fortune 500 manufacturer of heavy equipment that is focused on quality, productivity, and effectively connecting its customers with data-driven insights via technology. As an international, publicly traded organization, it is also careful about managing security, risk and compliance. So, when this manufacturer asked if we could set up an audit and notification system, we were happy to roll up our sleeves and begin work. (You can read here the full case study of this Fortune 100 customer.)
To support the business as best as possible, it’s important for Development to issue new features -- or greenfield solutions -- to market as quickly as possible. It’s not a stretch to say that many organizations’ ability to compete successfully depends on their speedy delivery of new products to customer. And in some cases first mover status is the difference between owning a market or bowing out of one.
AWS recently announced that Amazon ECS now supports a state for container instances that can be used to drain a container instance in preparation for maintenance or cluster scale down. AWS reports that the draining state prevents new tasks from being started on the container instance and notifies the service scheduler to move tasks that are running on the instance to other instances in the cluster. This is great news that we expect to save a lot of time and scripting when it comes to updating or removing containers from a cluster.