Book Image

AWS Automation Cookbook

By : Nikit Swaraj
Book Image

AWS Automation Cookbook

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)

Working with Kubernetes on AWS using AWS resources

We provisioned the Kubernetes cluster on AWS, therefore, we will try to integrate with AWS services wherever possible.

For storing docker images, we will use ECR; for LoadBalancer, we will use ELB; and for persistence storage, we will be using EBS. There are a couple of important points that needs to be taken care before implementing.

  1. Each and every master and worker node should be attached with the IAM role that has the permission of AWS resources such as S3, EC2, VPC, Route53, and so on. But that's not enough, we also have to run the aws configure command, but we don't need to fill AccessKey and SecretKey but region name, because the key is for global purpose and to provision a resource we have to mention region name.
  2. If a Kubernetes cluster is setup by kops or given an argument of --cloud-provider=aws in configuration...