Book Image

AWS for System Administrators

By : Prashant Lakhera
Book Image

AWS for System Administrators

By: Prashant Lakhera

Overview of this book

Amazon Web Services (AWS) is one of the most popular and efficient cloud platforms for administering and deploying your applications to make them resilient and robust. AWS for System Administrators will help you to learn several advanced cloud administration concepts for deploying, managing, and operating highly available systems on AWS. Starting with the fundamentals of identity and access management (IAM) for securing your environment, this book will gradually take you through AWS networking and monitoring tools. As you make your way through the chapters, you’ll get to grips with VPC, EC2, load balancer, Auto Scaling, RDS database, and data management. The book will also show you how to initiate AWS automated backups and store and keep track of log files. Later, you’ll work with AWS APIs and understand how to use them along with CloudFormation, Python Boto3 Script, and Terraform to automate infrastructure. By the end of this AWS book, you’ll be ready to build your two-tier startup with all the necessary infrastructure, monitoring, and logging components in place.
Table of Contents (18 chapters)
1
Section 1: AWS Services and Tools
4
Section 2: Building the Infrastructure
7
Section 3: Adding Scalability and Elasticity to the Infrastructure
11
Section 4: The Monitoring, Metrics, and Backup Layers

The v backup options offered by AWS

Before we start diving into AWS's various backup offerings, we first need to understand why we back up our data.

Why do we back up data?

One of the primary reasons we perform backups is to minimize data loss. Lost data will impact our business by impacting our brand, revenue, and trust in our customer relationships. So, the first thing we need to decide as an organization is how much data loss we can afford. Data loss can be defined in terms of a rcovery point objective (RPO). The RPO will dictate the backup frequency, which is the solution that we use to perform the backup, as it's the measurement of the maximum tolerable limit of our data loss. The other factor we need to consider is the recovery time objective (RTO), the amount of time it will take to recover, which is directly correlated to how much your business can afford to operate with that particular application offline or down.

Now the question is, why don't we back...