AWS Cookbook

AWS Cookbook

  • Downloads:7606
  • Type:Epub+TxT+PDF+Mobi
  • Create Date:2022-02-26 06:51:50
  • Update Date:2025-09-06
  • Status:finish
  • Author:John Culkin
  • ISBN:1492092606
  • Environment:PC/Android/iPhone/iPad/Kindle

Summary

This practical guide provides over 70 self-contained recipes to help you creatively solve common AWS challenges you'll encounter on your cloud journey。 If you're comfortable with rudimentary scripting and general cloud concepts, this cookbook provides what you need to address foundational tasks and create high-level capabilities。

Authors John Culkin and Mike Zazon share real-world examples that incorporate best practices。 Each recipe includes a diagram to visualize the components。 Code is provided so that you can safely execute in an AWS account to ensure solutions work as described。 From there, you can customize the code to help construct an application or fix an existing problem。 Each recipe also includes a discussion to provide context, explain the approach, and challenge you to explore the possibilities further。

Go beyond theory and learn the details you need to successfully build on AWS。 The recipes help you:

Redact personal identifiable information (PII) from text using Amazon Comprehend
Automate password rotation for Amazon RDS databases
Use VPC Reachability Analyzer to verify and troubleshoot network paths
Lock down Amazon Simple Storage Service (S3) buckets
Analyze AWS Identity and Access Management policies
Autoscale a containerized service

Download

Reviews

Sebastian Gebski

I didn't plan to read it initially, but I've briefly skimmed through - only to find some recipes that have appeared so useful that they have caught my immediate attention。 Why so? What was so special about them?1。 They represented some patterns - good practices and useful application of atomic services2。 They were CLI-based (not web console-based): good for scripting, automation, everyday use in general3。 Web console has many non-obvious defaults - you "click" one thing, but 2 more come "in pack I didn't plan to read it initially, but I've briefly skimmed through - only to find some recipes that have appeared so useful that they have caught my immediate attention。 Why so? What was so special about them?1。 They represented some patterns - good practices and useful application of atomic services2。 They were CLI-based (not web console-based): good for scripting, automation, everyday use in general3。 Web console has many non-obvious defaults - you "click" one thing, but 2 more come "in package"; CLI is much more explicit - it helps you build a better understanding of what's actually happening there4。 You can find here many "auxiliary" (supporting) services that are usually used as an addition to other ones, but aren't many popular, so many do not even know about their existence。 Good example: IAM Policy Simulator, VPC Reachability Analyzer, S3 Storage Lens。TBH not all of the recipes were so interesting, but as the book follows the cookbook structure, you don't have it read it carefully end-to-end。 Any other drawbacks? In fact, yes - quite a serious one: the actual solution description is typically very scarce。 The recipe tells you WHAT to do, but not WHY to do it (that exact activity - how does it contribute to the overall goal)。 In many cases, it's quite easy to figure it out, but someone with more limited AWS experience may struggle with intricacies of IAM or VPC (e。g。 why to create this role, why this execution role needs that policy, why did we just split the security group, etc。)。Btw。 please keep in mind that IaC is not used in the book。 The approach here is fully imperative, not declarative。 It's not a bad thing - just do not reach for this book if you want to learn IaC (CF or CDK)。In the end, I find "AWS Cookbook" really useful。 But please keep in mind I didn't pay for it (literally) - it was included in my OReilly subscription。 Well deserved 3。7-4。0 stars。 。。。more

Andrei Barbu

This is a cookbook in the sense of 'what to type in to do X' instead of 'how to do X'。 This is a cookbook in the sense of 'what to type in to do X' instead of 'how to do X'。 。。。more