BuiltForProd documentation
This site documents the three BuiltForProd offerings: the Baseline (a production-ready, multi-account cloud foundation), the Blueprints (production-ready reference architectures deployed on the Baseline) and Managed (engineers who operate and evolve the result). The Platform set you are reading is public. The sets for each cloud and blueprint open to customers who hold that product.
What the documentation covers
| Set | What it holds | Who can read it |
|---|---|---|
| Platform | The BuiltForProd Standard, key concepts, the products, the service explainers, the glossary, support and trust pages | Everyone |
| AWS Baseline | The landing zone: 14 accounts, hub-and-spoke network, security services, identity, delivery pipeline | Overview public; the rest needs sign-in and the AWS Baseline |
| Web App Blueprint | A working web application on EKS, ArgoCD, DocumentDB, ElastiCache and CloudFront | Overview public; the rest needs the blueprint |
| Data and ETL Blueprint | A zoned S3 data lake with Glue, Lake Formation and a Lambda trigger | Overview public; the rest needs the blueprint |
| Secrets Blueprint | Application secrets encrypted with SOPS and AWS KMS, synced to SSM Parameter Store | Overview public; the rest needs the blueprint |
| Azure Baseline, GCP Baseline | Sample placeholders until those baselines ship | Everyone |
The clouds
AWS is the cloud the products run on today: the AWS Enterprise Baseline and three blueprints exist as production-ready repositories. Baselines for Azure and GCP, and further blueprints, are the next phase. The roadmap page states exactly what the offerings note commits to and nothing more.
How to navigate
- The navigation bar switches between the Platform pages and the documentation for each cloud and blueprint.
- Every page ends with What's next and Related topics. Follow them and you read the set in a sensible order.
- Sample values such as
acme,company.com,us-west-2and the account ids111111111111to151515151515are placeholders. When you sign in and your organization profile is filled in, the pages show your own values. How to use these docs explains the mechanism. - Search is split by set, so a query on an AWS Baseline page searches the Baseline first.
Where to start by role
| You are | Start here |
|---|---|
| Deciding whether to buy | What is BuiltForProd, then the products and purchasing and licensing |
| An architect | Architecture overview, then the BuiltForProd Standard |
| A platform or DevOps engineer | Key concepts, then Terragrunt units and stacks |
| A developer or data engineer | Key concepts, then the blueprints |
| A security reviewer or auditor | Security posture summary, then Compliant |
| An operator | Operable, then support tiers |
The full ordered lists are on reading paths by role.
The standard behind every page
Everything BuiltForProd ships is measured against eight properties: Secure, Reliable, Observable, Scalable, Automated, Recoverable, Compliant and Operable. The BuiltForProd Standard defines each one and names the mechanism in the code that delivers it. The prerequisites page lists what your organization needs in place before a deployment is handed over.