Book Image

Implementing AWS: Design, Build, and Manage your Infrastructure

By : Yohan Wadia, Rowan Udell, Lucas Chan, Udita Gupta
Book Image

Implementing AWS: Design, Build, and Manage your Infrastructure

By: Yohan Wadia, Rowan Udell, Lucas Chan, Udita Gupta

Overview of this book

With this Learning Path, you’ll explore techniques to easily manage applications on the AWS cloud. You’ll begin with an introduction to serverless computing, its advantages, and the fundamentals of AWS. The following chapters will guide you on how to manage multiple accounts by setting up consolidated billing, enhancing your application delivery skills, with the latest AWS services such as CodeCommit, CodeDeploy, and CodePipeline to provide continuous delivery and deployment, while also securing and monitoring your environment's workflow. It’ll also add to your understanding of the services AWS Lambda provides to developers. To refine your skills further, it demonstrates how to design, write, test, monitor, and troubleshoot Lambda functions. By the end of this Learning Path, you’ll be able to create a highly secure, fault-tolerant, and scalable environment for your applications. This Learning Path includes content from the following Packt products: • AWS Administration: The Definitive Guide, Second Edition by Yohan Wadia • AWS Administration Cookbook by Rowan Udell, Lucas Chan • Mastering AWS Lambda by Yohan Wadia, Udita Gupta
Table of Contents (29 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Introducing AWS CodePipeline


AWS CodePipeline is a continuous delivery service that you can use to model, visualize, and automate the steps required to release your application software. This is made possible by building pipelines that contain one or more stages. The stages can be broadly classified as build, where the code is compiled and built using, say, AWS CodeBuild or some other third-party tool, staging, and deployment, where the code is pushed on to compute instances using AWS CodeDeploy, and so on. Each stage internally describes a set of actions that it needs to perform in order to prepare the software for its release. This action can be anything from building your source code from a Git repository, to making changes to a file, or deploying packages, and so on. Every change made to either your code or some configurational setting within CodePipeline is considered as a revision and you can have multiple such revisions created within a single stage of a pipeline.

Note

Even changes...