Book Image

Implementing DevOps on AWS

By : Vaselin Kantsev
Book Image

Implementing DevOps on AWS

By: Vaselin Kantsev

Overview of this book

Knowing how to adopt DevOps in your organization is becoming an increasingly important skill for developers, whether you work for a start-up, an SMB, or an enterprise. This book will help you to drastically reduce the amount of time spent on development and increase the reliability of your software deployments on AWS using popular DevOps methods of automation. To start, you will get familiar with the concept of IaC and will learn to design, deploy, and maintain AWS infrastructure. Further on, you’ll see how to design and deploy a Continuous Integration platform on AWS using either open source or AWS provided tools/services. Following on from the delivery part of the process, you will learn how to deploy a newly created, tested, and verified artefact to the AWS infrastructure without manual intervention. You will then find out what to consider in order to make the implementation of Configuration Management easier and more effective. Toward the end of the book, you will learn some tricks and tips to optimize and secure your AWS environment. By the end of the book, you will have mastered the art of implementing DevOps practices onto AWS.
Table of Contents (17 chapters)
Implementing DevOps on AWS
About the Author
About the Reviewer
Customer Feedback
Free Chapter
What is DevOps and Should You Care?
Build, Test, and Release Faster with Continuous Integration

Configuring Jenkins jobs

Prior to recreating the Continuous Integration pipeline job, we need a S3 bucket for our YUM repository. Create a bucket (unless you've kept the old one around), update the demo-app/Jenkinsfile script accordingly then commit and push Git changes upstream.

demo-app pipeline

Refer to the Setting up the pipeline steps from the previous chapter to create the Continuous Integration job. Let us call it demo-app this time around. The script path remains the same (

You should now have this:

The pipeline is going to fail as we do not have our YUM repository configured yet:

The repository contents have already been uploaded to S3 by this first job run. Now we need to update the salt/states/yum-s3/files/s3.repo file with the S3 URL and set the repository to enabled. Commit and push the Salt changes to the Git repository, then pull and apply on the Jenkins node.

A subsequent pipeline run takes us a step further...