Provisioning AWS CodePipeline with CloudFormation
Provisioning AWS CodePipeline with CloudFormation
Here's a method for taking advantage of AWS CloudFormation's newly added support for AWS CodePipeline.
Join the DZone community and get the full member experience.Join For Free
Learn how to migrate and modernize stateless applications and run them in a Kubernetes cluster.
Since our entire focus at Stelligent is to help our customers apply Continuous Delivery in Amazon Web Services (AWS), we were really excited when we learned that AWS CloudFormation added support for AWS CodePipeline. I spent some time upgrading our Dromedary demo scripts to incorporate this new functionality. This article describes the process we applied in making the necessary changes along with some bonus functionality we were able to implement a more fully automated solution – thanks to Corey at AWS Support.
When the AWS CodePipeline team released its Continuous Delivery service in July 2015, they provided a custom JSON-based DSL for it which we used to automate the provisioning of CodePipeline itself but we didn’t get it into the 100% automated state for which we’d been hoping. It was close, but were “chomping at the bit” for the time when they’d begin providing CloudFormation support. Thankfully, now’s the time.
A couple of Stelligent’s engineers wrote the first version of the demo that we used at the “Infrastructure as Code” breakout session as part of AWS re:Invent 2015 so they’d already been through some of the things I learned while adding and updating our scripts.
Below, you’ll find the steps for getting this demo running on your own AWS account. All of the code is freely available and open source.
Running From CloudFormation
Download the raw file from https://raw.githubusercontent.com/stelligent/dromedary/master/pipeline/cfn/testdrive.json and upload it into CloudFormation to run the stack. Enter the required parameters. In particular: Ec2SshKeyName, GitHubToken, GitHubUser and ProdHostedZone. See the figure below and complete the rest of the steps to launch the stack. It’ll take approximately 20 minutes to launch the stack and then launch a CodePipeline pipeline instance that launched an application stack. You can see the README for other ways to run this template from CloudFormation.
Once all the required AWS resources are bootstrapped, it automatically launches a pipeline instance in CodePipeline as shown below.
Running From the Command Line
You’ll need to run the command below from a computer on which Git, Dromedary and the AWS CLI has been installed.
Step 1: Clone the Dromedary Repo
git clone -b master https://github.com/stelligent/dromedary.git
Step 2: Change the directory
Step 3: Run the bootstrap command
You’ll need to supply two commands to the bootstrap-all.sh bash script. The first argument is the subdomain and domain for the hosted zone that you’ve already configured and have access to in AWS Route 53. The second argument is your Github token. You’ll need to configure this token by going to https://github.com/settings/tokens. Since this provides access to your Github account, you’ll need to treat it as secret information. The CloudFormation template applies a NoEcho property to the parameter so that the value is not displayed in the output of the CloudFormation stack.
./bin/bootstrap-all.sh dromedary.yourdomain.com 5b298a1123546544f31f7b4ebd99a1531a6578af.
CloudFormation Template For CodePipeline Details
The steps I went through to create this CloudFormation template were fairly straightforward. First, I started with a CloudFormation template that I had implemented for another effort and removed most everything except for the core structure including the AWSTemplateFormatVersion, an empty Parameters block and an empty Resources block. The core Resources Type for CodePipeline is – as you might’ve guessed - AWS::CodePipeline::Pipeline. After this, I got the name of an existing pipeline that we’d created using the AWS CodePipeline JSON DSL from our AWS CodePipeline and ran this command:
aws codepipeline get-pipeline --name YOUR_PIPELINE_NAME > pipeline.json
This provided a JSON structure with all the stages and actions already defined in code so I was able to copy and paste within my AWS::CodePipeline::Pipeline Resources construct in the CloudFormation template. Since the CodePipeline DSL produces a slightly different case than CloudFormation, I needed to update the letter case for several properties to conform to the CloudFormation standard.
Then, I added several parameters to the template including GitHubToken and GitHubUser. Finally, I ran through several testing scenarios and updated the bootstrap shell script and the CloudFormation template that calls the bootstrap script. Be sure to run through all the steps in README as well since it’s important that you enable security for Jenkins.
Essentially, until AWS implements a service in CloudFormation, we don’t really consider it a service we can use in the manner we like so we’re really happy that CodePipeline can now be provisioned in CloudFormation. Moreover, when implementing the CodePipeline provisioning in CloudFormation, we configured it so that all of CodePipeline including the Github configuration is automated so there are no manual steps anymore (except for enabling Jenkins Global Security). If you have any questions or comments, you can contact us at email@example.com or consult the contact information at https://github.com/stelligent/dromedary.
Published at DZone with permission of Paul Duvall , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.