Book Image

AWS Automation Cookbook

By : Nikit Swaraj
5 (1)
Book Image

AWS Automation Cookbook

5 (1)
By: Nikit Swaraj

Overview of this book

AWS CodeDeploy, AWS CodeBuild, and CodePipeline are scalable services offered by AWS that automate an application's build and deployment pipeline. In order to deliver tremendous speed and agility, every organization is moving toward automating their entire application pipeline. This book will cover all the AWS services required to automate your deployment to your instances. You'll begin by setting up and using one of the AWS services for automation –CodeCommit. Next, you'll learn how to build a sample Maven and NodeJS application using CodeBuild. After you've built the application, you'll see how to use CodeDeploy to deploy the application in EC2/Auto Scaling. You'll also build a highly scalable and fault tolerant Continuous Integration (CI)/Continuous Deployment (CD) pipeline using some easy-to-follow recipes. Following this, you'll achieve CI/CD for a microservice application and reduce the risk within your software development life cycle globally. You'll also learn to set up an infrastructure using CloudFormation templates and Ansible, and see how to automate AWS resources using AWS Lambda. Finally, you'll learn to automate instances in AWS and automate the deployment lifecycle of applications. By the end of this book, you'll be able to minimize application downtime and implement CI/CD, gaining total control over your software development lifecycle.
Table of Contents (11 chapters)

Integrating Jenkins with all of the AWS developers tools

In all the previous recipes, we configured AWS services and the Jenkins server. Now, it's time to integrate Jenkins with all of the tools of AWS that we had configured earlier and achieve the use-case or scenario. So whenever the latest code will be checked in the master branch of the repository (CC-AWSSTAR-APP), then based on the cron or Poll SCM parameter, Jenkins will get trigger. Jenkins will pull the latest code from the repository to its workspace. Then, it will run the commands which is mentioned in the build step of it. So basically, Jenkins will start building the code. Once the build will take place successfully, it will trigger an email. Post that, it will upload the build artifact in one of the S3 bucket (awsstar-s3-code), where revisions will be placed. Then, again the artifact will be uploaded to another...