{"id":249,"date":"2026-04-13T08:49:29","date_gmt":"2026-04-13T08:49:29","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/aws-amazon-q-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-machine-learning-ml-and-artificial-intelligence-ai\/"},"modified":"2026-04-13T08:49:29","modified_gmt":"2026-04-13T08:49:29","slug":"aws-amazon-q-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-machine-learning-ml-and-artificial-intelligence-ai","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/aws-amazon-q-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-machine-learning-ml-and-artificial-intelligence-ai\/","title":{"rendered":"AWS Amazon Q Tutorial: Architecture, Pricing, Use Cases, and Hands-On Guide for Machine Learning (ML) and Artificial Intelligence (AI)"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Category<\/h2>\n\n\n\n<p>Machine Learning (ML) and Artificial Intelligence (AI)<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introduction<\/h2>\n\n\n\n<p>Amazon Q is AWS\u2019s generative AI assistant designed to help people work faster with AWS, software development tasks, and (depending on the Amazon Q offering) enterprise knowledge and business data. It\u2019s part of AWS\u2019s broader Machine Learning (ML) and Artificial Intelligence (AI) portfolio, but it\u2019s delivered as an end-user assistant rather than a \u201cbuild-your-own-model\u201d platform.<\/p>\n\n\n\n<p>In simple terms: <strong>Amazon Q is a chat- and assistant-style experience that helps you get answers, generate or improve code, and complete tasks using natural language<\/strong>, with security and identity controls appropriate for organizations.<\/p>\n\n\n\n<p>Technically: Amazon Q is a set of AWS-managed AI assistant capabilities (for example, <strong>Amazon Q Developer<\/strong> for developers and <strong>Amazon Q Business<\/strong> for business users) that integrates with AWS identity, permissions, and selected AWS services and tooling. Depending on the offering, it can answer questions grounded in your organization\u2019s content, help you write and refactor code inside IDEs, and provide guidance for AWS operations\u2014while respecting access controls.<\/p>\n\n\n\n<p><strong>What problem it solves:<\/strong> teams spend large amounts of time searching for answers (internal docs, tickets, runbooks), writing boilerplate code, troubleshooting cloud errors, and navigating AWS best practices. Amazon Q reduces that \u201ctime-to-solution\u201d by providing context-aware assistance directly in the tools where work happens.<\/p>\n\n\n\n<blockquote>\n<p>Naming note (important): Amazon Q is a current, active AWS product name. Some related AWS capabilities were previously branded differently (for example, <strong>Amazon CodeWhisperer<\/strong> is now part of <strong>Amazon Q Developer<\/strong>). Also, \u201cQ\u201d features exist in other AWS products (for example, Amazon Q in Amazon QuickSight). Always verify which <strong>Amazon Q<\/strong> offering you are enabling, because <strong>features, setup, and pricing vary by offering<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Amazon Q?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Official purpose<\/h3>\n\n\n\n<p>Amazon Q is an AWS generative AI assistant that helps users <strong>answer questions<\/strong>, <strong>generate and improve content or code<\/strong>, and <strong>complete tasks<\/strong> using natural language\u2014while integrating with AWS identity and (for some offerings) organizational knowledge sources.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Core capabilities (high-level)<\/h3>\n\n\n\n<p>Because Amazon Q is a \u201cfamily\u201d of capabilities, the exact feature set depends on what you enable. Common themes include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Conversational Q&amp;A<\/strong> for AWS, software development, and (for business offerings) enterprise knowledge.<\/li>\n<li><strong>Context-aware assistance<\/strong> inside supported user experiences (for example, IDE integrations for developers).<\/li>\n<li><strong>Security-aware behavior<\/strong> tied to identity, permissions, and administrative controls.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Major components (conceptual)<\/h3>\n\n\n\n<p>Amazon Q is not a single \u201cone-size\u201d console page; it is best understood as a set of offerings:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Amazon Q Developer<\/strong>: Focused on developers and engineers (IDE assistance, code generation, code explanation, and related workflows).<\/li>\n<li><strong>Amazon Q Business<\/strong>: Focused on business users and enterprise knowledge retrieval across approved data sources (connectors, indexing, access control).<\/li>\n<li><strong>Amazon Q in other AWS products<\/strong>: Some AWS products expose \u201cAmazon Q\u201d experiences tailored to that product (for example, Amazon Q in Amazon QuickSight). Setup and billing may be separate.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Service type<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Managed AWS AI assistant service<\/strong> (SaaS-like experience operated by AWS), exposed through AWS consoles and supported integrations (for example, IDE plugins).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scope (global vs regional, account vs subscription)<\/h3>\n\n\n\n<p>Amazon Q offerings have different scoping models:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Identity scope:<\/strong> Typically user-based (often integrated with AWS identity solutions such as IAM Identity Center).  <\/li>\n<li><strong>Account scope:<\/strong> Administrative configuration is associated with AWS accounts\/organizations for business deployments.  <\/li>\n<li><strong>Regional scope:<\/strong> Availability can be <strong>region-dependent<\/strong>. Even when a UI seems \u201cglobal,\u201d the underlying service endpoints and data processing may be tied to specific AWS Regions. <strong>Verify in official docs<\/strong> for your offering and region.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How it fits into the AWS ecosystem<\/h3>\n\n\n\n<p>Amazon Q sits above foundational AI building blocks like Amazon Bedrock and Amazon SageMaker:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>Amazon Q<\/strong> when you want an <strong>out-of-the-box assistant experience<\/strong> for users.<\/li>\n<li>Use <strong>Amazon Bedrock<\/strong> when you want to <strong>build<\/strong> your own generative AI applications (custom RAG, agents, model selection).<\/li>\n<li>Use <strong>Amazon SageMaker<\/strong> when you want <strong>end-to-end ML<\/strong> (training, tuning, hosting, MLOps).<\/li>\n<\/ul>\n\n\n\n<p>Amazon Q also integrates with AWS security and governance capabilities (for example, identity, auditing, and administrative controls), which is critical for enterprise adoption.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Amazon Q?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Business reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Faster knowledge discovery:<\/strong> Reduce time spent searching internal documentation, wikis, tickets, and runbooks (especially with Amazon Q Business).<\/li>\n<li><strong>Developer productivity:<\/strong> Reduce time spent on boilerplate coding, refactoring, and troubleshooting (especially with Amazon Q Developer).<\/li>\n<li><strong>Enablement at scale:<\/strong> Provide a consistent assistant experience across teams with centralized administration.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Natural language interface<\/strong> to complex systems and codebases.<\/li>\n<li><strong>Contextual assistance<\/strong> in developer tools (where supported).<\/li>\n<li><strong>Integration with AWS identity and access controls<\/strong> to align with enterprise security requirements.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Standardize how teams get answers:<\/strong> consistent guidance, fewer tribal-knowledge bottlenecks.<\/li>\n<li><strong>Shorten incident resolution loops:<\/strong> faster interpretation of logs\/errors and quicker access to runbooks (when integrated into documentation sources).<\/li>\n<li><strong>Reduce cognitive load<\/strong> for on-call and DevOps engineers by improving discoverability of procedures.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/compliance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Centralized control and permissions:<\/strong> leverage AWS identity patterns (for example, IAM Identity Center) so users see only what they\u2019re allowed to see (particularly relevant for Amazon Q Business).<\/li>\n<li><strong>Auditability:<\/strong> AWS services typically integrate with AWS logging and auditing services. Confirm exact audit log coverage for your Amazon Q offering in the docs.<\/li>\n<li><strong>Enterprise governance:<\/strong> better alignment than \u201cbring your own consumer chatbot\u201d approaches.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scalability\/performance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Managed scaling:<\/strong> AWS runs the service. You focus on enablement and governance rather than model hosting.<\/li>\n<li><strong>Consistent user experience:<\/strong> designed for many users across teams (subject to service limits and subscription tiers).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose Amazon Q<\/h3>\n\n\n\n<p>Choose Amazon Q if you want:\n&#8211; A <strong>ready-to-use assistant<\/strong> for developers or business users.\n&#8211; <strong>Enterprise identity and access control integration<\/strong>.\n&#8211; A managed solution rather than building your own generative AI stack.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose it<\/h3>\n\n\n\n<p>Avoid (or delay) Amazon Q if:\n&#8211; You need <strong>full control over model selection, prompts, RAG pipelines, and runtime<\/strong> (consider Amazon Bedrock instead).\n&#8211; You require <strong>on-prem-only<\/strong> processing or strict data residency constraints not supported by the service\/region.\n&#8211; Your security policy requires <strong>private network-only access<\/strong> and the offering does not support that (verify current networking options).\n&#8211; Your use case is highly specialized and would be better served by a custom application (Bedrock + your application code).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Amazon Q used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<p>Amazon Q is broadly applicable across regulated and non-regulated industries, such as:\n&#8211; Financial services (with careful governance)\n&#8211; Healthcare and life sciences (with strict compliance controls)\n&#8211; Retail and e-commerce\n&#8211; Manufacturing\n&#8211; Technology and SaaS\n&#8211; Public sector (verify eligibility and regional availability)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Team types<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Developers and platform engineers (Amazon Q Developer)<\/li>\n<li>DevOps\/SRE\/on-call teams<\/li>\n<li>Security engineers (secure coding assistance and best-practice guidance; verify exact feature set)<\/li>\n<li>Data analysts and BI teams (for Amazon Q in analytics experiences, depending on product)<\/li>\n<li>Business operations and knowledge workers (Amazon Q Business)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Software development and modernization<\/li>\n<li>Cloud operations and troubleshooting<\/li>\n<li>Knowledge management and internal support<\/li>\n<li>Documentation generation and maintenance<\/li>\n<li>Controlled self-service for internal questions (policies, procedures)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Architectures<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Centralized enterprise enablement (IAM Identity Center + centralized policies)<\/li>\n<li>Multi-account AWS Organizations with delegated admin models (where supported)<\/li>\n<li>Integration with approved knowledge sources (for Amazon Q Business)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Real-world deployment contexts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Production:<\/strong> enterprise-wide rollout with governance, connectors, audit, and lifecycle management.<\/li>\n<li><strong>Dev\/test:<\/strong> pilots for one team, one environment, or a limited subset of docs and repos before scaling.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are realistic scenarios that align with how teams typically adopt Amazon Q. Exact steps and availability depend on whether you use Amazon Q Developer, Amazon Q Business, or Amazon Q in another AWS product\u2014verify in the official documentation for your chosen offering.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) IDE pair-programmer for application development (Amazon Q Developer)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Developers lose time on boilerplate code, common patterns, and learning unfamiliar APIs.<\/li>\n<li><strong>Why Amazon Q fits:<\/strong> It integrates into supported IDEs and helps with code generation, explanation, and refactoring workflows.<\/li>\n<li><strong>Example scenario:<\/strong> A team building a Python service asks Amazon Q Developer to generate a safe input-validation function and unit tests.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Troubleshoot AWS permission errors faster (Amazon Q Developer)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> IAM-related errors are time-consuming to diagnose (\u201cAccessDenied\u201d, missing actions, wrong resource ARNs).<\/li>\n<li><strong>Why Amazon Q fits:<\/strong> It can help interpret AWS error messages and suggest likely permission gaps (you still validate).<\/li>\n<li><strong>Example scenario:<\/strong> An engineer pastes an AWS CLI error into the chat and gets guidance on which IAM action is likely missing.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Write Infrastructure as Code (IaC) templates (Amazon Q Developer)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Creating CloudFormation\/Terraform templates from scratch is repetitive and error-prone.<\/li>\n<li><strong>Why Amazon Q fits:<\/strong> It can propose starter templates and explain security implications (still requires review).<\/li>\n<li><strong>Example scenario:<\/strong> Generate a minimal CloudFormation template for an S3 bucket with encryption and blocked public access, then refine it.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Generate and maintain runbooks (Amazon Q Developer + your docs)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Runbooks are stale; updates lag behind operational changes.<\/li>\n<li><strong>Why Amazon Q fits:<\/strong> It can draft runbooks from existing procedures and incident notes.<\/li>\n<li><strong>Example scenario:<\/strong> Convert \u201ctribal knowledge\u201d Slack notes into a structured incident response runbook.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Internal knowledge assistant for policies and procedures (Amazon Q Business)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Employees ask the same HR\/IT\/security questions repeatedly; answers are scattered across systems.<\/li>\n<li><strong>Why Amazon Q fits:<\/strong> Amazon Q Business is designed for enterprise Q&amp;A grounded in approved content and controlled by permissions.<\/li>\n<li><strong>Example scenario:<\/strong> Users ask \u201cHow do I request VPN access?\u201d and get an answer with links to the official policy page.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Engineering onboarding assistant (Amazon Q Business)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> New hires struggle to find correct, current onboarding steps.<\/li>\n<li><strong>Why Amazon Q fits:<\/strong> A curated knowledge base reduces onboarding time and increases consistency.<\/li>\n<li><strong>Example scenario:<\/strong> A new engineer asks for \u201cHow do I set up local dev for Service A?\u201d and receives steps sourced from internal docs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Knowledge assistant for customer support teams (Amazon Q Business)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Support engineers need quick answers from product docs, known issues, and ticket history.<\/li>\n<li><strong>Why Amazon Q fits:<\/strong> Central Q&amp;A with controlled source access reduces time-to-resolution.<\/li>\n<li><strong>Example scenario:<\/strong> A support agent asks about an error code and gets a summary of known causes and the latest fix procedure.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Standardized secure coding help (Amazon Q Developer)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Inconsistent security practices across teams lead to vulnerabilities.<\/li>\n<li><strong>Why Amazon Q fits:<\/strong> Assist with secure patterns (input validation, secrets handling) and code review suggestions; developers still validate.<\/li>\n<li><strong>Example scenario:<\/strong> Ask for a secure way to load secrets from AWS Secrets Manager (and then implement following AWS best practices).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Data\/analytics natural language insights (Amazon Q in analytics experiences)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Business users can\u2019t easily query dashboards or metrics without learning BI tools.<\/li>\n<li><strong>Why Amazon Q fits:<\/strong> In-product \u201cQ\u201d experiences can translate questions into insights (availability depends on the product).<\/li>\n<li><strong>Example scenario:<\/strong> A sales manager asks, \u201cWhich region had the largest month-over-month growth?\u201d and gets a chart and explanation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Migration and modernization guidance (Amazon Q Developer)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Modernizing a legacy codebase is risky and time-consuming.<\/li>\n<li><strong>Why Amazon Q fits:<\/strong> Amazon Q Developer can help explain unfamiliar legacy code and suggest refactoring approaches. Some transformation capabilities may exist\u2014verify supported languages\/targets.<\/li>\n<li><strong>Example scenario:<\/strong> A team upgrading dependencies asks for a plan and code changes for safer exception handling and logging patterns.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Drafting internal architecture decision records (ADR) (Amazon Q Developer)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Architectural decisions aren\u2019t documented consistently.<\/li>\n<li><strong>Why Amazon Q fits:<\/strong> It can generate ADR templates and summarize tradeoffs.<\/li>\n<li><strong>Example scenario:<\/strong> Draft an ADR comparing SNS+SQS vs EventBridge for asynchronous integration.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Reduce \u201cbus factor\u201d with explainability (Amazon Q Developer)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Only a few senior engineers understand key parts of the system.<\/li>\n<li><strong>Why Amazon Q fits:<\/strong> It can explain code blocks and produce documentation comments.<\/li>\n<li><strong>Example scenario:<\/strong> Ask for an explanation of a complex concurrency module and generate inline documentation.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<p>Amazon Q is multi-offering; features below are grouped and described in a way that helps you map them to your deployment. <strong>Verify the exact feature list for your Amazon Q offering<\/strong> in the official documentation, because capabilities and UI change over time.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Feature 1: Conversational chat experience<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Allows users to ask questions in natural language and get answers, guidance, or generated output.<\/li>\n<li><strong>Why it matters:<\/strong> Reduces time spent searching docs and copying snippets.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster iteration for troubleshooting, learning, and drafting.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Output can be wrong or incomplete; you must validate. Apply guardrails and a review culture.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Feature 2: IDE assistance for coding (Amazon Q Developer)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides code suggestions, explanations, and generation workflows inside supported IDEs (via AWS tooling integrations).<\/li>\n<li><strong>Why it matters:<\/strong> Keeps developers in-flow; avoids context switching.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster coding, fewer syntax\/API mistakes, quicker onboarding.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> IDE support varies (for example, VS Code vs JetBrains). Features may differ by edition\/subscription.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Feature 3: Code explanation and refactoring help (Amazon Q Developer)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Explains unfamiliar code, proposes refactors, and can help draft tests and documentation.<\/li>\n<li><strong>Why it matters:<\/strong> Improves maintainability and team knowledge transfer.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster reviews and safer changes when paired with testing.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Suggestions may not match your style guide; ensure you enforce linters, tests, and code review.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Feature 4: Assistance with AWS APIs and operations (Amazon Q Developer)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Helps interpret AWS errors, suggests likely causes, and provides steps or snippets for AWS tasks.<\/li>\n<li><strong>Why it matters:<\/strong> AWS systems are broad; guidance accelerates resolution.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster diagnosis for IAM and service configuration issues.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Do not blindly apply changes; validate against your security baselines.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Feature 5: Enterprise knowledge grounding (Amazon Q Business)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Answers questions grounded in your organization\u2019s indexed content, subject to user permissions.<\/li>\n<li><strong>Why it matters:<\/strong> Without grounding, assistants can be generic; knowledge grounding increases relevance.<\/li>\n<li><strong>Practical benefit:<\/strong> Employees get answers with citations\/links to internal sources (depending on configuration).<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Quality depends on content hygiene and access control mapping. Connector availability varies\u2014verify the current connector list.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Feature 6: Connectors to content sources (Amazon Q Business)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Connects Amazon Q Business to approved content repositories (for example, AWS data stores and selected SaaS apps).<\/li>\n<li><strong>Why it matters:<\/strong> Automates ingestion and indexing; reduces manual updates.<\/li>\n<li><strong>Practical benefit:<\/strong> Keep knowledge up to date.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Each connector has its own auth model and constraints; some sources may require extra licensing or admin consent. Verify supported connectors and any limits.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Feature 7: Identity and access control integration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Aligns access to Amazon Q experiences and content with enterprise identity.<\/li>\n<li><strong>Why it matters:<\/strong> Prevents data leakage and enforces least privilege.<\/li>\n<li><strong>Practical benefit:<\/strong> Users see responses based on what they are allowed to access.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Misconfigured identity mapping or overly broad permissions can leak information.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Feature 8: Administrative controls and governance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides administrative configuration for enabling the service, managing users, and controlling access.<\/li>\n<li><strong>Why it matters:<\/strong> Enterprises need control for rollout, monitoring, and compliance.<\/li>\n<li><strong>Practical benefit:<\/strong> Centralized enablement, consistent guardrails.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Admin model differs by offering; follow the official admin guide.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Feature 9: Logging, auditing, and monitoring hooks (varies by offering)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Supports observability through AWS-native mechanisms where available (for example, audit logs of administrative actions).<\/li>\n<li><strong>Why it matters:<\/strong> Security teams need auditability; operations teams need metrics.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster investigations and compliance reporting.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Not all user interactions are always logged the same way; <strong>verify<\/strong> what is logged and how long it\u2019s retained.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Feature 10: Multi-user scaling (subscription-based)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Supports broad adoption across organizations.<\/li>\n<li><strong>Why it matters:<\/strong> Adoption is often the goal; not just a single-user tool.<\/li>\n<li><strong>Practical benefit:<\/strong> Standardized assistant for teams.<\/li>\n<li><strong>Limitations\/caveats:<\/strong> Costs scale with users and usage; manage rollout thoughtfully.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">7. Architecture and How It Works<\/h2>\n\n\n\n<p>Because Amazon Q includes multiple offerings, treat \u201carchitecture\u201d as <strong>a pattern<\/strong> rather than a single diagram. This section explains two common patterns:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>A <strong>developer-assistant<\/strong> pattern (Amazon Q Developer).<\/li>\n<li>An <strong>enterprise knowledge assistant<\/strong> pattern (Amazon Q Business).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">High-level architecture concepts<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">Control plane vs data plane<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Control plane:<\/strong> Admin configuration, user enablement, identity integration, and connector setup (for Q Business).<\/li>\n<li><strong>Data plane:<\/strong> User prompts, responses, and (for Q Business) retrieval from indexed content.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Request\/data flow (conceptual)<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>A user authenticates via the approved identity method.<\/li>\n<li>The user submits a question or task.<\/li>\n<li>Amazon Q processes the request (potentially retrieving relevant content if configured).<\/li>\n<li>Amazon Q returns a response.<\/li>\n<li>Admin\/audit systems record relevant events (coverage varies).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related AWS services (common patterns)<\/h3>\n\n\n\n<p>Depending on the offering, Amazon Q commonly relates to:\n&#8211; <strong>Identity:<\/strong> IAM Identity Center (common for enterprise SSO); IAM for AWS permissions management.\n&#8211; <strong>Security:<\/strong> AWS KMS for encryption (service-managed or customer-managed keys depending on offering\/settings\u2014verify).\n&#8211; <strong>Audit\/monitoring:<\/strong> AWS CloudTrail \/ Amazon CloudWatch (availability varies by event type\u2014verify).\n&#8211; <strong>Data sources:<\/strong> Amazon S3 (common enterprise content store) and other sources through managed connectors (verify current connector list).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/authentication model (conceptual)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>End users<\/strong> authenticate using supported identity providers (often via IAM Identity Center for organizational SSO).<\/li>\n<li><strong>Authorization<\/strong> is enforced through:<\/li>\n<li>the user\u2019s identity and group membership,<\/li>\n<li>application-level access assignments (Q Business),<\/li>\n<li>and access control mapping for content sources (Q Business connectors).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Networking model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Amazon Q is accessed via AWS-managed endpoints over TLS.<\/li>\n<li>For private networking (VPC-only access), <strong>verify in official docs<\/strong> whether the specific offering supports AWS PrivateLink or other private endpoint options.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monitoring\/logging\/governance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Track:<\/li>\n<li>user enablement and access assignments,<\/li>\n<li>connector health and sync status (Q Business),<\/li>\n<li>audit events (CloudTrail where supported),<\/li>\n<li>cost allocation (tags, account separation, chargeback).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Simple architecture diagram (Mermaid)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  U[User] --&gt;|SSO \/ Sign-in| ID[Identity Provider \/ IAM Identity Center]\n  U --&gt;|Chat \/ Prompt| Q[Amazon Q]\n  Q --&gt;|Answer \/ Suggestions| U\n  Admin[Admin] --&gt;|Configure \/ Govern| Q\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Production-style architecture diagram (Mermaid)<\/h3>\n\n\n\n<p>This diagram focuses on an enterprise knowledge assistant pattern (Amazon Q Business) plus developer enablement (Amazon Q Developer) at scale.<\/p>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph Org[AWS Organization]\n    subgraph Sec[Security &amp; Governance]\n      CT[CloudTrail (audit)\\nVerify coverage]\n      CW[CloudWatch (metrics\/logs)\\nVerify coverage]\n      KMS[AWS KMS Keys\\n(verify CMK support)]\n      SCP[SCPs \/ Guardrails]\n    end\n\n    subgraph Identity[Identity &amp; Access]\n      IdC[IAM Identity Center\\n(SSO)]\n      Groups[Groups \/ Attributes]\n    end\n\n    subgraph QSuite[Amazon Q Offerings]\n      QDev[Amazon Q Developer\\n(IDE\/console experience)]\n      QBus[Amazon Q Business\\n(App + Index)]\n      Conn[Managed Connectors\\n(verify sources)]\n    end\n\n    subgraph Content[Enterprise Content Sources]\n      S3[Amazon S3\\nDocs\/Runbooks]\n      SaaS[SaaS Sources\\n(e.g., wiki\/tickets)\\nverify list]\n    end\n  end\n\n  UserDev[Developers] --&gt; IdC\n  UserBiz[Business Users] --&gt; IdC\n\n  IdC --&gt; QDev\n  IdC --&gt; QBus\n  Groups --&gt; QBus\n\n  QBus --&gt; Conn --&gt; S3\n  Conn --&gt; SaaS\n\n  QDev --&gt;|Assistance| UserDev\n  QBus --&gt;|Grounded answers| UserBiz\n\n  QDev -.audit\/metrics.-&gt; CT\n  QBus -.audit\/metrics.-&gt; CT\n  QBus -.encryption.-&gt; KMS\n  QDev -.encryption.-&gt; KMS\n  CT --&gt; CW\n\n  SCP --&gt; QSuite\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\n\n\n\n<p>Prerequisites vary by Amazon Q offering. The list below covers a practical baseline for most labs and pilots.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Account\/subscription requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An <strong>AWS account<\/strong> for administrative setup (especially for Amazon Q Business).<\/li>\n<li>For Amazon Q Developer in an IDE, AWS may allow use with an <strong>AWS Builder ID<\/strong> for certain tiers\/features. Availability and capabilities can differ\u2014<strong>verify in official docs<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM roles<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>For Amazon Q Developer in IDE:<\/li>\n<li>IDE sign-in permissions (varies by identity method).<\/li>\n<li>If you will access AWS resources (optional), you need standard IAM permissions for the tasks you perform.<\/li>\n<li>For Amazon Q Business (admin):<\/li>\n<li>Permissions to configure the Amazon Q Business application and its data source connectors.<\/li>\n<li>Permissions to configure IAM Identity Center assignments and (if used) IAM roles for connectors.<\/li>\n<\/ul>\n\n\n\n<p><strong>Best practice:<\/strong> Create separate admin roles (least privilege) for:\n&#8211; Q admin,\n&#8211; connector admin,\n&#8211; security\/audit admin.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Billing requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A valid payment method on the AWS account.<\/li>\n<li>Be aware that some Amazon Q offerings are <strong>per-user subscription priced<\/strong> and can scale quickly with user count.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tools needed (for this tutorial\u2019s lab)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A workstation with:<\/li>\n<li><strong>Visual Studio Code<\/strong> (VS Code)<\/li>\n<li>Internet access to download extensions<\/li>\n<li>VS Code extension:<\/li>\n<li><strong>AWS Toolkit<\/strong> (which provides Amazon Q Developer integration in supported configurations)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Amazon Q availability is <strong>region-dependent<\/strong> and varies by offering.<br\/>\n  Always confirm supported regions in official docs before committing to an architecture.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas\/limits<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Limits (users, connectors, sync frequency, etc.) vary by offering and can change.<\/li>\n<li>Check <strong>Service Quotas<\/strong> and the Amazon Q documentation for your offering.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services (common)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>IAM Identity Center<\/strong> (often recommended for enterprise deployments; verify requirement for your offering)<\/li>\n<li>Optional for Q Business:<\/li>\n<li>Content sources such as Amazon S3 or supported SaaS repositories<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<p>Amazon Q pricing depends on which \u201cQ\u201d offering you use. <strong>Do not assume one pricing model applies to all of them.<\/strong> Always confirm in the official AWS pricing pages for the specific offering you\u2019re enabling.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Current pricing model (what to expect)<\/h3>\n\n\n\n<p>Common pricing dimensions include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Per-user subscription pricing<\/strong> (common for Amazon Q Business and Amazon Q Developer paid tiers).<\/li>\n<li><strong>Usage-based components<\/strong> (possible for indexing, retrieval capacity, or add-on features depending on offering\u2014verify).<\/li>\n<li><strong>Edition\/tier differences<\/strong> (for example, Free vs Pro tiers for developer tooling\u2014verify current tiers).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier<\/h3>\n\n\n\n<p>Some Amazon Q Developer experiences historically offered free usage tiers (for example, for individuals). Whether a free tier exists today, what it includes, and any constraints (monthly caps, feature limits) must be validated against the official pricing page.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Cost drivers<\/h3>\n\n\n\n<p>Key cost drivers typically include:\n&#8211; <strong>Number of enabled users<\/strong> (the biggest lever in subscription models).\n&#8211; <strong>Which tier\/edition<\/strong> each user is assigned to.\n&#8211; For Q Business-style deployments:\n  &#8211; number and size of connected content sources,\n  &#8211; frequency of sync\/index updates,\n  &#8211; usage intensity (how often users query).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Hidden or indirect costs<\/h3>\n\n\n\n<p>Even if Amazon Q itself is subscription priced, you may also pay for:\n&#8211; <strong>Data storage<\/strong> in your content repositories (e.g., Amazon S3).\n&#8211; <strong>Data transfer<\/strong> (internet egress from sources; cross-region transfer if any).\n&#8211; <strong>Identity provider costs<\/strong> (if your IdP has licensing).\n&#8211; <strong>Operational overhead<\/strong> (time to manage connectors, permissions mapping, and content hygiene).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Network\/data transfer implications<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If your content sources are in AWS, data transfer patterns depend on region placement and service architecture.<\/li>\n<li>If your content sources are SaaS, you may incur API costs or rate-limiting constraints on the SaaS side.<\/li>\n<li>Avoid cross-region content architectures unless necessary; they can increase cost and complexity.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to optimize cost<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Start with a <strong>pilot group<\/strong> (10\u201350 users) and expand in phases.<\/li>\n<li>Use <strong>tiered licensing<\/strong>: assign paid tiers only to users who need them.<\/li>\n<li>For Q Business:<\/li>\n<li>connect only high-value sources first,<\/li>\n<li>remove obsolete content,<\/li>\n<li>tune sync schedules to balance freshness vs cost\/limits.<\/li>\n<li>Use tags, accounts, and cost allocation to support showback\/chargeback.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (non-numeric guidance)<\/h3>\n\n\n\n<p>A low-cost starter pilot often looks like:\n&#8211; A small number of users on the minimum tier that meets requirements.\n&#8211; Minimal connectors (or none initially).\n&#8211; A short pilot window (2\u20134 weeks) to validate value.<\/p>\n\n\n\n<p>Because AWS pricing is tier- and region-dependent, <strong>use the official pricing page and AWS Pricing Calculator<\/strong> to compute actual numbers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations<\/h3>\n\n\n\n<p>For production rollout, consider:\n&#8211; Licensing for hundreds\/thousands of users.\n&#8211; Dedicated admin and security review time.\n&#8211; Connector maintenance and content lifecycle processes.\n&#8211; Governance (audit, policies, training).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Official pricing pages and calculator<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Amazon Q pricing landing (may link to individual offerings): https:\/\/aws.amazon.com\/q\/  <\/li>\n<li>Amazon Q Business pricing: https:\/\/aws.amazon.com\/q\/business\/pricing\/  <\/li>\n<li>Amazon Q Developer pricing: https:\/\/aws.amazon.com\/q\/developer\/pricing\/  <\/li>\n<li>AWS Pricing Calculator: https:\/\/calculator.aws\/#\/<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<p>This lab focuses on <strong>Amazon Q Developer in VS Code<\/strong> because it\u2019s a practical, beginner-friendly way to experience Amazon Q with minimal AWS infrastructure changes. You will use Amazon Q Developer to explain code, fix a bug, and generate unit tests locally.<\/p>\n\n\n\n<blockquote>\n<p>This lab avoids provisioning AWS resources to keep cost and risk low. If you choose to extend it to AWS integrations (S3, Lambda, etc.), do so in a sandbox account with least privilege.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<p>Enable Amazon Q Developer in VS Code and use it to:\n1. Explain an unfamiliar piece of code.\n2. Fix a real bug in a small Python program.\n3. Generate unit tests and run them locally.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Install VS Code and the AWS Toolkit.\n2. Sign in to enable Amazon Q Developer.\n3. Create a small Python project with a deliberate bug.\n4. Use Amazon Q Developer to diagnose and fix the bug.\n5. Ask Amazon Q Developer to generate unit tests.\n6. Validate locally (run tests).\n7. Clean up (remove project and\/or sign out).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Install prerequisites (VS Code + Python)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Install <strong>Visual Studio Code<\/strong>: https:\/\/code.visualstudio.com\/<\/li>\n<li>Install <strong>Python 3.10+<\/strong> (or your org standard): https:\/\/www.python.org\/downloads\/<\/li>\n<li>Confirm Python is available:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">python3 --version\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome:<\/strong> <code>python3<\/code> prints a version (e.g., 3.11.x).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Install AWS Toolkit in VS Code<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open VS Code.<\/li>\n<li>Go to <strong>Extensions<\/strong>.<\/li>\n<li>Search for <strong>AWS Toolkit<\/strong> (publisher: Amazon Web Services).<\/li>\n<li>Click <strong>Install<\/strong>.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> AWS Toolkit appears in the Extensions list and an AWS icon appears in the Activity Bar (left side).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Enable Amazon Q Developer (sign in)<\/h3>\n\n\n\n<p>The sign-in method depends on your environment:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Individuals often use <strong>AWS Builder ID<\/strong> (if supported for your tier).<\/li>\n<li>Enterprises often use <strong>IAM Identity Center (SSO)<\/strong>.<\/li>\n<\/ul>\n\n\n\n<p>In VS Code:\n1. Open the AWS Toolkit panel.\n2. Find an option related to <strong>Amazon Q Developer<\/strong> or \u201cAmazon Q\u201d.\n3. Choose <strong>Sign in<\/strong> and follow the prompts.<\/p>\n\n\n\n<p>If you are in an enterprise:\n&#8211; Use the SSO start URL provided by your admin.\n&#8211; Ensure your user is entitled to Amazon Q Developer.<\/p>\n\n\n\n<p><strong>Expected outcome:<\/strong> You can open an Amazon Q Developer chat panel or see Amazon Q Developer features enabled in the IDE.<\/p>\n\n\n\n<blockquote>\n<p>If you cannot find the Amazon Q Developer UI in the Toolkit: verify your AWS Toolkit version and refer to the official Amazon Q Developer documentation, because the UI placement can change over time.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Create a small Python project with a deliberate bug<\/h3>\n\n\n\n<p>Create a new folder and files:<\/p>\n\n\n\n<pre><code class=\"language-bash\">mkdir amazon-q-lab\ncd amazon-q-lab\nmkdir -p src tests\n<\/code><\/pre>\n\n\n\n<p>Create <code>src\/price.py<\/code>:<\/p>\n\n\n\n<pre><code class=\"language-python\"># src\/price.py\n\ndef apply_discount(price: float, discount_percent: float) -&gt; float:\n    \"\"\"\n    Apply a percentage discount to a price.\n\n    discount_percent should be in the range [0, 100].\n    \"\"\"\n    if price &lt; 0:\n        raise ValueError(\"price must be &gt;= 0\")\n\n    # BUG: this formula is incorrect for percentage discounts.\n    return price - discount_percent\n<\/code><\/pre>\n\n\n\n<p>Create a quick runner <code>src\/app.py<\/code>:<\/p>\n\n\n\n<pre><code class=\"language-python\"># src\/app.py\nfrom price import apply_discount\n\nif __name__ == \"__main__\":\n    original = 200.0\n    discounted = apply_discount(original, 10.0)\n    print(f\"Original: {original}, discounted: {discounted}\")\n<\/code><\/pre>\n\n\n\n<p>Now run it:<\/p>\n\n\n\n<pre><code class=\"language-bash\">python3 -c \"import sys; sys.path.append('src'); from price import apply_discount; print(apply_discount(200.0, 10.0))\"\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome:<\/strong> It prints <code>190.0<\/code>, which is incorrect for a 10% discount on 200 (should be 180.0). This is the bug you will fix.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Use Amazon Q Developer to explain and diagnose the bug<\/h3>\n\n\n\n<p>In VS Code:\n1. Open the <code>src\/price.py<\/code> file.\n2. Open the Amazon Q Developer chat panel.\n3. Ask a prompt like:<\/p>\n\n\n\n<pre><code class=\"language-text\">Explain what apply_discount is doing and identify any bug in the logic. The discount is supposed to be a percentage from 0 to 100.\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome:<\/strong> Amazon Q Developer explains that the code subtracts the raw discount number instead of applying a percentage and suggests a corrected formula.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Apply the fix with a safe implementation<\/h3>\n\n\n\n<p>Update <code>src\/price.py<\/code> to validate the percent range and apply the correct formula:<\/p>\n\n\n\n<pre><code class=\"language-python\"># src\/price.py\n\ndef apply_discount(price: float, discount_percent: float) -&gt; float:\n    \"\"\"\n    Apply a percentage discount to a price.\n\n    discount_percent should be in the range [0, 100].\n    \"\"\"\n    if price &lt; 0:\n        raise ValueError(\"price must be &gt;= 0\")\n    if discount_percent &lt; 0 or discount_percent &gt; 100:\n        raise ValueError(\"discount_percent must be between 0 and 100\")\n\n    return price * (1 - (discount_percent \/ 100.0))\n<\/code><\/pre>\n\n\n\n<p>Re-run the quick test:<\/p>\n\n\n\n<pre><code class=\"language-bash\">python3 -c \"import sys; sys.path.append('src'); from price import apply_discount; print(apply_discount(200.0, 10.0))\"\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome:<\/strong> It prints <code>180.0<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 7: Ask Amazon Q Developer to generate unit tests<\/h3>\n\n\n\n<p>Install pytest (in a virtual environment is recommended):<\/p>\n\n\n\n<pre><code class=\"language-bash\">python3 -m venv .venv\nsource .venv\/bin\/activate\npip install -U pip pytest\n<\/code><\/pre>\n\n\n\n<p>Create <code>tests\/test_price.py<\/code>. You can ask Amazon Q Developer:<\/p>\n\n\n\n<pre><code class=\"language-text\">Generate pytest unit tests for apply_discount covering:\n- normal cases (10% of 200)\n- boundary cases (0% and 100%)\n- invalid inputs (negative price, percent outside 0-100)\n<\/code><\/pre>\n\n\n\n<p>A solid test file looks like this (you can paste or compare with Amazon Q\u2019s output):<\/p>\n\n\n\n<pre><code class=\"language-python\"># tests\/test_price.py\n\nimport sys\nimport pytest\n\nsys.path.append(\"src\")\nfrom price import apply_discount\n\ndef test_apply_discount_normal_case():\n    assert apply_discount(200.0, 10.0) == 180.0\n\ndef test_apply_discount_zero_percent():\n    assert apply_discount(99.99, 0.0) == 99.99\n\ndef test_apply_discount_hundred_percent():\n    assert apply_discount(50.0, 100.0) == 0.0\n\ndef test_apply_discount_negative_price_raises():\n    with pytest.raises(ValueError):\n        apply_discount(-1.0, 10.0)\n\n@pytest.mark.parametrize(\"pct\", [-0.01, 100.01, 1000.0])\ndef test_apply_discount_invalid_percent_raises(pct):\n    with pytest.raises(ValueError):\n        apply_discount(10.0, pct)\n<\/code><\/pre>\n\n\n\n<p>Run tests:<\/p>\n\n\n\n<pre><code class=\"language-bash\">pytest -q\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome:<\/strong> All tests pass.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Validation<\/h3>\n\n\n\n<p>You have validated Amazon Q Developer\u2019s usefulness if:\n&#8211; The IDE shows Amazon Q Developer chat assistance enabled.\n&#8211; The function\u2019s bug is fixed and outputs the correct result.\n&#8211; Unit tests run successfully with <code>pytest<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<p><strong>Issue: Amazon Q Developer UI does not appear in VS Code<\/strong>\n&#8211; Update AWS Toolkit to the latest version.\n&#8211; Ensure you are signed in through the supported method (Builder ID or IAM Identity Center).\n&#8211; Verify your organization has enabled Amazon Q Developer for your user (for enterprise SSO).\n&#8211; Check official docs for the current VS Code integration steps:\n  &#8211; Amazon Q Developer documentation: https:\/\/docs.aws.amazon.com\/amazonq\/latest\/qdeveloper-ug\/what-is.html (verify exact URL if it changes)<\/p>\n\n\n\n<p><strong>Issue: Sign-in fails<\/strong>\n&#8211; For IAM Identity Center: confirm your SSO start URL, region, and that your device is compliant with corporate policy.\n&#8211; For Builder ID: verify you are using the correct AWS account identity path for Amazon Q Developer.<\/p>\n\n\n\n<p><strong>Issue: Tests fail due to import paths<\/strong>\n&#8211; Ensure <code>src<\/code> is added to <code>sys.path<\/code> in tests as shown, or package your code properly.\n&#8211; Run <code>pytest<\/code> from the project root (<code>amazon-q-lab<\/code>).<\/p>\n\n\n\n<p><strong>Issue: Suggested code is insecure or not aligned to policy<\/strong>\n&#8211; Treat Amazon Q output as a draft. Apply secure coding standards, run static analysis, and require code review.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>To clean up locally:\n&#8211; Close VS Code.\n&#8211; Delete the folder:<\/p>\n\n\n\n<pre><code class=\"language-bash\">cd ..\nrm -rf amazon-q-lab\n<\/code><\/pre>\n\n\n\n<p>Optional:\n&#8211; In VS Code AWS Toolkit, <strong>sign out<\/strong> if you used a shared machine.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">11. Best Practices<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Architecture best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Choose the right Amazon Q offering<\/strong>:<\/li>\n<li>Use <strong>Amazon Q Developer<\/strong> for developer workflows.<\/li>\n<li>Use <strong>Amazon Q Business<\/strong> for enterprise knowledge Q&amp;A.<\/li>\n<li>Start with a <strong>pilot<\/strong> and define success metrics:<\/li>\n<li>time saved per task,<\/li>\n<li>reduced mean-time-to-resolution,<\/li>\n<li>onboarding time reduction,<\/li>\n<li>adoption and satisfaction.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">IAM\/security best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Apply <strong>least privilege<\/strong>:<\/li>\n<li>Separate admin roles from end-user roles.<\/li>\n<li>Limit connector permissions to only required sources.<\/li>\n<li>Use <strong>SSO (IAM Identity Center)<\/strong> for enterprise use cases where possible.<\/li>\n<li>Maintain a process for <strong>access reviews<\/strong> (quarterly\/biannual).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Control costs with:<\/li>\n<li><strong>phased rollout<\/strong> (small group \u2192 wider org),<\/li>\n<li><strong>tiering<\/strong> (paid tiers only where needed),<\/li>\n<li>chargeback\/showback using account separation and tags.<\/li>\n<li>For Q Business, connect <strong>high-value content sources first<\/strong> rather than indexing \u201ceverything.\u201d<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Performance best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Improve answer quality by improving input quality:<\/li>\n<li>remove outdated documents,<\/li>\n<li>consolidate duplicate runbooks,<\/li>\n<li>standardize document structure (headings, owners, last-updated date).<\/li>\n<li>For Q Business, tune connector scopes (folders\/spaces\/projects) to reduce noise.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Reliability best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treat knowledge as a product:<\/li>\n<li>assign owners,<\/li>\n<li>set review cycles,<\/li>\n<li>define deprecation procedures.<\/li>\n<li>For Q Business connectors, monitor sync health and establish an operational runbook.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operations best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Document:<\/li>\n<li>how to onboard\/offboard users,<\/li>\n<li>how to approve new content sources,<\/li>\n<li>how to respond to suspected data exposure.<\/li>\n<li>Establish a feedback loop so users can report:<\/li>\n<li>incorrect answers,<\/li>\n<li>missing sources,<\/li>\n<li>stale documents.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Governance\/tagging\/naming best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use consistent naming for:<\/li>\n<li>Q Business applications,<\/li>\n<li>data sources\/connectors,<\/li>\n<li>environments (dev\/pilot\/prod).<\/li>\n<li>Apply tags for cost and ownership where supported.<\/li>\n<li>Maintain an internal \u201cAI acceptable use policy\u201d for prompts and sensitive data.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">12. Security Considerations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Identity and access model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Amazon Q Developer:<\/strong> user access is typically controlled via sign-in method (Builder ID or enterprise SSO) and organization entitlements.<\/li>\n<li><strong>Amazon Q Business:<\/strong> user access typically relies on enterprise identity and access assignments, plus content access mapping for connected repositories.<\/li>\n<\/ul>\n\n\n\n<p><strong>Key security requirement:<\/strong> users must only be able to retrieve information they are authorized to access. Confirm how the connector enforces ACLs and group mapping for each source.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>AWS services commonly support encryption at rest and in transit.<\/li>\n<li>For Amazon Q, encryption specifics (including whether you can use <strong>customer-managed KMS keys<\/strong>) depend on the offering and configuration.<\/li>\n<li><strong>Verify in official docs<\/strong> for your Amazon Q offering:<\/li>\n<li>encryption at rest,<\/li>\n<li>encryption in transit,<\/li>\n<li>key management options.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network exposure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Amazon Q is accessed via AWS-managed endpoints over TLS.<\/li>\n<li>If your environment requires private connectivity:<\/li>\n<li>verify whether the offering supports AWS PrivateLink or equivalent.<\/li>\n<li>if not supported, control access through identity, device posture, and egress controls.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secrets handling<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Never paste:<\/li>\n<li>long-lived AWS access keys,<\/li>\n<li>database credentials,<\/li>\n<li>private keys,<\/li>\n<li>sensitive customer data\n  into chat prompts.<\/li>\n<li>Use secure patterns:<\/li>\n<li>short-lived credentials (SSO),<\/li>\n<li>AWS Secrets Manager for application secrets,<\/li>\n<li>redaction policies in runbooks and training.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Audit\/logging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Confirm what is captured in:<\/li>\n<li>AWS CloudTrail (admin actions, API calls),<\/li>\n<li>service logs\/telemetry options (if any),<\/li>\n<li>connector audit trails.<\/li>\n<li>Define retention and access policies for logs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>For regulated workloads:<\/li>\n<li>perform a vendor\/service risk review,<\/li>\n<li>review AWS compliance artifacts (SOC, ISO, etc.) relevant to your region and offering,<\/li>\n<li>confirm data residency and retention behaviors.<\/li>\n<li>Consult the AWS documentation and compliance resources for Amazon Q. If unclear, treat it as \u201cVerify in official docs.\u201d<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common security mistakes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Overbroad connector scopes (\u201cindex the entire company drive\u201d).<\/li>\n<li>Misconfigured group mapping that grants access too widely.<\/li>\n<li>Treating responses as authoritative without validation.<\/li>\n<li>Allowing sensitive production incident data to be pasted into prompts without sanitization.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secure deployment recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Roll out with:<\/li>\n<li><strong>pilot group<\/strong> + security review,<\/li>\n<li>documented acceptable use,<\/li>\n<li>regular access audits,<\/li>\n<li>least-privilege connector configurations,<\/li>\n<li>incident response procedures for suspected data exposure.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<p>Because Amazon Q is a suite of offerings, limitations are offering-specific. The items below are common patterns to plan for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Region availability varies<\/strong> by offering and feature set.<\/li>\n<li><strong>Connector availability varies<\/strong> and can change. Always verify the current list of supported connectors and their constraints.<\/li>\n<li><strong>Answer quality depends on your content quality<\/strong> (Q Business) and your prompts\/context (Q Developer).<\/li>\n<li><strong>Not a substitute for code review or security review.<\/strong><\/li>\n<li><strong>Costs can scale linearly with users<\/strong> in subscription models.<\/li>\n<li><strong>Audit coverage may not match expectations<\/strong>\u2014verify exactly what is logged and where.<\/li>\n<li><strong>Network isolation may be limited<\/strong> if private endpoints are not supported (verify).<\/li>\n<li><strong>Enterprise rollout requires change management:<\/strong> training, acceptable use policy, and governance.<\/li>\n<li><strong>Data source permissions mapping is non-trivial:<\/strong> incorrect mapping can cause overexposure or underexposure.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<p>Amazon Q is best compared against:\n&#8211; <strong>Other AWS services<\/strong> that solve adjacent problems differently (Bedrock, Kendra, SageMaker).\n&#8211; <strong>Other cloud assistants<\/strong> (Microsoft Copilot, Google Gemini offerings).\n&#8211; <strong>Self-managed\/open-source<\/strong> assistants built on open models plus a RAG stack.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Comparison table<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Best For<\/th>\n<th>Strengths<\/th>\n<th>Weaknesses<\/th>\n<th>When to Choose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Amazon Q (Developer\/Business)<\/strong><\/td>\n<td>Managed assistant for developers or enterprise knowledge<\/td>\n<td>AWS-native identity\/governance alignment; managed experience; integrates with AWS tooling<\/td>\n<td>Offering-specific constraints; subscription costs; connectors\/regions vary<\/td>\n<td>When you want an AWS-managed assistant with enterprise controls<\/td>\n<\/tr>\n<tr>\n<td><strong>Amazon Bedrock<\/strong><\/td>\n<td>Building custom genAI apps (RAG, agents, model choice)<\/td>\n<td>Maximum flexibility; design your own workflows; integrate with your app<\/td>\n<td>You must build, secure, and operate the app; more engineering effort<\/td>\n<td>When you need custom behavior, custom UX, or deep integration<\/td>\n<\/tr>\n<tr>\n<td><strong>Amazon Kendra<\/strong><\/td>\n<td>Enterprise search (non-chat-first)<\/td>\n<td>Mature enterprise search patterns; indexing and relevance<\/td>\n<td>Not a full assistant experience by itself<\/td>\n<td>When you primarily need search; pair with custom genAI if needed<\/td>\n<\/tr>\n<tr>\n<td><strong>Amazon SageMaker<\/strong><\/td>\n<td>Full ML lifecycle (train, tune, host)<\/td>\n<td>Full control for ML teams; MLOps tools<\/td>\n<td>Higher complexity; not a turnkey assistant<\/td>\n<td>When you need custom ML models and pipelines<\/td>\n<\/tr>\n<tr>\n<td><strong>Microsoft Copilot (various editions)<\/strong><\/td>\n<td>Organizations standardized on Microsoft ecosystem<\/td>\n<td>Deep integration with Microsoft 365 and dev tools<\/td>\n<td>Ecosystem lock-in; data governance differs<\/td>\n<td>When your knowledge and workflows are mostly in Microsoft stack<\/td>\n<\/tr>\n<tr>\n<td><strong>Google Cloud Gemini offerings<\/strong><\/td>\n<td>Organizations standardized on Google ecosystem<\/td>\n<td>Strong integration with Google Workspace and GCP<\/td>\n<td>Ecosystem alignment required<\/td>\n<td>When your workflows and data are primarily in Google services<\/td>\n<\/tr>\n<tr>\n<td><strong>ChatGPT Enterprise \/ similar<\/strong><\/td>\n<td>General enterprise assistant<\/td>\n<td>Strong general reasoning and UX<\/td>\n<td>Governance and AWS-specific integration varies<\/td>\n<td>When you need a general assistant and have clear governance controls<\/td>\n<\/tr>\n<tr>\n<td><strong>Self-managed (open-source model + RAG)<\/strong><\/td>\n<td>Highly customized needs or strict control<\/td>\n<td>Full control over data, models, and networking<\/td>\n<td>Highest operational burden; requires ML\/security expertise<\/td>\n<td>When policy requires maximum control or on-prem processing<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">15. Real-World Example<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Enterprise example: Large financial services organization<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Engineers and operations teams spend too long searching internal runbooks, architecture docs, and compliance procedures. New hires take months to become productive.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>IAM Identity Center for SSO and group-based access.<\/li>\n<li>Amazon Q Business connected to approved internal sources (for example, a curated S3 documentation bucket and selected ticket\/wiki systems via supported connectors\u2014verify).<\/li>\n<li>Amazon Q Developer enabled for engineering teams in supported IDEs.<\/li>\n<li>CloudTrail and central logging for audit and governance (verify exact logging coverage).<\/li>\n<li><strong>Why Amazon Q was chosen:<\/strong><\/li>\n<li>Enterprise identity integration and governance alignment with AWS.<\/li>\n<li>Managed service reduces operational burden compared to building a custom assistant.<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Reduced time to locate procedures and compliance guidance.<\/li>\n<li>Faster incident resolution.<\/li>\n<li>Improved onboarding through consistent answers grounded in approved docs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: SaaS company with a small platform team<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A small team ships quickly but struggles with consistent IaC, code quality, and operational readiness.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>Amazon Q Developer enabled in VS Code for all engineers.<\/li>\n<li>Internal \u201cgolden path\u201d templates maintained in a Git repo; Amazon Q Developer used to generate and explain patterns.<\/li>\n<li>Lightweight governance: code review + CI tests + secret scanning.<\/li>\n<li><strong>Why Amazon Q was chosen:<\/strong><\/li>\n<li>Fast productivity gains with minimal infrastructure.<\/li>\n<li>Lower effort than standing up a custom internal assistant.<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Faster delivery of well-tested features.<\/li>\n<li>Better code consistency and fewer production issues caused by basic mistakes.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<p>1) <strong>Is Amazon Q one service or multiple products?<\/strong><br\/>\nAmazon Q is a brand that includes multiple offerings (for example, Amazon Q Developer and Amazon Q Business), plus \u201cAmazon Q\u201d experiences embedded in some AWS products. Always confirm which offering you\u2019re deploying.<\/p>\n\n\n\n<p>2) <strong>What\u2019s the difference between Amazon Q Developer and Amazon Q Business?<\/strong><br\/>\nAmazon Q Developer focuses on software development and AWS engineering workflows (often inside IDEs). Amazon Q Business focuses on enterprise knowledge Q&amp;A grounded in internal content sources with access controls.<\/p>\n\n\n\n<p>3) <strong>Is Amazon CodeWhisperer still a thing?<\/strong><br\/>\nAmazon CodeWhisperer branding has been incorporated into Amazon Q Developer. If you see older references, treat them as legacy naming and verify the current Amazon Q Developer documentation.<\/p>\n\n\n\n<p>4) <strong>Does Amazon Q train on my company\u2019s data?<\/strong><br\/>\nAWS provides product-specific statements about data usage and training. The exact policy depends on the offering and configuration. <strong>Verify in the official Amazon Q documentation and service terms<\/strong> for your offering.<\/p>\n\n\n\n<p>5) <strong>Can Amazon Q access my private S3 documents?<\/strong><br\/>\nWith Amazon Q Business, you can connect content sources such as S3 (and others) using supported connectors and permissions mapping. You must configure access control correctly so users only see authorized content.<\/p>\n\n\n\n<p>6) <strong>Can I restrict Amazon Q to a private VPC-only endpoint?<\/strong><br\/>\nNetworking options vary by offering. <strong>Verify<\/strong> whether your Amazon Q offering supports private connectivity (for example, AWS PrivateLink). If not, rely on identity controls and egress controls.<\/p>\n\n\n\n<p>7) <strong>Do I need IAM Identity Center to use Amazon Q?<\/strong><br\/>\nEnterprise deployments commonly use IAM Identity Center. Some Amazon Q Developer setups may also support AWS Builder ID for individuals. Requirements vary\u2014verify in docs.<\/p>\n\n\n\n<p>8) <strong>How do I prevent sensitive data from being exposed in answers?<\/strong><br\/>\nUse least privilege, correct group mapping, connector scoping, and user training. Start with curated sources and expand carefully. Establish an acceptable use policy and audit processes.<\/p>\n\n\n\n<p>9) <strong>Is Amazon Q a replacement for Amazon Bedrock?<\/strong><br\/>\nNo. Amazon Bedrock is for building your own genAI apps. Amazon Q is a managed assistant experience. They can be complementary, but they solve different problems.<\/p>\n\n\n\n<p>10) <strong>Is Amazon Q good for production incident response?<\/strong><br\/>\nIt can help by improving access to runbooks and troubleshooting guidance, but it does not replace operational discipline. Validate outputs and ensure runbooks and permissions are accurate.<\/p>\n\n\n\n<p>11) <strong>What are the biggest cost drivers?<\/strong><br\/>\nTypically the number of users (subscription), tier selection, and (for knowledge offerings) indexing\/connector scope and usage. Validate your offering\u2019s pricing dimensions on the official pricing page.<\/p>\n\n\n\n<p>12) <strong>Can Amazon Q generate CloudFormation\/Terraform?<\/strong><br\/>\nAmazon Q Developer can often help draft IaC templates, but you must validate them against best practices, security requirements, and your organization\u2019s standards.<\/p>\n\n\n\n<p>13) <strong>How do I measure success for an Amazon Q rollout?<\/strong><br\/>\nTrack adoption, time saved, reduction in repeated questions, reduced incident resolution time, onboarding time reduction, and user satisfaction\u2014plus security metrics (access review findings).<\/p>\n\n\n\n<p>14) <strong>What\u2019s the best way to start?<\/strong><br\/>\nStart with Amazon Q Developer for a small engineering pilot (easy adoption) or Amazon Q Business for a specific knowledge domain (IT support, onboarding). Define success criteria and expand iteratively.<\/p>\n\n\n\n<p>15) <strong>What should we avoid during rollout?<\/strong><br\/>\nAvoid indexing everything, granting broad access, and skipping governance. Don\u2019t treat responses as authoritative without validation.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn Amazon Q<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Resource Type<\/th>\n<th>Name<\/th>\n<th>Why It Is Useful<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Official documentation<\/td>\n<td>Amazon Q Developer User Guide<\/td>\n<td>Canonical setup and feature documentation for Amazon Q Developer. https:\/\/docs.aws.amazon.com\/amazonq\/latest\/qdeveloper-ug\/what-is.html<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>Amazon Q Business User Guide<\/td>\n<td>Canonical setup and admin documentation for Amazon Q Business. https:\/\/docs.aws.amazon.com\/amazonq\/latest\/qbusiness-ug\/what-is.html<\/td>\n<\/tr>\n<tr>\n<td>Official product page<\/td>\n<td>Amazon Q (overview)<\/td>\n<td>High-level entry point and links to specific offerings. https:\/\/aws.amazon.com\/q\/<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>Amazon Q Developer pricing<\/td>\n<td>Current tiers and pricing dimensions for Amazon Q Developer. https:\/\/aws.amazon.com\/q\/developer\/pricing\/<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>Amazon Q Business pricing<\/td>\n<td>Current tiers and pricing dimensions for Amazon Q Business. https:\/\/aws.amazon.com\/q\/business\/pricing\/<\/td>\n<\/tr>\n<tr>\n<td>Pricing tool<\/td>\n<td>AWS Pricing Calculator<\/td>\n<td>Build region-specific estimates based on your expected usage. https:\/\/calculator.aws\/#\/<\/td>\n<\/tr>\n<tr>\n<td>Official architecture<\/td>\n<td>AWS Architecture Center<\/td>\n<td>Find reference architectures and security guidance to complement Amazon Q deployments. https:\/\/aws.amazon.com\/architecture\/<\/td>\n<\/tr>\n<tr>\n<td>Official security<\/td>\n<td>AWS CloudTrail<\/td>\n<td>Understand auditing capabilities across AWS services. https:\/\/docs.aws.amazon.com\/awscloudtrail\/latest\/userguide\/cloudtrail-user-guide.html<\/td>\n<\/tr>\n<tr>\n<td>Official identity<\/td>\n<td>IAM Identity Center<\/td>\n<td>SSO patterns commonly used with Amazon Q in enterprises. https:\/\/docs.aws.amazon.com\/singlesignon\/latest\/userguide\/what-is.html<\/td>\n<\/tr>\n<tr>\n<td>Official tooling<\/td>\n<td>AWS Toolkit for VS Code<\/td>\n<td>How to install and use AWS Toolkit, which integrates Amazon Q Developer in supported setups. https:\/\/docs.aws.amazon.com\/toolkit-for-vscode\/latest\/userguide\/welcome.html<\/td>\n<\/tr>\n<tr>\n<td>Official videos<\/td>\n<td>AWS YouTube Channel<\/td>\n<td>Search for Amazon Q sessions, demos, and re:Invent talks (content changes over time). https:\/\/www.youtube.com\/@amazonwebservices<\/td>\n<\/tr>\n<tr>\n<td>Reputable community<\/td>\n<td>AWS re:Post<\/td>\n<td>Practical Q&amp;A from AWS engineers and customers; validate against official docs. https:\/\/repost.aws\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">18. Training and Certification Providers<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Institute<\/th>\n<th>Suitable Audience<\/th>\n<th>Likely Learning Focus<\/th>\n<th>Mode<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps engineers, SREs, developers, architects<\/td>\n<td>AWS tooling, DevOps practices, cloud labs; may include Amazon Q Developer productivity workflows<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>ScmGalaxy.com<\/td>\n<td>Developers, DevOps, release engineers<\/td>\n<td>SCM\/CI\/CD, automation, cloud tooling; may include AWS integrations<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.scmgalaxy.com\/<\/td>\n<\/tr>\n<tr>\n<td>CLoudOpsNow.in<\/td>\n<td>Cloud operations teams, platform engineers<\/td>\n<td>Cloud operations, governance, best practices<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.cloudopsnow.in\/<\/td>\n<\/tr>\n<tr>\n<td>SreSchool.com<\/td>\n<td>SREs, reliability engineers, operations<\/td>\n<td>SRE practices, incident response, observability; potential fit for Amazon Q operational use cases<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.sreschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>AiOpsSchool.com<\/td>\n<td>Operations + AI automation learners<\/td>\n<td>AIOps concepts, operational automation, AI-assisted workflows<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.aiopsschool.com\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Platform\/Site<\/th>\n<th>Likely Specialization<\/th>\n<th>Suitable Audience<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>RajeshKumar.xyz<\/td>\n<td>Cloud\/DevOps training content (verify specific offerings on site)<\/td>\n<td>Engineers seeking practical cloud\/DevOps guidance<\/td>\n<td>https:\/\/rajeshkumar.xyz\/<\/td>\n<\/tr>\n<tr>\n<td>devopstrainer.in<\/td>\n<td>DevOps training and coaching (verify course catalog)<\/td>\n<td>DevOps engineers, SREs, CI\/CD practitioners<\/td>\n<td>https:\/\/www.devopstrainer.in\/<\/td>\n<\/tr>\n<tr>\n<td>devopsfreelancer.com<\/td>\n<td>Freelance DevOps help\/training platform (verify services offered)<\/td>\n<td>Teams needing short-term enablement<\/td>\n<td>https:\/\/www.devopsfreelancer.com\/<\/td>\n<\/tr>\n<tr>\n<td>devopssupport.in<\/td>\n<td>DevOps support and training resources (verify offerings)<\/td>\n<td>Operations teams and DevOps practitioners<\/td>\n<td>https:\/\/www.devopssupport.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Company<\/th>\n<th>Likely Service Area<\/th>\n<th>Where They May Help<\/th>\n<th>Consulting Use Case Examples<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cotocus.com<\/td>\n<td>Cloud\/DevOps consulting (verify exact focus areas)<\/td>\n<td>Cloud architecture, DevOps automation, governance<\/td>\n<td>Amazon Q rollout planning, IAM Identity Center integration approach, pilot success metrics<\/td>\n<td>https:\/\/cotocus.com\/<\/td>\n<\/tr>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>Training + consulting services (verify consulting offerings)<\/td>\n<td>Enablement, platform practices, DevOps transformations<\/td>\n<td>Developer productivity pilot using Amazon Q Developer; operational readiness and best practices<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>DEVOPSCONSULTING.IN<\/td>\n<td>DevOps consulting (verify service catalog)<\/td>\n<td>CI\/CD, cloud operations, SRE practices<\/td>\n<td>Governance model for AI assistants, secure development workflows using Amazon Q Developer<\/td>\n<td>https:\/\/www.devopsconsulting.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">21. Career and Learning Roadmap<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn before Amazon Q<\/h3>\n\n\n\n<p>To use Amazon Q effectively (especially in enterprise settings), you should understand:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>AWS fundamentals<\/strong>: IAM, regions, basic networking, CloudTrail basics.<\/li>\n<li><strong>Security basics<\/strong>: least privilege, identity federation\/SSO, data classification.<\/li>\n<li><strong>Developer tooling<\/strong> (for Amazon Q Developer): Git, CI\/CD basics, unit testing, code review practices.<\/li>\n<li><strong>Knowledge management<\/strong> (for Amazon Q Business): content lifecycle, doc ownership, permissions models.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after Amazon Q<\/h3>\n\n\n\n<p>Once you are comfortable with Amazon Q, expand into:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Amazon Bedrock<\/strong> for building custom generative AI apps (RAG pipelines, agents).<\/li>\n<li><strong>Enterprise governance for AI<\/strong> (policies, risk management, evaluation).<\/li>\n<li><strong>Observability<\/strong> (CloudWatch, OpenTelemetry patterns) for operational excellence.<\/li>\n<li><strong>Secure SDLC<\/strong> (SAST\/DAST, secrets scanning, policy-as-code).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Job roles that use it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Engineer \/ Platform Engineer<\/li>\n<li>DevOps Engineer \/ SRE<\/li>\n<li>Solutions Architect<\/li>\n<li>Software Engineer<\/li>\n<li>Security Engineer (governance and secure coding enablement)<\/li>\n<li>IT Knowledge Manager \/ IT Ops (for Q Business use cases)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>AWS certifications are not \u201cAmazon Q-specific\u201d today in the same way some services are, but Amazon Q knowledge aligns well with:\n&#8211; AWS Certified Solutions Architect (Associate\/Professional)\n&#8211; AWS Certified Developer (Associate)\n&#8211; AWS Certified Security (Specialty)<\/p>\n\n\n\n<p>If AWS introduces Amazon Q\u2013specific learning badges or certifications, <strong>verify on AWS Training and Certification<\/strong>: https:\/\/aws.amazon.com\/training\/<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Developer workflow project:<\/strong> Use Amazon Q Developer to generate unit tests and refactor a small repo; enforce formatting and CI checks.<\/li>\n<li><strong>IaC project:<\/strong> Generate a baseline CloudFormation template with security defaults; validate with cfn-lint and security scanning.<\/li>\n<li><strong>Knowledge pilot:<\/strong> Curate a small set of internal docs (in S3) and define a governance process for doc ownership and updates (for Q Business\u2014verify connector\/config steps).<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Amazon Q Developer:<\/strong> Amazon Q offering focused on developer and engineering workflows (IDE assistance, code generation\/explanation, AWS troubleshooting guidance).<\/li>\n<li><strong>Amazon Q Business:<\/strong> Amazon Q offering focused on enterprise knowledge Q&amp;A grounded in internal content sources with access control.<\/li>\n<li><strong>AWS Builder ID:<\/strong> An identity option often used by individual developers for AWS developer tools. Availability for Amazon Q Developer features\/tiering must be verified in current docs.<\/li>\n<li><strong>IAM (Identity and Access Management):<\/strong> AWS service for permissions management (users, roles, policies).<\/li>\n<li><strong>IAM Identity Center:<\/strong> AWS service for workforce identity federation and SSO (formerly AWS SSO).<\/li>\n<li><strong>RAG (Retrieval-Augmented Generation):<\/strong> Pattern that retrieves relevant documents and uses them to ground model responses.<\/li>\n<li><strong>Least privilege:<\/strong> Security principle that grants only the permissions required to perform a task.<\/li>\n<li><strong>Connector:<\/strong> Integration that synchronizes content from a source system into a knowledge assistant index (Q Business), typically with ACL mapping.<\/li>\n<li><strong>CloudTrail:<\/strong> AWS service for auditing API calls and certain account activity.<\/li>\n<li><strong>KMS (Key Management Service):<\/strong> AWS service to create and manage encryption keys (customer-managed or AWS-managed, depending on service support).<\/li>\n<li><strong>IDE:<\/strong> Integrated Development Environment (for example, VS Code, JetBrains).<\/li>\n<li><strong>IaC (Infrastructure as Code):<\/strong> Managing infrastructure using code (CloudFormation, Terraform).<\/li>\n<li><strong>SaaS:<\/strong> Software as a Service\u2014vendor-hosted application delivered via the internet.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>Amazon Q is AWS\u2019s generative AI assistant family within the Machine Learning (ML) and Artificial Intelligence (AI) category, designed to help developers and business users get answers and complete tasks faster. <strong>Amazon Q Developer<\/strong> targets engineering productivity (especially inside IDEs), while <strong>Amazon Q Business<\/strong> targets enterprise knowledge Q&amp;A grounded in approved content sources with access controls.<\/p>\n\n\n\n<p>From an architecture standpoint, Amazon Q is a managed, identity-aware assistant: your primary design work is <strong>governance, permissions, content quality, and rollout planning<\/strong>, not model hosting. From a cost standpoint, expect <strong>subscription-style pricing<\/strong> (often per user) and plan for indirect costs like content curation, connector administration, and organizational change management. From a security standpoint, prioritize <strong>least privilege<\/strong>, careful connector scoping, and clear policies about what data users may paste into prompts.<\/p>\n\n\n\n<p>Use Amazon Q when you want an AWS-managed assistant experience with enterprise controls. If you need deep customization and full control, consider building on <strong>Amazon Bedrock<\/strong> instead.<\/p>\n\n\n\n<p><strong>Next learning step:<\/strong> Run the hands-on lab above with Amazon Q Developer in VS Code, then read the official documentation for your chosen Amazon Q offering and validate region availability, security controls, and pricing before scaling to production.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Machine Learning (ML) and Artificial Intelligence (AI)<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20,32],"tags":[],"class_list":["post-249","post","type-post","status-publish","format-standard","hentry","category-aws","category-machine-learning-ml-and-artificial-intelligence-ai"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/249","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=249"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/249\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=249"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}