Chapter Seven
Developer Tools & Integration
Two themes in one chapter: defining infrastructure as code, and wiring services together with messages and events. Together they are how AWS systems are built repeatably and decoupled cleanly.
The first three services define infrastructure as code: CloudFormation is the declarative engine, the CDK generates it from real programming languages, and the Code* pipeline ships changes through build and deploy stages.
The last four are the integration layer — EventBridge, SQS, SNS, and Step Functions — the messaging and orchestration that let components fail independently instead of together.
Services in This Chapter
Service 46
AWS CloudFormation
Infrastructure as code in JSON or YAML. Declares resources as stacks AWS creates, updates, and deletes as a unit — the native IaC engine.
Service 47
AWS CDK
Define infrastructure in TypeScript, Python, or Java; the CDK synthesizes CloudFormation. Real code — loops, abstractions, tests — instead of hand-written YAML.
Service 48
CodePipeline, CodeBuild & CodeDeploy
AWS's native CI/CD trio — orchestration, build, and deployment — wired together for pipelines that live entirely inside AWS.
Service 49
Amazon EventBridge
A serverless event bus that routes events between AWS services, SaaS, and your apps by rule. The backbone of event-driven architectures.
Service 50
Amazon SQS
Managed message queues. Decouples producers from consumers and absorbs spikes — the simplest, most durable way to buffer work.
Service 51
Amazon SNS
Pub/sub messaging and fan-out. One message delivered to many subscribers — queues, Lambdas, HTTP endpoints, email, SMS.
Service 52
AWS Step Functions
Serverless workflow orchestration as state machines. Coordinates Lambdas and services with retries, branching, and error handling — visibly.