Book Image

AWS for Solutions Architects

By : Alberto Artasanchez
3 (1)
Book Image

AWS for Solutions Architects

3 (1)
By: Alberto Artasanchez

Overview of this book

One of the most popular cloud platforms in the world, Amazon Web Services (AWS) offers hundreds of services with thousands of features to help you build scalable cloud solutions; however, it can be overwhelming to navigate the vast number of services and decide which ones best suit your requirements. Whether you are an application architect, enterprise architect, developer, or operations engineer, this book will take you through AWS architectural patterns and guide you in selecting the most appropriate services for your projects. AWS for Solutions Architects is a comprehensive guide that covers the essential concepts that you need to know for designing well-architected AWS solutions that solve the challenges organizations face daily. You'll get to grips with AWS architectural principles and patterns by implementing best practices and recommended techniques for real-world use cases. The book will show you how to enhance operational efficiency, security, reliability, performance, and cost-effectiveness using real-world examples. By the end of this AWS book, you'll have gained a clear understanding of how to design AWS architectures using the most appropriate services to meet your organization's technological and business requirements.
Table of Contents (20 chapters)
1
Section 1: Exploring AWS
4
Section 2: AWS Service Offerings and Use Cases
11
Section 3: Applying Architectural Patterns and Reference Architectures
17
Section 4: Hands-On Labs

Choosing the right tool for the job

In the previous sections, we learned how to classify databases, and we learned about the different services that AWS provides. Now comes the hard part: deciding which service is the right one for our particular use case. As technologists, we often fall in love with the latest shiny new object we have learned about, and because we have a hammer, everything looks like a nail. Firstly, we should spend a significant amount of time clearly articulating the business problem we are trying to solve. Often, your client will have a set of requirements and, based on your experience, you know they want or need something else. The problem statement should be carved and shaped to its most precise and simple level. Once you get signoff or agreement from all parties involved, only then is it time to start thinking about what the right tool for the job is.

Some of the questions the requirements should answer are as follows:

  • How many users are expected...