# AWS GenAI Catalog: 23 Open Reusable Assets From AgentCore FAST to RAG

> Source: <https://explainx.ai/blog/aws-genai-23-open-source-reusable-assets-agentcore-fast-november-2026?utm_source=rss&utm_medium=feed&utm_campaign=blog>
> Published: 2026-11-11 00:00:00+00:00

**Amazon Web Services published a catalog of 23 open-source reusable generative AI assets on November 11, 2026**, arguing that teams waste months rebuilding the same **RAG pipelines, document processors, and agent scaffolds**. The post comes from the **AWS Generative AI Innovation Center**, now folded into **AWS Frontier AI Engineering & Services**, and it cites **DoorDash**, **Lyft**, and **Ricoh** outcomes alongside newer **AgentCore** starters such as **FAST**.

## TL;DR

| Theme | AWS claim (Nov 11, 2026 blog) | 
|---|---|
| Catalog size | **23** open assets with deployment guides | 
| Problem framed | No single source of truth, no quality signal, no reuse culture | 
| Contact center | Shared **Contact Center GenAI Agent** for voice + text RAG | 
| IDP | **GenAI Intelligent Document Processing** accelerator (serverless) | 
| Agentic newness | **FAST** full-stack AgentCore template;**Agentic Chatbot Accelerator** | 
| Cited wins | **50x** testing capacity (DoorDash case study);**90%+** hour cuts (Ricoh) | 

## Why AWS is packaging reuse now

The [AWS Machine Learning Blog post](https://aws.amazon.com/blogs/machine-learning/accelerating-generative-ai-delivery-with-reusable-assets/?ref=explainx) names three drivers of redundant GenAI engineering:

1. **Scattered artifacts** across repos, wikis, and drives.
2. **No trust signal** for production readiness or security review status.
3. **Informal sharing** so every team rebuilds the same middleware.

AWS argues even **AI-generated code** still needs **hardening, security review, load testing, and maintenance**. These assets claim to arrive **pre-validated** so builders focus on **domain prompts and business rules**.

That message aligns with explainx.ai coverage of [AWS Quick Skills for agents](https://explainx.ai/blog/aws-quick-skills-agents-catalog-build-guide-2026), [UAE agent evaluation frameworks](https://explainx.ai/blog/aws-uaef-universal-agent-evaluation-framework-2026), and [Bedrock bidirectional streaming metering](https://explainx.ai/blog/aws-sagemaker-bidirectional-streaming-usage-metering-deepgram-2026): Amazon wants **repeatable agent plumbing**, not one-off demos.

## What counts as a reusable asset

AWS defines an asset as a **production-grade, composable building block** for a discrete GenAI capability—not a snippet demo. Attributes include:

- **Security review** before publication.
- **Deployment guides** and instrumentation for adoption tracking.
- **Lifecycle maintenance** by Frontier AI Engineering.

Examples span **RAG components**, **document ingestion**, **agent scaffolding**, **evaluation frameworks**, and **prompt management patterns** tested in customer engagements.

## Customer stories AWS highlights

### Contact Center GenAI Agent (DoorDash and Lyft)

AWS points to a shared **Contact Center GenAI Agent** GitHub asset:

- **DoorDash** built a voice self-service center handling**100,000+ calls/day** at**2.5-second** latency, with**50x** testing-capacity growth and**50%** faster development on Bedrock, reaching live testing in**two months** (per AWS case study links in the post).
- **Lyft** reused the same asset for rider and driver agentic flows.

Architecture pieces include **Amazon Connect**, **Amazon Bedrock Knowledge Bases**, hybrid search, metadata filters, and **Bedrock Guardrails** for hallucination and topic boundaries.

### GenAI IDP Accelerator (Ricoh)

For healthcare payer document floods, AWS cites Ricoh building on the **Accelerated Intelligent Document Processing on AWS** asset:

- **7x** throughput (10,000–70,000 documents monthly cited range in post).
- Engineering hours per deployment **80 → under 5** .
- Onboarding **4–6 weeks → 2–3 days** .
- **1,000 documents in minutes** during spikes;**1,900** potential annual person-hours saved (vendor case study numbers).

## New agentic assets: FAST and chatbot accelerator

Two **November-era** launches target **agentic full-stack** speed:

| Asset | What AWS says it ships | 
|---|---|
| **Fullstack AgentCore Solution Template (FAST)** | React UI + **Bedrock AgentCore** backend, deploy**under 30 minutes** with IaC; Cognito auth; hooks for memory, Gateway, Code Interpreter, observability | 
| **Agentic Chatbot Accelerator** | CDK deployable web app on **Strands Agents** + AgentCore with auth/hosting patterns | 

FAST is explicitly aimed at teams that want a **reference architecture** they can swap components on (identity provider, frontend framework, agent framework).

For readers comparing clouds, contrast [Microsoft agent substrates on Kubernetes](https://explainx.ai/blog/nvidia-agent-substrate-kubernetes-cncf-dynamo-2026) and [Anthropic multi-agent bench work](https://explainx.ai/blog/anthropic-worse-together-multi-user-multi-agent-mamubench-2026): AWS is selling **opinionated Bedrock-centric templates**, not raw VMs.

## Catalog map: 23 assets by category

The blog ends with a **full list**. Grouped for navigation:

### Document processing and extraction

- GenAI Intelligent Document Processing (GenAIDP)
- Multi-lingual Document Processor (MDP)
- Intelligent Document Processing with Generative AI
- Extracting Information From Complex Documents (workshop)
- Semi-Structured Documents Automatic Pre-Labeling Tool

### Contact center and voice

- Contact Center GenAI Agent
- Live Call Analytics with Agent Assist (LCA)
- Contact Center: Post Call Analytics (PCA)
- Live Meeting Assistant (LMA)
- Recorded Voice Insight Extraction Webapp (ReVIEW)

### Agentic AI and chatbots

- **FAST** (AgentCore full stack)
- **Agentic Chatbot Accelerator**
- Fashion Assistant Agent (Titan + AgentCore)
- Natural Language Database Agent (LangGraph)

### RAG and knowledge bases

- Deploy Amazon Bedrock Knowledge Bases using Terraform
- Leveraging the User to Improve Agents in RAG Use Cases
- Reranker Fine-Tuning and Deployment (BGE)
- Durable Semantic Caching in Amazon MemoryDB

### Development and migration

- C to Java Code Conversion agentic workflow
- OpenAI Migration Framework
- Fine-tuning ModernBERT for Intent Classification

### Infrastructure and operations

- Bedrock Logging Automation
- Data Analyst BI for non-experts

Each item links to a **GitHub README** with prerequisites; the post walks a **Contact Center** deployment in under an hour for knowledgeable AWS admins.

## Walkthrough pattern AWS recommends

The blog's sample deployment for **Contact Center GenAI Agent** follows four steps:

1. Clone repo and install dependencies.
2. Deploy **Knowledge Base** and**RAG** CloudFormation stacks.
3. Integrate **Amazon Connect** contact flows from the repo.
4. Validate with bundled **Jupyter notebooks** and optional**QuickSight** analytics dashboard.

Cleanup section reminds teams to delete stacks to avoid **SPICE** and Connect charges—small but real FinOps detail.

**Claimed time saved:** **4–6 weeks** versus greenfield build, with your team focusing on **KB curation and domain prompts**.

## How this compares to DIY agent repos

GitHub trend pieces like [Herdr agent terminal runtime](https://explainx.ai/blog/herdr-agent-terminal-runtime-coding-agents-github-trending-2026) and [shadcn skill audits](https://explainx.ai/blog/shadcn-improve-agent-skill-audit-expensive-execute-cheap-2026) chase **developer ergonomics**. AWS assets chase **enterprise compliance**: Guardrails, Connect integration, and **pre-written CDK**.

Neither replaces the other. A startup might prototype in Herdr, then cherry-pick **AWS FAST** when a Fortune 500 procurement asks for **Cognito + CloudFormation** evidence.

## Responsible AI hooks

The contact-center walkthrough stresses **Bedrock Guardrails** for **hallucination detection**, **content filters**, and **topic boundaries** on day one. That matches [England OfS coursework grading safeguards](https://explainx.ai/blog/england-ofs-ai-coursework-grading-secure-assessment-november-2026) and broader **evaluation** pushes in [Amazon Bedrock AgentCore evaluation playbook](https://explainx.ai/blog/amazon-bedrock-agentcore-evaluation-playbook-deepeval-autoeval-guide-2026).

## What to do this week

1. **Pick one asset** matching your bottleneck (IDP vs contact center vs FAST).
2. **Deploy in a sandbox account** using the blog's cleanup section as your budget guardrail.
3. **Fork prompts** , not infrastructure—keep upstream security patches flowing.
4. Map **AgentCore** pieces to your existing[Bedrock tokenomics lake](https://explainx.ai/blog/amazon-bedrock-tokenomics-data-lake-finops-2026) so reuse shows up in**unit economics** , not just sprint velocity.
5. If you are mid **OpenAI migration** , read the bundled**OpenAI Migration Framework** asset alongside[OpenAI discount poaching reports](https://explainx.ai/blog/openai-discounts-up-to-90-percent-poach-anthropic-customers-rippling-replit-datacamp-claimed-vs-verified-2026) for negotiation context only—not as legal advice.

## Limitations and honest caveats

- **Case study metrics** are**customer-specific** ; your latency and accuracy will differ with audio quality and KB hygiene.
- **23 assets** does not mean**23 one-click SaaS products** ; most still require**AWS literacy** and ongoing**stack ownership** .
- Assets complement but do not replace [UAEF-style evaluation harnesses](https://explainx.ai/blog/aws-uaef-universal-agent-evaluation-framework-2026) when you ship agents to regulated users.

## FinOps: what saved hours do not automatically save

DoorDash and Ricoh numbers are **engineering-hour** stories. Finance leaders still need **token and connect-minute budgets**:

- **Amazon Connect** voice minutes and**Lex** turns continue after the asset deploys.
- **Bedrock** charges per**input and output token** on knowledge-base retrieval and generation paths inside the contact-center flows.
- **QuickSight SPICE** datasets from the sample analytics dashboard add**storage and refresh** lines.

Pair asset adoption with [Bedrock tokenomics lakes](https://explainx.ai/blog/amazon-bedrock-tokenomics-data-lake-finops-2026) so leadership sees **unit cost per resolved call**, not only **time-to-first-demo**.

## Security review expectations

AWS claims assets are **security-reviewed before publication**. Your enterprise may still require **internal pen tests** on:

- **IAM roles** created by the CDK stacks
- **Knowledge Base data source** permissions
- **Guardrail topic lists** that might block legitimate customer intents in your domain

Treat AWS review as **acceleration**, not **sign-off**. The same discipline applies when you import [shadcn agent skill audits](https://explainx.ai/blog/shadcn-improve-agent-skill-audit-expensive-execute-cheap-2026) into CI.

## When to pick FAST versus Agentic Chatbot Accelerator

| Need | Start here | 
|---|---|
| Full **React** product surface + AgentCore backend in days | **FAST** | 
| **Chat-only** agent with CDK deploy patterns | **Agentic Chatbot Accelerator** | 
| **Voice + text** support center | **Contact Center GenAI Agent** | 
| **Document back office** | **GenAI IDP** accelerator | 

FAST is ideal for **hack week → pilot** transitions. Contact-center assets fit **existing Connect estates**. Do not deploy voice assets if your bottleneck is **PDF extraction**—start IDP instead.

## Open source maintenance contract with yourself

Each repo includes **issues tabs** and **version tags**, but **23 repos** means **23 dependency alert feeds**. Assign an **owner service** in your org chart, or repos rot when upstream **Bedrock API shapes** shift.

If you lack staff, pick **one** asset depth-first—Ricoh-like IDP or DoorDash-like voice—rather than cloning all templates into separate forks that never merge security patches.

## Related reading

**Sources:** [AWS ML Blog (Nov 11, 2026)](https://aws.amazon.com/blogs/machine-learning/accelerating-generative-ai-delivery-with-reusable-assets/?ref=explainx) · [DoorDash case study (linked from AWS)](https://aws.amazon.com/solutions/case-studies/doordash-case-study/?ref=explainx) · [Ricoh IDP case study (linked from AWS)](https://aws.amazon.com/blogs/machine-learning/how-ricoh-built-a-scalable-intelligent-document-processing-solution-on-aws/?ref=explainx)