Skip to main content

Angle 4 — education-portal-and-workshop-patterns

Generated at build time from research/aws-demo-catalog/sources/education-portal-and-workshop-patterns.md in the repo — edit the source, not this page.

Date: 2026-09-04 (all retrievals on this date unless a source carries its own date). Scope: how AWS and others structure "learn a solution through a working deployment", to shape P0 and give a link / fork / build recommendation per catalog item from the content-structure point of view. Repo-coverage detail belongs to angle 1; this file cites repos only where they define a documentation or workshop convention.

Summary​

AWS now has three distinct "learn by deploying" surfaces, each with a stable, copyable page anatomy: (1) Workshop Studio (catalog.workshops.aws, surfaced since 2025-11-18 through AWS Builder Center) — markdown modules plus a contentspec.yaml that declares CloudFormation templates for either AWS-provisioned event accounts or the learner's own account; (2) the Solutions Library, whose Guidance and Solution pages moved to docs.aws.amazon.com/solutions/ (301 redirects observed today) and follow a fixed layout — overview, architecture diagram with numbered steps, "Deploy with confidence" (GitHub sample or CloudFormation launch), six Well-Architected pillar paragraphs, related content — with the cost table living in the sample repo README (Guidance) or the implementation guide (Solution); (3) aws-samples / aws-solutions-library-samples repos with an MIT-0 license, a Security + License README tail, and, for Guidance repos, a README contract of Overview → Cost → Prerequisites → Deployment Steps → Deployment Validation → Running → Next Steps → Cleanup. Healthcare coverage on Workshop Studio is thin: four healthcare workshops exist (HealthLake basics, "Intelligent Healthcare Systems", SMART on FHIR with HealthLake, HealthOmics end-to-end) plus one HCLS agents workshop; none covers F0 as a single account, U1 as a portal-plus-mobile app, or U2 at all. Healthcare Guidance is stronger on U3, U4 and U5. For P0, the recommended pattern is the Backstage TechDocs / Antora model — each use-case repo owns its README, ADRs (docs/decisions/NNNN-*.md, MADR 4) and a contentspec.yaml, and the portal aggregates those at build time rather than holding prose of its own.

A. Workshop Studio / catalog.workshops.aws — mechanics​

#FindingSourceTierConfidence
A1Workshop Studio has two provisioning modes. AWS event: the learner signs in at catalog.workshops.aws with Email OTP or Login with Amazon, enters an event access code, and gets a dashboard with "Open AWS Console" plus event outputs (e.g. IDE URL, credentials). Own account: the same workshop is followed in the learner's account.eksworkshop.com "At an AWS event" setup page (AWS-run workshop), retrieved 2026-09-04 — https://www.eksworkshop.com/docs/introduction/setup/aws-eventPractitioner (AWS-maintained workshop docs, not product docs)High for the mechanics; account lifetime not stated on this page.
A2Event accounts are free to the attendee and are terminated after the event (one older AWS-run workshop states 72 hours after the workshop).Amplify iOS Workshop, "Use a Workshop AWS Account" — https://amplify-ios-workshop.go-aws.com/10_prerequisites/05_event_engine.html (undated, pre-Builder-Center)PractitionerMedium — dated page; treat the 72 h figure as indicative.
A3Since 2025-11-18 workshops are discoverable in AWS Builder Center (builder.aws.com/build/workshops) with filters by category, AWS service, level (100–400) and duration (1–8 h); "hundreds" of workshops; the announcement frames them as guided tutorials in your own AWS account; free Builder ID needed.AWS What's New, 2025-11-18 — https://aws.amazon.com/about-aws/whats-new/2025/11/workshops-available-aws-builder-centerPrimaryHigh
A4Workshop content is a git repo with contentspec.yaml at root, content/ (one index.<lang>.md per folder = one page), static/ (images and CloudFormation templates), optionally infrastructure/ (CDK). The synthesised CDK template is copied into static/ and referenced from contentspec.yaml.aws-samples/sample-agent-jailbreak-to-cloud-takeover README (MIT-0), retrieved 2026-09-04 — https://github.com/aws-samples/sample-agent-jailbreak-to-cloud-takeoverPrimary (repo)High
A5contentspec.yaml (version 2.0) declares: locales; additionalLinks; awsAccountConfig with accountSources: [WorkshopStudio, CustomerProvided], a participant IAM role policy, EC2 key-pair flag; regionConfiguration (min/max regions, deployable region); infrastructure.cloudformationTemplates[] each with templateLocation, label, participantVisibleStackOutputs, requiredCapabilities, parameters. This is the whole "empty account → running" contract for a workshop.aws-samples/rancher-on-aws-workshop contentspec.yaml — https://github.com/aws-samples/rancher-on-aws-workshop/blob/main/contentspec.yamlPrimary (repo)High
A6A CDK app can be wrapped as a single self-contained CloudFormation template (static/CDKDeployer.template.json, CodeBuild runs cdk bootstrap + cdk deploy) so Workshop Studio can provision a CDK stack; the tool has a setup-workshop command that also edits contentspec.yaml. Community tool, Apache-2.0.flochaz/cdk-standalone-deployer — https://github.com/flochaz/cdk-standalone-deployer (39 commits; no release date visible)PractitionerMedium — useful pattern; verify maintenance before depending on it.
A7Before Workshop Studio, AWS workshops were Hugo sites (content/ with _index.md, numbered folders introduction / modules / conclusion / cleanup, static/, config.toml, hugo-theme-learn). Legacy *.workshop.aws hosts now 301 to Workshop Studio (observed for amazon-healthlake.workshop.aws → catalog.us-east-1.prod.workshops.aws/v2/workshops/498fdbc5-…).aws-samples/aws-modernization-workshop-sample "Edit and Build" — https://aws-samples.github.io/aws-modernization-workshop-sample/20_build/2_editing/ ; redirect observed 2026-09-04Primary (repo docs) + direct observationHigh
A8AWS's largest open workshop (EKS Workshop v2) is not on Workshop Studio: Docusaurus site + Terraform in one repo (Apache-2.0), own-account path with an explicit cost warning and cleanup guide, modules Introduction / Fundamentals / Observability / Security / Networking / Automation / AI/ML / Troubleshooting; IDE bootstrapped by a CloudFormation quick-create link. Shows AWS itself uses docs-as-code outside Workshop Studio when the content is large.https://github.com/aws-samples/eks-workshop-v2 ; https://www.eksworkshop.com/docs/introduction/setup/your-accountPrimary (repo)High

Method caveat: Workshop Studio pages are client-rendered; WebFetch returned only the page title for every catalog URL tried. Module-level detail below therefore comes from AWS-published descriptions, backing GitHub repos and search snippets, and is marked accordingly.

B. Healthcare / life-sciences workshop inventory, mapped to catalog items​

#Workshop (Workshop Studio)What it covers (as far as verifiable)Catalog item / tierLink-worthy?SourceTierConfidence
B1Amazon HealthLake Workshop — IDs 498fdbc5-46e1-4cb0-97a0-f4ec3a30f26a (v2) and 4849824d-084a-4a64-a237-f05027f54abc (listed on the HealthLake getting-started page)"creating an AWS HealthLake Data Store, importing synthetic data into it, exporting data, and generating a QuickSight Dashboard". Backing repo: CloudFormation setup templates, Synthea data generation, Athena notebook, QuickSight notes. Repo archived 2026-02-04 (read-only), MIT-0.U5 Tier 1 (HealthLake → Athena → BI) partial; U1 Tier 1 HealthLake component onlyLink for "what HealthLake is" only; do not fork (archived; QuickSight naming predates Amazon Quick).https://aws.amazon.com/healthlake/getting-started/ ; https://github.com/aws-samples/healthlake-workshopPrimary (AWS page + repo)High on scope/archival; module list unverified.
B2Intelligent Healthcare Systems: FHIR, AI, and AWS HealthLake — da0cf4f5-63d4-4e4b-bf98-6a48b748d914AWS describes it as guiding you "through building an AI-powered healthcare data pipeline that transforms unstructured medical documents" (into FHIR on HealthLake, with Bedrock).U4 Tier 2 (documents → structured), U3 Tier 2 partialLink as a Tier-2 "documents to FHIR" primer; not a substitute for a portal + mobile reference app.https://aws.amazon.com/healthlake/getting-started/ ; https://catalog.us-east-1.prod.workshops.aws/workshops/da0cf4f5-63d4-4e4b-bf98-6a48b748d914/en-USPrimary (AWS page) for the description; page body not retrievableMedium
B3SMART on FHIR with AWS HealthLake — 542c1a0f-7bd2-4f2f-8da9-699e953c7b26Title only retrievable; HealthLake docs confirm SMART on FHIR v1/v2 with a third-party OAuth 2.0 authorization server.U1 Tier 1 (auth + FHIR record) partialLink for the SMART/OAuth sub-topic; the catalog's Cognito-based patient auth still has to be built.https://catalog.us-east-1.prod.workshops.aws/workshops/542c1a0f-7bd2-4f2f-8da9-699e953c7b26 ; https://docs.aws.amazon.com/healthlake/latest/devguide/reference-smart-on-fhir.htmlPrimary (docs) for SMART support; workshop content unverifiedLow–Medium
B4AWS HealthOmics – End to End — catalog.workshops.aws/amazon-omics-end-to-endGenomics workflows, stores, analytics.None (no catalog item uses HealthOmics)Not needed; note only.https://catalog.workshops.aws/amazon-omics-end-to-end/en-USSearch snippet onlyMedium (existence), n/a (coverage)
B5Strands Agents and AgentCore for Healthcare and Life Science — fe97ac91-ff75-4753-a269-af39e7c3d765 (ko-KR listing indexed; en-US presumed)Related public material: aws-samples HCLS Agents Toolkit (docs site says "36+ reference agents" spanning drug research, clinical trials, genomics, commercialization, deployed to AgentCore) and aws-samples/sample-strands-agents-for-healthcare-and-life-sciences. Life-science skew.U1/U3/U5 Tier 2 (agent patterns), partialLink for AgentCore-in-HCLS patterns; fork agent templates where they fit; patient-facing assistant still to build.https://catalog.us-east-1.prod.workshops.aws/workshops/fe97ac91-ff75-4753-a269-af39e7c3d765/ko-KR ; https://aws-samples.github.io/amazon-bedrock-agents-healthcare-lifesciences/ ; https://github.com/aws-samples/sample-strands-agents-for-healthcare-and-life-sciencesPrimary (repos/docs site); workshop body unverifiedMedium
B6Generic (non-healthcare) official workshops that cover catalog tiers by component — "Diving Deep into Bedrock AgentCore (Official)"; "Getting started with AgentCore CLI (Official)"; "Agentic AI with Strands SDK and AgentCore"; "Building Production-Ready Generative AI Application"; "Intelligent Document Processing with AWS AI Services [Official]"; "Document Processing with Amazon Bedrock Data Automation" (c64e3606-…); "Amazon SageMaker AI Workshop" (9 labs, MLOps + governance); "Amazon SageMaker MLOps – from idea to production"; "End-to-End ML Development with SageMaker Studio and MLflow"; "Amazon Managed Service for Apache Flink workshop"; "AWS IoT Device Management Workshop"; "Amplify for web Immersion Day"; "Getting started with Amazon Connect".Titles and one-line descriptions only.Tier 2 (AgentCore set), U4 Tier 1/2 (IDP pair), Tier 3 (SageMaker set), U2 Tier 1 components (Flink, IoT DM), U1 Tier 1 platform (Amplify), U6 Tier 1 (Connect)Link as "prerequisite / go deeper" boxes inside chapters; none teaches a healthcare use case end to end.catalog.workshops.aws / catalog.us-east-1.prod.workshops.aws listings retrieved 2026-09-04 (URLs in source list)Search-index snippets of primary pagesMedium (existence), Low (module detail)
B7Not found on Workshop Studio / Builder Center (searched 2026-09-04): any remote-patient-monitoring or healthcare-IoT workshop; any HIPAA landing-zone / Control Tower-for-healthcare workshop; any HealthScribe, HealthImaging or standalone Comprehend Medical workshop; any Amazon Connect healthcare workshop; any patient-portal + mobile app workshop.—F0, U1 T1, U2 all tiers, U3 T1, U6These are where new work has demonstration value.Domain-restricted searches on catalog.workshops.aws, catalog.us-east-1.prod.workshops.aws, builder.aws.comAbsence-of-evidenceMedium — the catalog search index is incomplete; angle 1 may find repos, but no workshop surfaced.

Builder Center also carries healthcare articles (e.g. "Setting up a Managed FHIR Server on AWS Using AWS HealthLake", 2026-03-07; "AI in Healthcare: Predictive Diagnostics on AWS", 2026-02-24) under topic pages #healthcare and #healthcare-life-sciences-industry — these are community posts, not deployable workshops (https://builder.aws.com/learn/topics/healthcare; practitioner tier).

C. AWS Solutions Library — page anatomy and healthcare coverage​

#FindingSourceTierConfidence
C1Domain move. aws.amazon.com/solutions/guidance/<slug>/ and aws.amazon.com/solutions/implementations/<slug>/ return HTTP 301 to docs.aws.amazon.com/solutions/<slug>/. Any portal link to a Guidance should use the docs domain.Direct observation 2026-09-04 on patient-entity-resolution-with-aws-healthlake and landing-zone-accelerator-on-awsPrimary (observation)High
C2Guidance page anatomy (identical across four pages fetched): 1 Overview paragraph; 2 "How it works" — architecture PNG + downloadable PDF + numbered steps (9–11); 3 "Deploy with confidence" — one link, "Go to sample code" (GitHub, in aws-samples or aws-solutions-library-samples); 4 "Well-Architected Pillars" — six short paragraphs (OpEx, Security, Reliability, Performance, Cost, Sustainability), each linking the pillar whitepaper; 5 "Related content"; 6 "Read usage guidelines" → guidance-disclaimers. No cost table and no deployment steps on the page itself — both live in the repo README.https://docs.aws.amazon.com/solutions/patient-entity-resolution-with-aws-healthlake/ ; …/identifying-diagnosis-codes-from-clinical-notes-on-aws/ ; …/intelligent-document-processing-on-aws/ ; …/multi-modal-data-analysis-with-aws-health-and-ml-services/PrimaryHigh
C3Solution page anatomy (Landing Zone Accelerator on AWS): header metadata — Version 1.16.2, Released 9/2026, Author AWS, Est. deployment time 50 mins, Estimated cost link; Overview (with "will not, by itself, make you compliant" caveat); Benefits (3 cards); How it works (diagram + 10 steps); Deploy with confidence — "Open guide" (implementation guide) + "Launch in the AWS Console" (CloudFormation quick-create URL); Deployment options — download template, GitHub source; Related content (videos, blogs incl. "Introducing Landing Zone Accelerator for Healthcare"); AWS Support; RSS feed for releases.https://docs.aws.amazon.com/solutions/landing-zone-accelerator-on-aws/PrimaryHigh
C4Solution cost page pattern: one headline monthly figure for the sample configuration in us-east-1 with no workload ($430.22/month), a budget recommendation, then a table `AWS serviceDimensionsMonthly cost [USD]` with per-service usage assumptions and a footnote of services under $0.01. This is the cost-table shape the portal should copy per chapter.https://docs.aws.amazon.com/solutions/latest/landing-zone-accelerator-on-aws/cost.html
C5Guidance usage guidelines: sample code is "AWS Content" under the customer agreement, "You should not use this AWS Content in your production accounts", and deploying it may incur charges. Portal chapters that fork Guidance code should carry the same disclaimer.https://docs.aws.amazon.com/solutions/guidance-disclaimers/PrimaryHigh
C6Healthcare Guidance mapped to the catalog (details in table C-map below): Patient Entity Resolution with HealthLake (U5 T1 component); Identifying Diagnosis Codes from Clinical Notes (U3 T1/T2 partial); Intelligent Document Processing on AWS (U4 T1/T2 — now AgentCore-based); Multi-Modal Data Analysis with AWS Health and ML Services (U5 T1/T3 partial); Patient Outcome Prediction (listed in search; docs-domain URL returned 404 — unverified); LZA + LZA for Healthcare (F0, organisation-level).Pages above; https://github.com/aws-samples/landing-zone-accelerator-on-aws-for-healthcarePrimaryHigh for the four fetched; Low for Patient Outcome Prediction.
C7Healthcare Industry Lens for Well-Architected: published 2022-11-17, no revisions since (revision table has one row). Still the only AWS-official healthcare lens; usable as chapter framing for F0's "shared responsibility / HIPAA-eligible" narrative, but it predates Bedrock, HealthScribe and AgentCore.https://docs.aws.amazon.com/wellarchitected/latest/healthcare-industry-lens/healthcare-industry-lens.html ; …/document-revisions.htmlPrimaryHigh

C-map: healthcare Guidance / Solution vs catalog item

Guidance / SolutionStack shown on pageSample codeIaC / license (from repo README)Cost on page?Catalog fit
Guidance for Patient Entity Resolution with AWS HealthLakeAPI GW + Lambda, Neptune, DynamoDB, HealthLake, QuickSight, Entity Resolution, Step Functions, Glue, Athenaaws-samples/patient-matching-with-aws-healthlake-and-aws-entity-resolutionnot fetched (angle 1)NoU5 T1 (patient matching / EMPI) — one component
Guidance for Identifying Diagnosis Codes from Clinical Notes on AWSHealthLake ← FHIR; HealthScribe → S3; Comprehend Medical (ICD-10-CM); Lambda → Bedrock Converse; OpenSearch vector KB; Lake Formation; Athena; QuickSightaws-solutions-library-samples/guidance-for-identifying-diagnosis-codes-from-clinical-notes-on-awsCDK (Python); MIT-0; README cost table $495.89/month (April 2025, us-east-1) dominated by OpenSearch Serverless $350 and Bedrock $138No (in README)U3 T1 (HealthScribe + Comprehend Medical) and T2 (Bedrock coding) partial; no clinician review UI, no Step Functions, no write-back to HealthLake
Guidance for Intelligent Document Processing on AWSSES/S3 intake → EventBridge → Lambda → AgentCore Runtime / Identity / Gateway (Strands agents, MCP tools) → Textract, embeddings → ECS-hosted chat dashboard → AgentCore Observability; pillars text still references Comprehend Medical PHI redactionaws-samples/aws-ai-intelligent-document-processingCDK per pillar text; license not fetched (angle 1)NoU4 T1/T2 strong — the closest existing match to any catalog item and already on the 2026 AgentCore stack
Guidance for Multi-Modal Data Analysis with AWS Health and ML ServicesHealthOmics + HealthLake + HealthImaging → Lake Formation → Athena; SageMaker Processing, Feature Store, AutoGluon-Tabular, real-time endpoint; QuickSightaws-solutions-library-samples/guidance-for-multi-modal-data-analysis-with-aws-health-and-ml-servicesCloudFormation (1-click SageMaker domain); MIT-0; README sections Overview / Instructions / Security / License; no cost tableNoU5 T1 (lake + Athena) and T3 (Feature Store → model → endpoint) partial; imaging/genomics modalities out of scope
Landing Zone Accelerator on AWS (Solution) + LZA for Healthcare (config repo)35+ services; Control Tower Management/Audit/LogArchive required; healthcare config aligned to HIPAA, NCSC, ENS High, C5, FSE; healthcare repo v1.9.0-e released 2025-11-29 with HIPAA-eligible-services list update; ~$420/month baselineawslabs/landing-zone-accelerator-on-aws ; aws-samples/landing-zone-accelerator-on-aws-for-healthcareCDK inside CodePipeline; MIT-0 (healthcare repo)Yes ($430.22 sample table)F0 — full for the organisation layer; not single-account deployable (brief open question 2)

D. aws-samples / aws-solutions-library-samples repository conventions​

#FindingSourceTierConfidence
D1MIT-0 exists because sample/template code should impose "not even the cost of attribution"; it is the default license across aws-samples, serverless-patterns, LZA-for-Healthcare and both Guidance repos fetched. Apache-2.0 appears on some (extract-medical-insights…, eks-workshop-v2, jsii-docgen).https://github.com/aws/mit-0/blob/master/README.md ; repos cited in this filePrimaryHigh
D2Standard README tail: ## Security — "See CONTRIBUTING for more information." and ## License — "This library is licensed under the MIT-0 License." CONTRIBUTING carries "Security issue notifications" (report via the AWS vulnerability reporting page, not GitHub issues) and the Amazon Open Source Code of Conduct.guidance-for-multi-modal-data-analysis README; https://github.com/aws-samples/serverless-patterns/blob/main/CONTRIBUTING.mdPrimaryHigh
D3Pattern README contract (serverless-patterns, ~1,000+ patterns, 8,306 commits, MIT-0): every pattern ships Requirements, Deployment Instructions, How it works, Testing, Cleanup, plus example-pattern.json metadata that drives the Serverless Land site; explicit "there are costs associated with these services after the Free Tier" caveat. This is the smallest proven "docs from repo metadata" contract at AWS.https://github.com/aws-samples/serverless-patternsPrimaryHigh
D4Guidance README contract (aws-solutions-library-samples): observed sections Overview/Architecture → Data Flow → Services Used → Cost (table: service, dimensions, monthly USD, with month and region) → Prerequisites → Deployment Steps → Deployment/Test Validation → Running the Guidance → Next Steps → Cleanup → (FAQ, Notices, Authors). Adherence varies: diagnosis-codes repo follows it; multi-modal repo has only Overview/Instructions/Security/License; entity-resolution-prep repo uses a GitLab-style layout with no cost section. No public template repository was located.https://github.com/aws-solutions-library-samples/guidance-for-identifying-diagnosis-codes-from-clinical-notes-on-aws ; …/guidance-for-multi-modal-data-analysis-with-aws-health-and-ml-services ; …/guidance-for-preparing-and-validating-records-for-entity-resolution-on-awsPrimary (repos)Medium on "template" claim; High on observed sections.
D5Counter-example of a healthcare sample that is a snippet, not a deployment: extract-medical-insights-from-amazon-healthlake-with-bedrock — Streamlit app, pip install, no IaC, Apache-2.0, 13 commits. Portal must state "runbook-only" for such links.https://github.com/aws-samples/extract-medical-insights-from-amazon-healthlake-with-bedrockPrimaryHigh
D6Workshop-as-repo pattern: labs/00–10 sequential markdown, agents/, mcp-servers/, own-account deploy via AgentCore CLI, MIT-0, "expect total costs under $10", cleanup section. Shows AWS DevRel now ships workshops as plain repos as well as on Workshop Studio.https://github.com/aws-samples/sample-multi-agent-framework-protocol-agentcore-workshopPrimaryHigh
D7Workshop-with-CDK pattern: infrastructure/ (CDK TS) + content/ + static/ + contentspec.yaml in one repo, the synthesised template pushed to Workshop Studio for events and deployable locally with cdk deploy.https://github.com/aws-samples/sample-agent-jailbreak-to-cloud-takeoverPrimaryHigh

E. Documentation-from-code patterns (for P0's "content generated from the repos")​

#FindingSourceTierConfidence
E1AWS Prescriptive Guidance on ADRs (published March 2022): one ADR per architecturally significant decision; states Proposed → Accepted / Rejected → Superseded; accepted ADRs are immutable; the decision log is the project's context document; template sections Title, Status, Date, Context, Decision, Consequences (positive/negative), Compliance, Notes (author, version, changelog). Points to adr.github.io for templates.https://docs.aws.amazon.com/prescriptive-guidance/latest/architectural-decision-records/adr-process.html ; …/appendix.htmlPrimaryHigh
E2MADR 4.0.0 (2024-09-17): docs/decisions/NNNN-title-with-dashes.md, YAML front matter (status, date, decision-makers, consulted, informed), sections Context and Problem Statement, Decision Drivers, Considered Options, Decision Outcome, Consequences, Confirmation, Pros and Cons, More Information; MIT/CC0. Machine-parseable front matter makes ADRs a clean source for portal generation.https://adr.github.io/madr/PrimaryHigh
E3jsii-docgen generates API.md (TS/Python/Java/C#/Go) for jsii construct libraries; Construct Hub (constructs.dev, run by CDK Labs) is built on it and can be self-hosted; both Apache-2.0. Caveat: only for jsii-compiled construct libraries; a CDK app is documented with TypeDoc (comments → HTML/JSON, plugin-extensible).https://github.com/cdklabs/jsii-docgen ; https://github.com/cdklabs/construct-hub ; https://typedoc.org/PrimaryHigh
E4Backstage TechDocs ("docs-like-code"): markdown lives with the code; mkdocs.yml + catalog-info.yaml per repo; the portal builds and publishes each repo's docs (CI-driven, S3/GCS/Azure storage); Spotify runs 5,000+ sites; TechDocs v1.0 is a core Backstage product; docs reference v1.54.0. This is the canonical "portal aggregates repo-owned docs so nothing drifts" model.https://backstage.io/docs/features/techdocs/PrimaryHigh
E5Antora 3.2: a playbook lists content sources (repos, branches, tags); the site is generated from many repos into one site — lighter-weight alternative to TechDocs, AsciiDoc-based.https://docs.antora.org/antora/latest/PrimaryHigh
E6Docusaurus + remote content: docusaurus-plugin-remote-content (MIT, 83 commits) downloads markdown/images from remote repos at build time (constant sync or CLI sync). Fits the catalog's React/CloudFront stack if the portal stays on Docusaurus.https://github.com/rdilweb/docusaurus-plugin-remote-contentPractitionerMedium — small community plugin; consider a build-time git submodule/sparse-checkout instead.
E7AWS's own examples of repo-generated docs sites: eks-workshop-v2 (Docusaurus, content + Terraform in one repo) and the HCLS Agents Toolkit docs site (Astro on GitHub Pages, catalog of agents + guides). Microsoft Learn Architecture Center pages likewise expose original_content_git_url / gitcommit metadata — every page is a file in a git repo with ms.date and a 180-day review cycle.https://github.com/aws-samples/eks-workshop-v2 ; https://aws-samples.github.io/amazon-bedrock-agents-healthcare-lifesciences/ ; https://learn.microsoft.com/en-us/azure/architecture/ai-ml/architecture/baseline-microsoft-foundry-landing-zone (ms.date 2026-06-17)PrimaryHigh

F. Comparable "teach cloud through deployable use cases" portals​

#PortalWhat the page gives the learnerWhat works / does notSourceTierConfidence
F1AWS Serverless Land patterns (backed by aws-samples/serverless-patterns)Title + description; language/framework badge; download zip / GitHub; clone + deploy command; Testing; Cleanup; author card; related patterns. Left-hand filters by service and IaC.Works: one contract, machine-generated from example-pattern.json, thousands of entries. Does not: patterns are two-service integrations, not use cases.https://serverlessland.com/patterns/apigw-lambda-cdk ; https://github.com/aws-samples/serverless-patternsPrimaryHigh
F2AWS Builder Center workshops (Workshop Studio catalog)Filters category / service / level / duration; own-account tutorials; event mode via access code.Works: single discovery surface, level and duration up front. Does not: no healthcare use-case workshops beyond HealthLake basics (section B).https://aws.amazon.com/about-aws/whats-new/2025/11/workshops-available-aws-builder-centerPrimaryHigh
F3AWS Solutions Library Guidance / SolutionSee C2–C4: diagram + numbered steps + pillars + sample code (Guidance) or version / deploy time / cost / launch button (Solution).Works: the Solution header (version, released, deploy time, estimated cost) is the best "is this maintained?" signal on any AWS page. Does not: Guidance pages hide cost and steps in the repo.https://docs.aws.amazon.com/solutions/landing-zone-accelerator-on-aws/PrimaryHigh
F4Google Cloud Jump Start Solutions (announced 2023-04-18)Review (architecture diagram, monthly cost estimate, free-credit note) → Deploy (project, region, one click; Terraform underneath) → Explore (open app, list resources, delete). Initial six solutions. The docs index now 301s to the console solutions catalog (console.cloud.google.com/products/solutions/catalog), i.e. JSS is embedded in the console rather than a public docs page.Works: cost estimate before deploy and a delete button after are first-class. Does not: content is behind console sign-in; not linkable as public reading.https://cloud.google.com/blog/products/application-modernization/introducing-google-cloud-jump-start-solutions ; redirect observed 2026-09-04Primary (blog) + observationMedium on current state
F5Azure Architecture Center reference architectureArchitecture → Components → topic sections → Considerations by five Well-Architected pillars → Contributors; ms.date visible; page source in GitHub.Works: dated, git-backed, pillar structure mirrors AWS. Does not: no deploy button or cost table on the page fetched.https://learn.microsoft.com/en-us/azure/architecture/ai-ml/architecture/baseline-microsoft-foundry-landing-zone (ms.date 2026-06-17)PrimaryHigh

G. Per-catalog-item recommendation (content-structure view)​

Legend — Link: point the chapter at existing AWS content; Fork: compose from an existing repo/Guidance and adapt; Build: nothing demonstrable exists at use-case level, new work has demonstration value. Angle 1 supplies the repo-coverage view; the comparator reconciles.

ItemTierRecommendationRationale (with sources above)
F0 HIPAA-ready landing zoneT1Link (organisation layer) + Build (single-account layer)LZA Solution + LZA-for-Healthcare config (C3, C-map) is the authoritative org-level story and has the best page anatomy on AWS (version, deploy time, cost table). But it requires Control Tower Management/Audit/LogArchive, contradicting the brief's default that F0 works in a fresh single account, and no single-account HIPAA-baseline workshop exists (B7). Build the single-account CDK baseline; the chapter links LZA as "the enterprise extension" and uses the Healthcare Lens (C7) for framing. Copy the Solution cost-table shape (C4).
U1 Patient portal + mobileT1BuildNo workshop or Guidance shows portal + iOS/Android + Cognito + HealthLake end to end (B7). Link SMART-on-FHIR workshop (B3) for the OAuth/FHIR sub-topic and Amplify workshops (B6) for platform basics.
T2ForkHCLS Agents Toolkit / Strands+AgentCore HCLS workshop (B5) and the official AgentCore workshops (B6) give agent scaffolding; the patient-facing "explain my lab result" assistant with Guardrails and FHIR tools is new.
T3Link for mechanics, Build the modelSageMaker MLOps / SageMaker AI workshops (B6) teach Pipelines/Registry; the no-show model on the app's own data is new.
U2 Remote patient monitoringT1–T3BuildNothing healthcare-specific exists on Workshop Studio or in Guidance for IoT → Flink → Timestream → SageMaker → Greengrass (B7). Link Managed Flink and IoT Device Management workshops (B6) as component primers. Highest demonstration value in the catalog.
U3 Ambient clinical documentationT1–T2ForkGuidance "Identifying Diagnosis Codes from Clinical Notes" (C-map: CDK Python, MIT-0, HealthScribe → Comprehend Medical → Bedrock, cost table) covers capture-to-codes. Build the Step Functions review workflow, clinician approval UI and HealthLake DocumentReference write-back. Link B2 for the documents-to-FHIR primer.
T3BuildNo public note-quality classifier / evaluation harness found.
U4 Intelligent document intakeT1–T2Link + ForkBest-covered item: Guidance for IDP on AWS is already AgentCore-based with Textract and an ECS dashboard (C-map), and two official workshops exist ("IDP with AWS AI Services", "Document Processing with Bedrock Data Automation", B6). Link the workshops as the learning layer; fork the Guidance sample for the healthcare specifics (Comprehend Medical PHI, Macie on the intake bucket, prior-auth packet). Lowest new-build value.
T3BuildClassifier / denial-risk model on intake history not found publicly.
U5 Population health platformT1ForkMulti-Modal Data Analysis Guidance (CloudFormation, MIT-0) + Patient Entity Resolution Guidance + HealthLake Workshop (B1, repo archived 2026-02-04) cover HealthLake → Lake Formation → Athena → dashboard. Build the S3 Tables/Iceberg landing from U2, Amazon Quick (pages still say QuickSight) and the de-identification pipeline.
T2BuildNatural-language analytics over the lake not found in Guidance or workshops.
T3ForkMulti-Modal Guidance already shows Feature Store → AutoGluon → endpoint; re-target to readmission risk.
U6 Contact center (optional)T1–T2Link"Getting started with Amazon Connect" workshop exists (B6); no healthcare Connect workshop or Guidance found. Keep as a link-only chapter unless angle 1 finds a Guidance.
P0 Portal—Build, on existing contractsDo not rebuild content that exists as an Official workshop — link it (B6). For chapters, adopt the Guidance page anatomy (C2) plus the Solution header (version, released, deploy time, estimated cost — C3/C4) and the serverless-patterns README contract (D3). Make each use-case repo self-describing: README in the Guidance contract (D4), ADRs in MADR 4 under docs/decisions/ (E1–E2), a contentspec.yaml so any chapter can be published as a Workshop Studio event (A4–A6), and generated API docs for CDK constructs (E3). Aggregate at build time in the TechDocs/Antora manner (E4–E6); the portal itself holds navigation, not prose. Add the Guidance usage disclaimer (C5) to every forked chapter.

Gaps​

  • Workshop module lists: every Workshop Studio page is client-rendered; module structure, IaC, level and last-updated dates for B1–B6 could not be read. Coverage judgements are based on AWS-published descriptions and backing repos. Someone with a browser should open B2, B3 and B5 and confirm modules before the portal links them.
  • Guidance for Patient Outcome Prediction on AWS: appears in search results but docs.aws.amazon.com/solutions/patient-outcome-prediction-on-aws/ returned 404; status unknown.
  • No public Guidance README template repo was found; D4 is inferred from three repos.
  • Builder Center workshop count and filters could not be read from the page (client-rendered); the 2025-11-18 What's New post is the source.
  • Google Jump Start Solutions current inventory is behind the console; only the 2023 launch set is documented publicly.
  • Azure "Deploy this scenario" sections were not present on the page fetched; not claimed.
  • Not found anywhere: an RPM/IoT healthcare workshop, a single-account HIPAA baseline workshop, HealthScribe/HealthImaging workshops, a Connect healthcare workshop, a patient-portal-plus-mobile workshop.
  • Practitioner post "Document your AWS CDK constructs like a pro" (Medium) returned 403 and is not used.

Sources (retrieved 2026-09-04 unless dated)​

Primary

Practitioner