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.
This week we are highlighting the most talked about issues from the Flux7 blog in 2016. While new AWS services are always being announced, sometimes making it hard to keep up, we found that a lot of discussion revolved around process management and how to best use new features and tools to streamline DevOps processes like continuous integration and continuous delivery (CI/CD).
As we all know CI/CD is a key tenet of successful DevOps with automation playing a starring role. Whether you are getting features to internal customers faster or bringing new products to market before the competition, a continuous delivery pipeline helps speed time to delivery, generating greater value to the business. And when it came to delivering the greatest value to our readers on the topics of CI pipelines and deployment pipelines, these posts scored:
This month’s re:Invent in Las Vegas drew over 32,000 attendees and the show did not disappoint as AWS delivered on its precedent to unveil a number of new features and products at the show. With numerous announcements, AWS news was peppered throughout two days of lengthy keynote sessions, we’ve asked Ali Hussain, Flux7 co-founder and CTO, to weigh in on what caught his attention and where he thinks the most impact will be seen to enterprise organizations like those that Flux7 serves.
Continuous Delivery (CD) is a core facet of successful DevOps and as a result, a core Flux7 strategy for implementing DevOps-based IT modernization. At Flux7, we always view DevOps as streamlining the delivery of not just Code but also the delivery of Infrastructure (networking, firewalls, VMs), Server Configuration (software packages such as Apache or JAVA), and Security Rules (policies for AWS Config Rules or HashiCorp Vault). Among these, efficient delivery of infrastructure and configuration are both very critical for full stack agility. For our customers in AWS, our typical choice for infrastructure delivery is CloudFormation. We like AWS CloudFormation because it is native to AWS, follows a simple YAML or JSON syntax, and has deep integration with other AWS Services such as the AWS Service Catalog.
In addition to the announced CloudFormation YAML support, AWS also announced cross-stack references for CloudFormation. (For Flux7 commentary on YAML support, please see our blog post earlier this week here.) As our AWS experts work daily with CloudFormation, we were very interested in this news and couldn’t wait to roll up our sleeves and take a look for ourselves.
In our blog last week we told you that AWS CloudFormation has grown its support beyond JSON to include YAML. Prior to the announcement, our AWS consultants had been writing in YAML and used an in-house YAML CloudFormation generator to help us avoid the typical pain points associated with JSON. We promised in that article to share with you instructions on how to convert existing JSON CloudFormation templates into YAML and are delivering on that promise today.
Today AWS announced that CloudFormation will now support YAML. As big fans of YAML, we have been testing this new feature and are not disappointed in the results. Prior to this announcement, JSON specifications were used to write CloudFormation templates. However, we had been writing in YAML and using an in-house YAML CloudFormation generator which helped us avoid the typical pain points associated with JSON.
According to Innovative Retail Technologies, 52% of surveyed retailers plan to actively move applications to the cloud this year. The initially tepid response to cloud is waning as retailers learn more about its strengths for availability and innovation. Yet, one question our AWS consultants frequently field from retailers is about achieving AWS PCI Compliance in the cloud. As most readers of this blog know, the Payment Card Industry Data Security Standard, otherwise known as PCI DSS, is an information security standard requiring organizations to incorporate controls around customer data to prevent credit card fraud. There are several ways that AWS helps its retail clients build a foundation for PCI compliance and they’ve recently announced one more in the form of a Quick Start.
On March 29, 2016, Amazon released Change Sets for AWS CloudFormation, an important new update with far reaching benefits. Anyone using CloudFormation templates, anyone pursuing an infrastructure as code strategy on AWS, should pay attention.
AWS CloudFormation gives developers and systems administrators an easy way to create and manage a collection of related AWS resources, allowing them to provision and update them in an orderly and predictable fashion.