Book Image

AWS Certified Solutions Architect ??? Associate Guide

By : Gabriel Ramirez, Stuart Scott
Book Image

AWS Certified Solutions Architect ??? Associate Guide

By: Gabriel Ramirez, Stuart Scott

Overview of this book

Amazon Web Services (AWS) is currently the leader in the public cloud market. With an increasing global interest in leveraging cloud infrastructure, the AWS Cloud from Amazon offers a cutting-edge platform for architecting, building, and deploying web-scale cloud applications. As more the rate of cloud platform adoption increases, so does the need for cloud certification. The AWS Certified Solution Architect – Associate Guide is your one-stop solution to gaining certification. Once you have grasped what AWS and its prerequisites are, you will get insights into different types of AWS services such as Amazon S3, EC2, VPC, SNS, and more to get you prepared with core Amazon services. You will then move on to understanding how to design and deploy highly scalable applications. Finally, you will study security concepts along with the AWS best practices and mock papers to test your knowledge. By the end of this book, you will not only be fully prepared to pass the AWS Certified Solutions Architect – Associate exam but also capable of building secure and reliable applications.
Table of Contents (26 chapters)
22
Mock Test 1
23
Mock Test 2

CI / CD pipeline

Jez Humble in his book, Continuous Delivery, speaks about this and he says, "if it hurts, do it more often, and bring the pain forward.". So, are you in pain when you deploy new versions to production, or do the development team suffers when they integrate their code every week? If you answered yes to any of these two questions, maybe you need to adopt the practice of Continuous Integration (CI) and Continuous Deployment (CD).

Continuous Integration consist of the frequent and early integration process between code branches. This process must be made automatically every time a developer pushes code to development branches. The exhaustive code testing must be performed in parallel and provide early results about test failures, incompatible interfaces, or regressions in code. All of this has the purpose to improve the quality of software, we want to fail...