Many developers steeped in the world of agile startups view continuous delivery (CD) pipelines as an accepted standard requirement for software development. Yet many companies, particularly large enterprises with traditional infrastructure, still struggle to make this approach a standard part of their development process. Whether you are an enterprise looking to make CD pipelines a standard project element to increase agility and speed time to market, or if you are looking to simply implement code delivery pipeline best practices, Flux7 CEO, Dr. Aater Suleman, has written a paper that illustrates how to deliver business value through DevOps-based automation that grows developer output and strategic contributions. Download it here or read on for highlights from his piece.
Building a continuous integration and continuous delivery pipeline is a goal of many enterprises as they look to increase their agility and speed time to market. More to the point, as part of a healthy DevOps environment, CI/CD pipelines deliver business value through automation that grows developer output and strategic contributions. For AWS-based DevOps environments, many enterprises look to AWS CodePipeline to help facilitate their CI/CD as it integrates easily with other AWS services -- and a broad set of ecosystem tools -- and provides a consistent set of quality checks for code.
As more organizations move to cloud computing, the ability to deploy with a blue-green deployment scenario is gaining popularity as a proven strategy to reduce downtime and risk. As this agile approach is one we are being asked about more often, today we will discuss the benefits of blue-green deployments, specifically within AWS hosted infrastructure, and how it can be even more easily facilitated now that Amazon CloudWatch events support AWS CodePipeline as a target.
At Flux7, we are passionate about sharing the power of DevOps. In that vein, we recently gave a workshop introducing developers to the power, ease of use, and governance that comes with moving to a DevOps model reinforced with well-architected tooling. The goal of the workshop was to teach developers more about AWS and Docker-based microservices architecture. And, how using Amazon services like EC2 Container Service, CodePipeline, and CodeBuild can come together to create a platform for developer teams to focus on their application. We highlighted the Anchore solution as part of our microservices architecture for security and will share in today’s blog why we deployed Anchore, how we used it to ensure DevOps security and policy compliance, and our overall experience with the tool.
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.
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 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.
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:
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.
As DevOps consultants, at Flux7 we believe that Continuous Delivery (CD) is a key tenet of successful DevOps. And as heavy users of Amazon Web Services (AWS), we have a keen interest in any tools or features that streamline CD for our clients within AWS. For this reason, we are pretty excited to dive into the Amazon Pipeline Starter Kit. Now, you may be familiar with two services that Amazon has traditionally offered to help facilitate CD: AWS CodePipeline and AWS CodeDeploy.
For several years, that’s been the challenge for both developers and businesses. And the pressure to condense the dev and test life cycle has only increased.
Code Spaces. Its story is sending shivers up and down the spines of businesses and developers alike, and for good reason. But that doesn’t mean it should stop the progress of cloud migration or significantly change your strategy. In fact, the story brightly shines a light on an issue that is avoidable, and serves as a warning of what can happen in the complex world of cloud architecture.