Internal knowledge assistants
Answers from Confluence, SharePoint and your records, with citations and source links.
Generative AI on AWS
AI pilots stall on governance, cost spirals, and team alignment. We get yours to ship: RAG pipelines, agents, and Bedrock applications hardened with cost guardrails, evaluations, and security controls from sprint one.
Last updated:
Bedrock, SageMaker, AgentCore, Quick Suite and Amazon Q overlap on paper. Choose your job and see where we would start.
Serverless foundation-model APIs, Knowledge Bases and Guardrails. The fastest path to production.
How we deliver itAgents Classic is in maintenance. Runtime, Harness and Gateway are the path for net-new builds.
How we deliver itThe full ML lifecycle for churn, fraud or forecast models: training, tuning, hosting and monitoring.
How we deliver itBedrock for managed simplicity. SageMaker when you need control over the training run.
How we deliver itThe net-new path after Q Business entered maintenance on 30 July 2026, with ACL-aware Quick Index. Formerly Amazon Quick.
How we deliver itIDE-native, with the /dev agent, security scans and code transformation.
How we deliver itNatural-language BI. Amazon QuickSight is now AWS Quick Sight; datasets and pricing are unchanged.
How we deliver itOpen-source weights with customer-managed inference, for workloads that cannot call an API model.
How we deliver itNative vector storage in S3, about 10× cheaper than OpenSearch for cold archives.
How we deliver itEach one runs in your AWS account, on your data, with guardrails and a budget before the first user.
Answers from Confluence, SharePoint and your records, with citations and source links.
Read, extract, classify and summarize contracts, records and filings. Textract, Bedrock, S3, Lambda.
Handles common questions, escalates the rest, and drafts replies grounded in your docs.
Review, boilerplate and tests in your CI/CD, on Amazon Q Developer or Bedrock.
SageMaker forecasts with a plain-language Bedrock explanation for people who do not read statistics.

Every component in your VPC. No data leaves your AWS environment.
IAM decides which roles and services can invoke which models.
Every invocation logged to CloudTrail with the user and request context.
Bedrock Guardrails for content filters, PII protection and topic limits.
Input validation and a hardened system prompt.
Per-model and per-user invocation budgets, with alerts.
Cuts input token cost 70–90% and latency 60–85% when the system prompt or context repeats.
Send each task to the smallest model that meets the accuracy bar.
Per-model and per-user invocation budgets with alerts, set on day one.
List rates, us-east-1, checked November 11, 2026. Price your own workload
2,000 tokens in · 500 out
A prototype on your real data by week three. Auth, observability, budgets and adversarial testing are in before launch.
Generative AI on AWS is the set of managed services that lets organizations build, deploy, and operate large language model (LLM) and foundation-model applications without managing GPU infrastructure. The stack centers on Amazon Bedrock for foundation models (Claude Fable 5.2 for long-horizon Covered Model jobs (Fable 5.1 remains the prior pin), Claude Opus 5.5 with ZDR default and 1M context, Claude Opus 5 as the prior Opus pin, Claude Sonnet 5, Claude Haiku 5.5 (Haiku 4.5 remains the prior pin), Amazon Nova 2 Lite, OpenAI GPT-6 Astra / Sol / Luna with GPT-5.6 as the prior pins, Daybreak Blue and Daybreak Red (November 10, 2026 — enrollment-gated; bedrock-runtime US and Global CRIS; not the general GPT-5.6 Sol pin), xAI Grok 4.6 with US Geo / Global CRIS, Grok 4.3, Llama, Mistral Large 3, Cohere, and marketplace models including GLM 5.3 (October 5, 2026 — eligible customers, US/Global CRIS, 1M context; GLM 5 remains the prior pin), MiniMax M2.5, and Kimi K3.1 Pro (November 6, 2026 — Highspeed; 1M context; Global CRIS global.moonshotai.kimi-k3.1 at $4 / $20 per 1M; Kimi K3, September 18, 2026, remains the prior pin)), Amazon SageMaker AI / Unified Studio for custom training and hosting, and Amazon Q / Quick Suite for turnkey assistants — all integrated with VPC endpoints, IAM, KMS, and CloudTrail for data residency and audit-ready compliance.
See how we’ve deployed production GenAI systems that deliver measurable business outcomes:
AWS provides the most complete enterprise-ready stack for generative AI — from managed model access to data pipelines, vector search, orchestration, and guardrails.
| If your use case is… | Choose | Why |
|---|---|---|
| Customer-facing chatbot, RAG over docs, summarization, classification | Amazon Bedrock | Serverless foundation-model APIs, Knowledge Bases, Guardrails — fastest path to production |
| AI agent that calls tools/APIs across multiple steps | Bedrock AgentCore | Agents Classic in maintenance — Runtime, Harness, Gateway for net-new builds |
| Custom-trained model on your proprietary data (churn, fraud, forecast) | Amazon SageMaker | Full ML lifecycle: training, tuning, hosting, monitoring |
| Fine-tuning a foundation model on domain data | SageMaker JumpStart or Bedrock fine-tuning | Bedrock for managed simplicity; SageMaker for control |
| Internal employee Q&A across SharePoint/Confluence/Salesforce | AWS Quick | Net-new path after Q Business maintenance (July 30, 2026); ACL-aware Quick Index |
| AI coding assistant in IDE/CLI | Amazon Q Developer | IDE-native, /dev agent, security scans, code transformation |
| Conversational analytics on dashboards | AWS Quick Sight | Natural-language BI. Amazon QuickSight is now AWS Quick Sight; datasets and pricing are unchanged |
| Air-gapped, regulated workload that cannot use API-based models | SageMaker (private VPC) with open-source weights | Full data isolation, customer-managed inference |
| Knowledge base over very large vector corpus (100M+ vectors) | S3 Vectors + Bedrock | Native S3 vector storage, ~10× cost reduction vs OpenSearch for cold archives |
The key services:
Amazon Bedrock is the starting point for most enterprise GenAI on AWS. It provides serverless access to foundation models from Anthropic (Claude), Meta (Llama), Mistral, Cohere, OpenAI, xAI, and Amazon (Nova, plus Titan embeddings) through a single API — without provisioning or managing any model infrastructure.
Bedrock includes:
SageMaker is the platform for teams that need to go beyond off-the-shelf foundation models:
Amazon Q extends generative AI capabilities to specific AWS use cases:
Enterprise chatbots that answer questions from your internal documentation, Confluence, SharePoint, Slack archives, and database records. Powered by Bedrock Knowledge Bases with Kendra or OpenSearch as the retrieval layer.
Example: A healthcare company’s internal assistant answering clinical protocol questions from 50,000 pages of documentation — with citations and source links, deployed with HIPAA-compliant architecture on Bedrock.
Applications that read, extract, classify, and summarize large volumes of documents — contracts, medical records, financial reports, regulatory filings.
Components: Textract for extraction, Bedrock Claude for summarization and classification, S3 for storage, Lambda for orchestration.
Example: A fintech operations team automating SOC 2 evidence collection from 12,000 quarterly documents — Textract → Bedrock classification → S3 evidence locker, audit log every step. Replaced 3 FTE-weeks of manual review per quarter.
Customer-facing support automation that handles common inquiries, escalates complex cases, and provides agents with suggested responses — grounded in your product documentation and customer history.
Developer tooling that accelerates code review, generates boilerplate, writes tests, and explains complex codebases — integrated with your CI/CD pipeline and built on Amazon Q Developer or Bedrock.
Combining SageMaker for predictive models with Bedrock for natural language explanation of predictions — enabling business users to understand model outputs without data science expertise.
Example: A retail operations team running a SageMaker demand-forecast model for 800 SKUs, with Bedrock generating plain-language explanations of week-over-week shifts (“inventory at risk at 12 stores due to promo cannibalization”) for store managers who do not read statistical output.
Enterprise generative AI requires more than just good prompts:
For deep-dive guidance on specific Bedrock capabilities, see our Amazon Bedrock Consulting service. For machine learning beyond foundation models, see AWS SageMaker Services.
Generative AI on AWS refers to building LLM-powered applications using AWS managed services — primarily Amazon Bedrock (for accessing foundation models from Anthropic, Meta, Mistral, and Amazon without managing infrastructure) and Amazon SageMaker (for training, fine-tuning, and hosting custom models). AWS provides a complete stack for enterprise generative AI: managed model access, vector databases (OpenSearch, RDS pgvector), retrieval pipelines, orchestration (Step Functions, Bedrock AgentCore), guardrails, and security controls that keep your data within your AWS environment. Workforce AI net-new buyers after July 30, 2026 should evaluate AWS Quick instead of Q Business.
Direct third-party LLM APIs (OpenAI, Anthropic API) send your data to the model provider. For enterprise applications — especially in healthcare, fintech, or legal — this creates data residency, privacy, and compliance issues. Amazon Bedrock provides access to the same underlying models (including Claude from Anthropic) through an API that stays within your AWS environment. Your data never leaves your AWS account. You also get consolidated billing, IAM-based access control, CloudTrail logging of all model invocations, and integration with your existing VPCs and security controls.
RAG (Retrieval-Augmented Generation) is an architecture where a foundation model is given relevant context retrieved from your private knowledge base before generating a response. Without RAG, the model only knows what was in its training data — it cannot answer questions about your products, policies, customer history, or any other proprietary information. With RAG, you retrieve relevant documents from your knowledge base and include them in the model prompt, enabling accurate, grounded responses based on your data. Most enterprise GenAI applications — internal assistants, customer support bots, document Q&A — require RAG.
A focused prototype (demonstrating core functionality with real data) typically takes 2–3 weeks. Production-hardening — adding error handling, observability, guardrails, cost controls, and user authentication — adds another 4–6 weeks. More complex systems with fine-tuning, multiple agents, or integration with many data sources take longer. We recommend starting with a focused prototype on the highest-value use case, validating it with real users, then expanding.
The right model depends on your use case, latency requirements, and cost tolerance. Claude Opus 5.5 (September 22, 2026 — ZDR default on Bedrock, adaptive thinking always on, 1M context) is the current Opus workhorse; Claude Opus 5 (July 24, 2026) stays the prior pin until you benchmark it. Claude Sonnet 5.5 (September 28, 2026 — 1M context, adaptive thinking on by default, also in AWS GovCloud (US)) is the balanced agentic default; Claude Sonnet 5 (June 30, 2026) stays the prior pin until you benchmark 5.5. Claude Haiku 5.5 (October 7, 2026 — 1M context, model ID anthropic.claude-haiku-5-5, Global CRIS global.anthropic.claude-haiku-5-5, Marketplace-billed) is the current volume Haiku; Claude Haiku 4.5 (October 16, 2025) stays the prior pin. Claude Fable 5.2 (November 9, 2026) is the current Mythos-class GA path for multi-hour autonomous jobs. It is a Covered Model: set data retention to aws_review. The abuse-detection page retains all Fable 5.2 traffic for up to 30 days. Eligible Enterprise Frontier Safeguards customers get zero data retention through June 30, 2027. Fable 5.1 (September 1, 2026) remains the prior pin. OpenAI GPT-6.2 Astra and Sol were announced November 17, 2026 and have no user-guide model card or dollar rate as of November 18, 2026 (pricing page: Astra Ultrafast is 3× Standard through February 28, 2027, then 6×). GPT-6 Luna, GPT-6.1 Sol, and GPT-6 Astra remain the priced lanes for volume, recurring complex work, and the hardest end-to-end jobs (GPT-6.1 Sol GA September 29, 2026 — OpenAI reports near-Astra results at Sol pricing, 1M context; Ultrafast October 8, 2026 at 6× Standard; Global CRIS global.openai.gpt-6.1-sol on the model card; GPT-6 Sol and Luna GA September 22, 2026, up to 1M context, with GPT-6 Sol as the older Sol pin; Astra GA September 8, 2026, priced prior Astra pin). GPT-5.6 Luna/Terra/Sol remain prior pins (Luna −80% / Terra −20% July 30, 2026; 1M context August 3, 2026). Amazon Nova 2 Lite (December 2, 2025, 1M context) is the current everyday Nova; Nova Micro remains the cheapest published text lane. Grok 4.7 (September 28, 2026) is the current Converse-native xAI model — 500K context, four reasoning-effort levels, US Geo and Global CRIS; Grok 4.6 is the prior pin and Grok 4.3 remains the cheaper Mantle-only long-context option. We benchmark candidates against your data before committing.
Source: Claude Sonnet 5.5 on AWS
Source: Grok 4.7 on Amazon Bedrock
Source: Claude Fable 5.2 on AWS
Source: Claude Opus 5.5 on AWS
Source: GPT-6.2 Astra and Sol on Amazon Bedrock
Source: GPT-6.1 Sol on Amazon Bedrock
Source: GPT-6 Sol and Luna on Amazon Bedrock
Source: Claude Opus 5 on AWS
Source: Claude Haiku 5.5 on AWS
Security is built into every GenAI engagement from day one. We deploy all components within your VPC — no data traverses the public internet. Amazon Bedrock model providers never see your data. We implement Bedrock Guardrails to prevent PII leakage, prompt injection, and harmful content. All model invocations are logged to CloudTrail. IAM policies restrict model access to authorized roles. For regulated industries (healthcare, fintech), we ensure the architecture meets applicable compliance requirements (HIPAA, SOC 2, PCI DSS) before deployment.
Bedrock gives you managed access to foundation models via API; SageMaker is the platform for training, fine-tuning, and hosting custom models. Most enterprise GenAI uses both — Bedrock for the LLM, SageMaker for proprietary embeddings or predictive models. For a side-by-side feature matrix and pricing comparison, see our [Amazon Bedrock service page](/services/aws-bedrock/).
Yes — our GenAI Discovery Call is specifically designed for this. We will assess your use case against four criteria: data availability (do you have the private data to power the application), business value (is the expected ROI clear), technical feasibility (can the use case be reliably solved with current LLM capabilities), and organizational readiness (does your team have the context to validate and iterate on the system). Not every use case is a good fit for GenAI, and we will tell you honestly if yours is not.
We implement hard budget limits at the AWS Bedrock account level, per-feature token budgets, and cost monitoring dashboards from sprint one. Most clients know their per-query cost within two weeks of going live — before they have committed to scale. Automated alerts trigger before spend thresholds are reached, not after.
Amazon Nova is Amazon's own foundation model family available on Bedrock: Nova Micro (text-only, ultra-low latency, ~$0.04/1M input tokens), Nova Lite (multimodal — text, image, and video input, strong price/performance balance), and Nova Pro (highest Nova capability for complex reasoning and vision tasks). Nova Micro costs far less per token than Claude Sonnet 5.5. For high-volume tasks — classification, extraction, summarization, routing, and structured output generation — Nova delivers strong results at a fraction of the Claude cost. We benchmark both models against your specific use case and data before recommending, and many production systems we build use Nova for volume workloads and Claude Sonnet 5.5 for reasoning-intensive tasks.
We establish a golden dataset during development — a curated set of test cases drawn from your real user queries — and run automated evaluations against it on every deployment. This gives you a quality number, not just a demo. We also set up hallucination scoring and output validation so your team can monitor quality in production, not just at launch.
Yes — this is the most common engagement we run. We start with a 1-week diagnostic: review your current architecture, retrieval quality, evaluation gap, cost trajectory, and security posture. You get a written punch list of what is blocking production with effort estimates against each item. From there we either embed with your team to ship the fixes (typical 4–6 weeks) or hand back the punch list for your team to execute. No vendor lock-in.
For regulated workloads we layer three controls: Bedrock Guardrails for content and PII filtering, Bedrock Automated Reasoning Checks for math and logic validation against a defined policy, and golden-dataset evaluations on every deploy. For high-stakes outputs we add human-in-the-loop review and citation requirements — the model must surface the source document for every claim. We have shipped this pattern under HIPAA and SOC 2 audit; the architecture pattern is documented in our [HIPAA-compliant AI on Bedrock guide](/blog/hipaa-compliant-ai-aws-bedrock/).
Two-week migration is typical for most applications. The work: switch the SDK from OpenAI to Bedrock (Anthropic Claude is the closest behavioral match for GPT-4-class workloads, Nova for cheaper-than-GPT-4o-mini volume tasks), rewrite prompts where needed (Claude responds slightly differently to system instructions), wire VPC endpoints for data residency, and run an evaluation against a golden dataset to confirm parity. We document the cost delta — typically 30–60% lower for comparable quality once Prompt Caching is enabled.
Knowledge transfer is built into every engagement, not an afterthought. Your engineers pair on every PR, our weekly demos are recorded with architecture rationale, the runbook is written in your wiki (not ours), and we run a 2-hour handoff session before invoice close. We have references from clients who ran their Bedrock systems in production for 12+ months without re-engaging us — that is the outcome we optimize for, not retainer hours.
We have heard that story often: impressive slides, then ghosting when it was time to build — or a handoff of spaghetti with no tests, hardcoded keys, and no docs. Every engagement here is fixed scope and locked price with production deliverables: evals, cost guardrails, observability, and code your team can read. We embed with your engineers; we do not disappear after the deck. If a prior engagement left you in pilot purgatory, our 1-week diagnostic produces a punch list you can execute with or without us.
We build with minimal abstraction — explicit prompts, control loops, and Bedrock/SageMaker APIs — so you can debug, monitor, and change behavior without fighting a framework. Orchestration stays in code you own (Step Functions, AgentCore, or a thin application layer). Frameworks are fine for demos; production needs rails you can inspect. Your team should be able to ship a prompt change without waiting on us.
We have shipped 20+ GenAI systems on AWS with cost guardrails, evaluations, and audit-ready security baked in. Tell us your use case and we will map a delivery path — fixed scope, locked price.
Photograph: “This is a card puncher, an integral part of the tabulation system used by the United States Census Bureau”, U.S. National Archives, public domain, via Wikimedia Commons.
We use cookies and similar technologies to analyze site traffic, personalize content, and provide social media features. By clicking “Accept,” you consent to our use of cookies. You can adjust your preferences at any time.