Delivery Pipeline as Code: AWS CloudFormation and AWS CodePipeline
The assembly line is the heart of any factory. Workers and supervisors are giving their best to ensure a steady flow of raw materials to the end products. The delivery pipeline is an important part of DevOps and the equivalent to the assembly line. A delivery pipeline allows you to define and automate the process of making changes to your systems.
Read on to learn how to combine two tools: Infrastructure as Code and delivery pipelines. You will gain superpower by making use of this pattern!
You can create your cloud infrastructure by clicking through the Management Console, the web interface offered by AWS. But automating the process of provisioning and updating your infrastructure allows you to increase reliability and decrease effort. Describing the target state of your infrastructure in code and using a tool to transform the current state of your infrastructure into the target state is called Infrastructure as Code.
Our article Understanding Infrastructure as Code explains the concept of Infrastructure as Code in more detail.
AWS is offering an Infrastructure as Code tool: AWS CloudFormation. You can define your infrastructure consisting of virtual machines, networking configuration, databases, and any other AWS service within a template. CloudFormation can use the template containing the target state to create or update your infrastructure.
Beside Infrastructure as Code every DevOps toolbox should contain delivery pipelines as well. Pushing every source code change through an automated pipeline ending with a deployment to your production system is called Continuous Delivery. A delivery pipeline defines the process of deploying changes to production. It consists at least of the following steps:
Please support our work!
We have published 327 articles, 41 podcast episodes, and 15 videos. It's all free and means a lot of work in our spare time.
Thanks to Alex DeBrie, e9e4e5f0faef, Goran Opacic, jhoadley, Thorsten Hoeger, Todd Valentine, Vince Fulco, and all anonymous supporters for your help! We also want to thank all supporters who purchased a cloudonaut t-shirt. It gives us great pleasure to send our t-shirts all over the world.
With your help, we can continue to produce independent & high-quality content focused on AWS. Please support us!Support us
- Building and Packaging
- Testing small units and the whole system
- Deploying to production
Think of a delivery pipeline as the assembly line in a DevOps world. AWS is offering a service allowing you to define and execute delivery pipelines: AWS CodePipeline.
Your delivery pipeline will become as valuable to your company as an assembly line within a factory. It contains all the knowledge needed to deploy a change to production.
Therefore creating the delivery pipeline should be reproducible and automated in the same way as creating your infrastructure. The delivery pipeline itself should be defined in code. Again, Infrastructure as Code is the tool of your choice.
The following example shows how to use Infrastructure as Code to create a deployment pipeline. The example uses CodePipeline and CloudFormation to deploy a static website on EC2.
The following snippet contains the definition of a CodePipeline consisting of three stages:
- Source: References a GitHub repository. A commit to the repository triggers the deployment pipeline automatically.
- Deploy: CodeDeploy is used to deploy a static web application on EC2.
- Test: A Lambda function sends HTTP request to the EC2 instance to validate the deployment.
Find the whole source code at andreaswittig/codepipeline-codedeploy-example.
In my opinion, making use of Infrastructure as Code to manage your deployment pipeline is an important DevOps pattern. AWS CloudFormation and AWS CodePipeline allow you to benefit from an automated, reproducible, and transparent deployment pipeline.