Book Image

AWS Certified Developer - Associate Guide - Second Edition

By : Vipul Tankariya, Bhavin Parmar
5 (2)
Book Image

AWS Certified Developer - Associate Guide - Second Edition

5 (2)
By: Vipul Tankariya, Bhavin Parmar

Overview of this book

This book will focus on the revised version of AWS Certified Developer Associate exam. The 2019 version of this exam guide includes all the recent services and offerings from Amazon that benefits developers. AWS Certified Developer - Associate Guide starts with a quick introduction to AWS and the prerequisites to get you started. Then, this book will describe about getting familiar with Identity and Access Management (IAM) along with Virtual private cloud (VPC). Next, this book will teach you about microservices, serverless architecture, security best practices, advanced deployment methods and more. Going ahead we will take you through AWS DynamoDB A NoSQL Database Service, Amazon Simple Queue Service (SQS) and CloudFormation Overview. Lastly, this book will help understand Elastic Beanstalk and will also walk you through AWS lambda. At the end of this book, we will cover enough topics, tips and tricks along with mock tests for you to be able to pass the AWS Certified Developer - Associate exam and develop as well as manage your applications on the AWS platform.
Table of Contents (30 chapters)
Free Chapter
1
Overview of AWS Certified Developer - Associate Certification

The need for CodeDeploy

In general, once software development (that is, such as feature, bug-fix, or hot-fix) is done, and code is committed last time to a specific forked source control branch, then it gets merged to a development and, subsequently, into the master branch. Usually, a peer code review takes place before merging a code into the development branch or any other branch from the forked branch. Now, if this development has been executed using a language that requires a compilation such as Java, VB.NET, or C#, it needs to trigger a build process. Again, upon committing a new change or development, a build process is triggered with the new change.

In broad terms, the build process is nothing but compiling the project. If this development or change is done at the level where compilation is not required, such as HTML, JavaScript, or PHP, then it doesn't need to trigger...