Security and Microservice Architecture on AWS: Architecting and Implementing a Secured, Scalable Solution

This is a good book, but it falls short in the 2nd half. It offers a solid guided tour of AWS from a security point of view, covering most of the AWS services you're likely to know and use (VPC, EC2, EKS, S3, Lambda etc.).The writing is straight forward and approachable to anyone with moderate technical experience, tho you'll be much better off if you already understand the essentials of networking (CIDR, subnets, etc.), system administration, and VMs, containers, and Kubernetes. Each chapter focuses on a clear essential topic (IAM, encryption, monitoring/response, etc.), and they build progressively in a coherent way. The focus is on microservice architectures, but most of the AWS features covered can apply more broadly to any architecture you might be using.My only complaints about this book are:1) The 2nd half covers more complicated topics, but does so with less depth. The author covers a lot of ground, but he ends up only giving a quick overview of those things (ex: TLS, App Mesh, Managing multiple AWS accounts, and incident monitoring and response).2) There are lots of screenshots of AWS console throughout, but 90% are impossibly small and totally illegible. Whoever did the layout graphics needs to be fired for the 2nd edition. I like screenshots, but these will be of little use to anyone.3) While screenshots are nice, there's almost zero code in this book. There are scattered snippets of JSON examples for things like IAM policies, but even these are few and far between. A book with "...Implemenging..." in the title should have extensive examples of AWS CLI at the very least. Gaurav Raje seems to think none of his readers will use the CLI or shell scripts/automation anywhere; He refers almost exclusively (in writing and graphics) to getting things done via AWS Console (i.e. the browser) instead of the terminal, much less DevOps tools like Terraform, Ansible, etc.I actually really like this book, and I'm glad I read it. It just suffers from the same complaint I have about O'Reilly's other popular architecture books from Ford, Newman, and others (which Raje refers to repeatedly, ironically enough): These books all tell you _what_ you should do, without delivering the goods on _how_ to actually do it in practice. Raje gets closer to delivering the tactical goods than his contemporaries, but he still falls short in the end (and notably, he fails to deliver enough external links to AWS docs, etc., for further reading on the topics he does cover).Final word: This is a solid guided tour of the essential security tools and techniques everyone building on AWS should know and master. It's an easy read, covers a lot of ground, and offers plenty of valuable tips and best practices along the way. I just wish it offered enough actual *implementation* details and depth to fully live up to the title on the cover.

On the first glance book is well made with a lot of diagrams. When you start reading it the text quite disorganized and confused, and diagrams at time are comically unrelated to what the author apparently tries to say. It is not that you can't understand what what author is saying, but it is not clear what he wants to say.Overall the book content feel slapped together, which is critical flow for its subject matter: security. Where attention to details and attention that details fit perfectly into the whole picture is paramount.After reading first to chapters I am going to return it to Amazon, order just released AWS security book by Manning and hope that that one is better.