What's changed: Initial: 5 sections for Domain 2 (implementation and integration)
2.3Designing Enterprise Integration Architectures
Learn to embed FM capabilities into existing enterprise environments: event-driven (EventBridge), GenAI gateway, identity federation/RBAC/least privilege, Outposts/Wavelength, and CI/CD with CodePipeline/CodeBuild.
GenAI delivers value when integrated into existing business systems, not in isolation. The exam tests integration that is loosely coupled, securely accessed, and compliant.
2.3.1Enterprise integration patterns
- Event-driven integration: add GenAI to existing apps loosely via EventBridge/Lambda webhooks.
- GenAI gateway: a central abstraction layer for FM consumption that centralizes auth, rate limiting, observability, and policy.
- Secure access: identity federation between FM services and enterprise systems, RBAC, and least-privilege API access to FMs.
- Data sovereignty/edge: meet cross-jurisdiction data needs with Outposts (on-prem) and Wavelength (edge).
- CI/CD: continuously deploy/test GenAI components with CodePipeline/CodeBuild, including security scans and rollback.
Common: add to existing apps loosely = event-driven (EventBridge), central control of FM usage = GenAI gateway, cross-jurisdiction data/on-prem = Outposts, edge = Wavelength, continuous GenAI deployment = CodePipeline/CodeBuild.
Enterprise integration hinges on loose coupling and central control. Insert GenAI into existing systems loosely via API Gateway + Lambda (webhook handlers) or EventBridge (event-driven), designing sync patterns with legacy. Centralize FM usage behind a GenAI gateway (a central abstraction layer) that unifies auth, rate limiting, cost allocation, observability, and policy. Secure access with federation between FM services and the corporate IdP, RBAC for models/data, and least-privilege APIs to FMs. For data sovereignty/low latency, route securely between cloud and on-prem with Outposts (on-prem) and Wavelength (5G edge). Deliver with CodePipeline/CodeBuild, continuously deploying GenAI components (prompts, flows, agents) with automated tests, security scans, and rollback.
| Need | Use | Point |
|---|---|---|
| Loose addition | EventBridge/Lambda | Event-driven/webhook |
| Central FM governance | GenAI gateway | Auth/rate/observability/policy |
| On-prem/edge | Outposts/Wavelength | Data sovereignty/low latency |
| Continuous delivery | CodePipeline/CodeBuild | Test/scan/rollback |
Trap: “each app should call Bedrock directly; no central gateway needed” is wrong at scale—a GenAI gateway centralizes auth, cost, observability, and policy. Also “broad permissions to FMs are convenient” is wrong—least privilege is the rule.
2.3.2Section summary
- Loose = EventBridge / central = GenAI gateway / delivery = CodePipeline
- Access = federation + RBAC + least privilege / on-prem·edge = Outposts/Wavelength
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want to add GenAI summarization triggered by an order-confirmed event to an existing order system, loosely and without modifying the core. Best option?
Q2. Many internal apps are starting to use Bedrock, and you want to centralize auth, rate limiting, cost allocation, and observability. Best option?
Q3. You want to continuously deploy GenAI components (prompts, flows) to production with automated tests, security scans, and rollback on failure. Best option?