All Services

AI / ML

Amazon Q

Amazon Q is a family of generative-AI assistants; this guide focuses on Amazon Q Business for permission-aware enterprise answers and Amazon Q Developer for software-development and AWS assistance.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with Amazon Q.

Amazon Q pricing and cost programs

Pricing model: Subscription and usage tiers

On-Demand
Service-specific
Reserved Instances or reserved capacity
Not applicable
Savings Plans
Not applicable
Spot
Not applicable

Billing dimensions: User subscriptions · Index units · Transformation or agent usage

Programs and modes: Q Business subscriptions · Q Developer tiers · Service-specific usage

Amazon Q product editions use distinct subscription and metered dimensions.

Free Tier: Service-specific — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement Amazon Q?

  • Provides managed conversational experiences for enterprise knowledge and developer workflows without building a retrieval and chat stack from individual components.
  • Q Business can index supported source access-control information so responses can respect end-user document permissions.
  • Q Developer assists with software and AWS tasks in supported development environments and consoles, reducing time spent locating documentation and drafting routine code.

How to implement Amazon Q

  1. Choose Q Business, Q Developer, or another named Q product based on the user and task; validate that product's current Region, identity, connector, data, and licensing capabilities.
  2. For Q Business, configure IAM Identity Center or the supported identity path, create the application and index, store connector credentials in Secrets Manager, and ingest only approved sources with their ACLs.
  3. Test representative users, denied documents, stale memberships, adversarial prompts, citations, answer quality, and offboarding; publish through the supported web experience or application integration with monitoring and feedback.

Amazon Q best practices

  • Never disable source ACL handling casually: AWS warns that content ingested without ACLs can become available to every application end user.
  • Use least-privilege connector and administrator roles, minimize indexed sensitive data, rotate connector secrets, and promptly resynchronize identity and source permission changes.
  • Treat generated answers and code as suggestions, require source review or testing for consequential work, and monitor feedback, denied access, ingestion failures, and usage cost.

Amazon Q use cases and server impact

  • Permission-aware enterprise knowledge search
  • Employee self-service assistants
  • Developer coding and AWS guidance

Replaces much of a custom enterprise-chat or coding-assistant service, but source authorization, content quality, identity lifecycle, output review, and exact product governance remain customer work.

Official implementation resources

Commonly paired AWS services