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)

Creating an AMIs of the EC2 instance using AWS lambda and CloudWatch

In the era of Cloud and DevOps, maintaining multiple copies of your data will save you whenever there is something wrong with the server. A backup of your data is important, because you can restore your lost data using it. In AWS, you can take a backup of EBS. You can automate the backup of EBS using any custom script, which will use ec2 api and take a snapshot of the same. Earlier, we used to keep that script in any server and schedule it using cron; but now, we use lambda instead of server where we keep our script of taking a backup of EBS. Using lambda will remove the need of another server, which was needed to run the script on cron basis. Having EBS backup, means the snapshot is good, but if you have multiple EBS volumes attached to an instance, then it's recommended to take the AMI of the instance...