# Amazon Q

Amazon Q is an AWS family of generative AI assistants for software development, AWS operations, and enterprise information retrieval.

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/amazon-q

> Amazon Q helps engineers build and operate applications and helps employees find answers in organizational content. Its principal offerings, Q Developer and Q Business, have different deployment models, permissions, data sources, and billing structures.

Practice exams covering Amazon Q: [AIB-C01 (beta) AWS Certified AI Business Strategist](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist), [AIF-C01 AWS Certified AI Practitioner](https://blowstack.com/practice-exams/aws-certified-ai-practitioner), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional).

## 10 key features of Amazon Q

1. **Code assistance in development environments**: Q Developer can generate code suggestions, explain existing code, and help create tests in supported IDEs. Review generated changes against repository conventions and run tests before merging.
2. **Multi-step development assistance**: Supported Q Developer capabilities can investigate a codebase and propose or implement changes across files. Use version control and inspect the resulting diff before accepting a task's output.
3. **AWS troubleshooting guidance**: Q Developer can explain AWS concepts and assist with troubleshooting in supported AWS interfaces. Resource-aware assistance depends on the interface, available context, and the user's permissions.
4. **Enterprise content retrieval**: Q Business can retrieve information from configured organizational sources to answer employee questions. Configure ingestion and synchronization to keep searchable information aligned with source systems.
5. **Source references**: Q Business can include references to retrieved content in its answers. Use those references to check whether an answer is supported and whether the underlying document is current.
6. **Identity-aware document access**: Q Business supports permission-aware retrieval using configured identities and supported source access controls. Test user and group mappings so documents are not exposed to unauthorized employees.
7. **Actions through configured integrations**: Q Business supports plugins for interacting with supported external systems. Limit action permissions and test confirmation behavior before allowing workflows that create or update business records.
8. **Supported code transformations**: Q Developer offers transformation capabilities for supported modernization scenarios, including selected Java upgrades. Check language and project eligibility, then validate transformed applications with builds, tests, and dependency checks.
9. **Built-in indexing pipeline**: Q Business provides a built-in pipeline for indexing data in a vector database, with optional preprocessing logic supplied through an AWS Lambda function.
10. **Global and topic-level guardrails**: Q Business supports global and topic-level controls that can detect personally identifiable information, abuse, or sensitive information in prompts.

## Where Amazon Q is used

1. **Understand and modify an unfamiliar repository**: Use Q Developer to explain modules, trace application behavior, and draft changes or tests. Verify its interpretation against actual code paths and automated test results.
2. **Investigate AWS operational problems**: Ask Q Developer for help interpreting errors or identifying relevant diagnostic steps. Supply appropriate context without secrets, and validate proposed remediation before changing production resources.
3. **Search internal engineering knowledge**: Connect Q Business to runbooks, architecture documents, and operating procedures so engineers can ask questions across approved sources. Preserve document permissions and monitor synchronization health.
4. **Support employee self-service**: Use Q Business to answer questions about internal policies or support procedures with references to authoritative documents. Establish an escalation path for missing, conflicting, or sensitive answers.
5. **Assist application modernization**: Apply eligible Q Developer transformation workflows to supported application upgrades. Run compatibility testing and performance checks before deploying the transformed application.

## How Amazon Q is priced

- **Q Developer Free tier**: A free tier provides access to selected development assistance capabilities with usage limits. Features, authentication requirements, and quotas vary by interface and capability.
- **Q Developer Pro subscription**: Pro is generally billed per subscribed user and adds higher limits and organizational capabilities. Check the applicable entitlements and any capability-specific usage charges when estimating costs.
- **Q Business user subscriptions**: Q Business uses user subscription tiers, including Lite and Pro, with different feature entitlements. Select tiers according to the experiences each user needs rather than assuming all application users require the same subscription.
- **Q Business index capacity**: Indexed Q Business deployments incur index capacity charges separately from user subscriptions. Size capacity for the supported document and workload limits, and account for index runtime even when query traffic is low.
- **Supporting resource charges**: Connected storage, encryption keys, logging, data transfer, and systems invoked by actions can incur their own charges. Include these resources in the total cost model rather than treating the assistant subscription as the entire deployment cost.

## Services Amazon Q works with

A common Q Business architecture uses IAM Identity Center for workforce access, an indexed document collection for retrieval, and S3 as one of the source repositories. A dedicated ingestion role reads only approved objects, while source metadata and identity mappings determine which documents individual users may retrieve. These are separate controls: allowing the service to ingest a document does not automatically mean every application user should see it.

Manage supported application resources with CloudFormation to make environments reproducible and changes reviewable. Keep connector credentials and authorization steps outside plain-text templates, and account for source synchronization when planning releases. Where customer-managed encryption keys are required, configure KMS permissions alongside application and ingestion permissions, then test both normal access and failure scenarios.

Q Developer follows a different integration pattern: developers access the assistant through supported IDEs or AWS interfaces, with organizational subscriptions and AWS permissions managed separately. Do not assume that Q Developer automatically uses a Q Business index. For either offering, separate development and production permissions, validate generated recommendations, and include subscriptions and supporting services in cost monitoring.

- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Q Business can ingest documents from an Amazon S3 data source. For example, publish approved operational runbooks to a dedicated bucket and synchronize them into the application's index. Restrict the connector role to the required bucket and prefixes, and configure document metadata and access controls where needed.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: CloudFormation supports Q Business resource types that can be used to manage supported application infrastructure declaratively. For example, maintain an application, index, retriever, and supported data source configuration in reviewed templates. Check resource coverage and handle identity assignments or connector authorization separately where the template does not manage them.
- **[Amazon Aurora](https://blowstack.com/tools/cloud-services-hub/amazon-aurora)**: Amazon Q Business can index content from supported Amazon Aurora databases through its database connectors. Users can then ask questions about the indexed information alongside content from other connected sources.
- **[Amazon Bedrock](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock)**: Amazon Q Business uses foundation models supported by Amazon Bedrock to generate answers grounded in enterprise content.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Amazon Q Business publishes operational metrics and connector synchronization logs to Amazon CloudWatch. Amazon Q Developer also helps generate CloudWatch Logs Insights queries and investigate operational problems using CloudWatch telemetry.
- **[Amazon Connect](https://blowstack.com/tools/cloud-services-hub/amazon-connect)**: Amazon Q in Connect uses customer conversations and connected knowledge sources to recommend answers and actions to contact center agents. It can provide relevant guidance while an agent is handling a customer interaction.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Amazon Q Developer provides EC2 instance-type recommendations based on workload requirements and helps investigate EC2 resource configurations. Its console-to-code capability can also turn recorded EC2 console actions into reusable deployment code.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: Amazon Q Developer helps troubleshoot ECS workloads by examining deployment information, task configuration, and related operational data. For example, it can help investigate why a task failed to start.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: Amazon Q Developer provides troubleshooting assistance for EKS workloads using Kubernetes resource information and related AWS operational context. It can help investigate unhealthy workloads and explain relevant configuration issues.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: Amazon Q Developer's Apache Spark upgrade capabilities help modernize Spark applications that run on Amazon EMR. It can analyze application code and propose changes needed for a newer Spark version.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: Amazon Q Developer in chat applications can deliver EventBridge events to configured chat channels through Amazon SNS. EventBridge input transformations can format events into custom notifications with useful context and links.
- **[Amazon FSx](https://blowstack.com/tools/cloud-services-hub/amazon-fsx-(for-all-types))**: Amazon Q Business provides a connector for Amazon FSx for Windows File Server. It indexes files and their access-control information so answers can respect users' permissions.
- **[Amazon GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-guardduty)**: Amazon Q Developer in chat applications can deliver GuardDuty finding notifications to chat channels through supported notification routes. Teams can review the finding and use authorized AWS commands to investigate from the conversation.
- **[Amazon Kendra](https://blowstack.com/tools/cloud-services-hub/amazon-kendra)**: Amazon Q Business can use an existing Amazon Kendra index as its retriever instead of creating a native Amazon Q index. This lets a Q application answer questions using content already indexed in Kendra.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: Amazon Q Developer in OpenSearch Service helps users explore operational data with natural-language queries and generated Piped Processing Language queries. It also provides assistance with OpenSearch concepts and troubleshooting.
- **[Amazon QuickSight](https://blowstack.com/tools/cloud-services-hub/amazon-quicksight)**: Amazon Q in QuickSight supports natural-language questions, dashboard authoring, and generated data narratives. Amazon Q Business can also integrate with QuickSight to combine enterprise knowledge with insights from structured business data.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Amazon Q Business can connect to supported databases hosted on Amazon RDS and index selected database content. Users can ask natural-language questions about that content through their Q Business application.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: Amazon Q generative SQL in the Redshift query editor helps users create and refine SQL from natural-language requests. It uses database context to help produce queries appropriate to the available tables.
- **[Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker)**: Amazon Q Developer is available in SageMaker Studio to assist with machine learning development. It can generate and explain code and help troubleshoot errors within the development environment.
- **[Amazon Simple Notification Service (Amazon SNS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-notification-service-(amazon-sns))**: Amazon Q Developer in chat applications subscribes to SNS topics to deliver AWS notifications to configured chat channels. For example, an SNS topic can forward CloudWatch alarm notifications to an operations channel.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Amazon Q Business supports VPC-connected data sources so its connectors can reach resources in private subnets. Security groups and subnet configuration control the connector's network access.
- **[AWS Billing and Cost Management](https://blowstack.com/tools/cloud-services-hub/aws-billing-and-cost-management)**: Amazon Q Developer's cost-analysis capabilities answer natural-language questions about AWS spending using billing and cost data. Users can ask about spending changes and investigate the services or accounts contributing to them.
- **[AWS Budgets](https://blowstack.com/tools/cloud-services-hub/aws-budgets)**: Amazon Q Developer in chat applications can receive AWS Budgets notifications through Amazon SNS. This brings budget thresholds and spending alerts into the team's chat channel.
- **[AWS Chatbot](https://blowstack.com/tools/cloud-services-hub/aws-chatbot)**: Amazon Q Developer can be enabled in chat channels configured through AWS Chatbot, providing conversational AWS assistance alongside notifications and authorized AWS commands.
- **[AWS Cloud9](https://blowstack.com/tools/cloud-services-hub/aws-cloud9)**: Amazon Q Developer's code-suggestion capabilities are available in AWS Cloud9. Developers can receive inline code recommendations while working in the browser-based development environment.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: Amazon Q API activity can be recorded in AWS CloudTrail for auditing. Amazon Q Developer operational investigations can also use CloudTrail events to identify changes that may explain an incident.
- **[AWS CodeConnections](https://blowstack.com/tools/cloud-services-hub/aws-codeconnections)**: Amazon Q Developer can use AWS CodeConnections to access supported source-code repositories for code customizations. These customizations adapt code recommendations to an organization's internal libraries and conventions.
- **[AWS Compute Optimizer](https://blowstack.com/tools/cloud-services-hub/aws-compute-optimizer)**: Amazon Q Developer can surface Compute Optimizer recommendations when helping users investigate resource efficiency and cost optimization. This helps connect a natural-language cost question with concrete rightsizing opportunities.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: Amazon Q Developer operational investigations use AWS Config resource configuration and relationship information to understand affected infrastructure. This context helps connect symptoms with related resources and configuration changes.
- **[AWS Cost Explorer](https://blowstack.com/tools/cloud-services-hub/aws-cost-explorer)**: Amazon Q Developer uses Cost Explorer capabilities to answer questions about AWS costs and usage. For example, it can break down a spending increase by service or compare costs across time periods.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: Amazon Q Developer in AWS Glue helps generate and explain data integration code and troubleshoot ETL jobs. Users can describe a transformation in natural language or request help diagnosing a failed job.
- **[AWS Health Dashboard](https://blowstack.com/tools/cloud-services-hub/aws-health-dashboard)**: Amazon Q Developer operational investigations can incorporate AWS Health events when assessing service disruptions. Amazon Q Developer in chat applications can also deliver AWS Health notifications to configured channels.
- **[AWS IAM Identity Center (AWS Single Sign-On)](https://blowstack.com/tools/cloud-services-hub/aws-iam-identity-center-(aws-single-sign-on))**: Amazon Q Business integrates with IAM Identity Center to authenticate users and manage application access. Amazon Q Developer Pro also uses IAM Identity Center for workforce sign-in and subscription assignment.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: Amazon Q uses IAM roles and policies to control administrative actions and access to connected AWS resources. For example, a Q Business connector assumes a role granting access only to its designated data source.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: Amazon Q Business supports customer-managed KMS keys for encrypting application data. Key policies determine whether the service can use the key to protect and retrieve that data.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: Amazon Q Business can invoke Lambda functions during document enrichment to transform or augment documents before indexing. For example, a function can normalize document content or add metadata used for retrieval.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: Amazon Q Developer supports organization-level administration through AWS Organizations. Administrators can apply supported organizational controls across member accounts rather than configuring each account separately.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: Amazon Q Business supports interface VPC endpoints through AWS PrivateLink. Applications can use these endpoints to access supported Q Business APIs without routing traffic through an internet gateway.
- **[AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager)**: Amazon Q Business connectors retrieve data-source credentials from AWS Secrets Manager. This keeps database passwords and other connector authentication secrets out of application configuration.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: Amazon Q Developer in chat applications can send Security Hub finding notifications to configured chat channels. Security teams can review findings and use authorized AWS commands from the same conversation.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: Amazon Q Business uses STS temporary credentials for role-based access, including identity-aware access patterns. Trusted identity propagation can carry a user's Identity Center context into calls to Q Business.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: Amazon Q Developer in chat applications supports running Systems Manager Automation runbooks through configured actions and permissions. Teams can use chat-based actions to perform operational tasks without leaving an incident conversation.
- **[AWS Trusted Advisor](https://blowstack.com/tools/cloud-services-hub/aws-trusted-advisor)**: Amazon Q Developer in chat applications supports Trusted Advisor notifications, bringing relevant check results into team channels. Teams can use these alerts to follow up on recommended improvements to their AWS resources.
- **[AWS User Notifications](https://blowstack.com/tools/cloud-services-hub/aws-user-notifications)**: AWS User Notifications can deliver notifications to Amazon Q Developer in chat applications. This lets teams receive centrally configured AWS event notifications in their chat channels.
- **[AWS WAF](https://blowstack.com/tools/cloud-services-hub/aws-waf)**: Amazon Q Business web experiences can be protected with an AWS WAF web ACL. Administrators can apply request-filtering and rate-based rules to help protect the application's public endpoint.
- **[AWS X-Ray](https://blowstack.com/tools/cloud-services-hub/aws-x-ray)**: Amazon Q Developer operational investigations can use X-Ray traces and service relationships to investigate application problems. Trace context helps identify downstream dependencies associated with latency or errors.

## Amazon Q exam questions

Real practice exam questions on Amazon Q, with the correct answer and its explanation.

### Question 1 (AIB-C01 (beta))

**Question:**

A software company wants to shorten the time needed to deliver maintenance updates. An assessment finds that developers spend most of this time understanding unfamiliar code and writing unit tests, rather than waiting for deployment approvals. The company wants to pilot an AI capability within its existing development environments without building a custom AI application. All proposed code changes must continue to pass developer review, security checks, and automated tests. Which initiative and success measure BEST align with the business objective?

**Correct answer:** Use Amazon Q Developer to explain unfamiliar code and propose unit tests, retaining existing review and release controls; measure median time from starting a maintenance change to release readiness while ensuring escaped defects do not increase.

**Explanation:** Amazon Q Developer supports code explanation and test generation in supported development environments without requiring the company to build a custom assistant. Measuring time to release readiness connects these capabilities to the delivery objective, while the defect measure helps ensure that speed does not come at the expense of quality.

### Question 2 (DVA-C02)

**Question:**

A developer uses Amazon Q Developer to generate tests for a Python shipping-cost calculator. All tests pass, and the CI coverage report shows 100% line coverage. A review finds that the tests execute each conditional expression but never exercise several alternative outcomes, including the surcharge for oversized packages. The team requires at least 90% coverage of decision outcomes before deployment. Which approach should the developer use?

**Correct answer:** Ask Amazon Q Developer to generate additional tests for uncovered decision outcomes with assertions for expected charges. Enable branch measurement in the coverage tool and configure the test command to fail below 90% branch coverage, preserving its failing exit status in CI.

**Explanation:** Branch coverage measures whether alternative decision outcomes are exercised, exposing gaps that line coverage can miss. Amazon Q Developer can help generate targeted tests, while assertions check expected behavior. An enforced branch-coverage threshold and an unmasked failure status prevent deployment when the requirement is not met.

### Question 3 (AIP-C01)

**Question:**

A company operates a tool-calling assistant that retrieves account information from several internal APIs concurrently. After a refactor, the assistant occasionally associates a valid tool result with the wrong pending tool call. All API requests succeed, and each result passes schema validation. Sequential execution does not reproduce the problem, but disabling concurrency would violate the application's latency requirement.

Engineers have identified affected requests in CloudWatch Logs Insights and created sanitized fixtures that reproduce different tool-completion orders. They need to accelerate a source-level fix across the orchestration, dispatch, and response-assembly modules while retaining concurrent execution. All changes must pass code review and automated regression testing.

Which approach best meets these requirements?

**Correct answer:** Use Amazon Q Developer in the IDE with the relevant repository files and sanitized fixtures. Ask it to trace tool-call identifier propagation, propose a targeted fix, and generate regression tests for different completion orders. Review the diff and run the tests before deployment.

**Explanation:** Amazon Q Developer can use source-code context and supplied failure evidence to help investigate cross-module behavior, propose implementation changes, and write tests. Checking identifier propagation addresses the association between each invocation and its result without sacrificing concurrency. Tests covering different completion orders verify the required invariant, while review and execution of the tests validate the generated changes.

### Question 4 (AIF-C01)

**Question:**

A company wants employees to describe IT problems in natural language to a managed workplace assistant. The assistant must draft a service ticket from the conversation and, after the employee confirms, create the issue in the company's Jira Cloud system. The company wants an existing assistant with a supported integration rather than a custom chatbot or model-based application. Which solution best meets these requirements?

**Correct answer:** Use Amazon Q Business with a supported Jira plugin configured to create issues.

**Explanation:** Amazon Q Business is a managed workplace generative AI assistant. Its supported Jira integration can let employees create issues through conversation, with confirmation before submission, without building a custom chatbot.

### Question 5 (CLF-C02)

**Question:**

A company's employees spend significant time searching internal policy documents across several enterprise repositories. The company wants a managed generative AI assistant that answers employees' questions using these documents, provides references to the source material, and respects each employee's document access permissions. Which solution meets these requirements with the least custom development?

**Correct answer:** Use Amazon Q Business with supported repository connectors and configure employee identities and document-level access controls.

**Explanation:** Amazon Q Business provides a managed generative AI assistant grounded in organizational content. Supported connectors can ingest documents and their access controls, enabling answers with source references while restricting retrieved content according to employee permissions.

## Practice Amazon Q in a full exam

Questions on Amazon Q in each practice exam, with every answer option and an explanation for each:

- [AIF-C01](https://blowstack.com/practice-exams/aws-certified-ai-practitioner): 5 questions
- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 4 questions
- [AIP-C01](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional): 3 questions
- [AIB-C01 (beta)](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist): 2 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 1 question

## What is Amazon Q

Amazon Q is a family of generative AI assistants rather than a single endpoint with one configuration model. For engineering teams, the main distinction is between Q Developer, which supports software development and AWS workflows, and Q Business, which provides an enterprise assistant grounded in organizational information. Amazon Q has been in maintenance since June 30, 2026: it is closed to new customers, while existing customers can continue using it.

Q Developer is available through supported development environments and AWS interfaces. Engineers can use it to explain unfamiliar code, generate implementation suggestions, write tests, investigate errors, and obtain guidance about AWS resources. Certain capabilities can perform multi-step development tasks or assist with supported code transformations. Availability depends on the interface, subscription, programming language, and task. Treat generated code and infrastructure changes as proposed work: review the diff, run automated tests, and apply the same security and release controls used for human-authored changes.

The Q Developer experience in the AWS Management Console and AWS Console Mobile Application is now called the AWS assistant. Q Developer retains its name in IDEs and on the command line.

AWS will discontinue support for Amazon Q Developer IDE plugins on April 30, 2027.

Q Business is configured around an application, an identity setup, and access to enterprise content. A typical deployment connects repositories or object storage, configures ingestion and synchronization, and exposes a conversational interface to authorized employees. Responses can reference retrieved documents so users can inspect the material supporting an answer. Content freshness depends on successful ingestion and synchronization; changing a source document does not necessarily make that change immediately available in responses.

For retrieval, Q Business can use a provisioned native Q Business index with a Q Business retriever, or a preconfigured Amazon Kendra index as a retriever.

Q Business permits at most 50 applications per AWS account; this quota is not adjustable.

Q Business permits at most 50 data sources per application; this quota is not adjustable.

Authorization requires careful design. For Q Business, configure user and group identities and preserve supported document-level access controls when ingesting content. Validate access with representative users, particularly when connectors map identities across different systems. For Q Developer, distinguish the permissions needed to access the assistant from the AWS permissions needed to inspect resources or execute operations. An answer about an AWS service is not evidence that the caller is authorized to change that service.

Security and governance settings differ across offerings and subscription tiers. Review data handling, encryption, retention, supported administrative policies, and any settings controlling the use of content for service improvement before enabling sensitive workloads. Do not place credentials or secrets in prompts. Where actions or external integrations are enabled, restrict execution roles and require appropriate confirmation or approval for consequential changes.

Operate each deployment with measurable acceptance criteria. For Q Business, test retrieval quality, document permissions, synchronization failures, and citation relevance using a representative question set. For Q Developer, evaluate suggestion quality, test coverage, security findings, and developer workflow fit. Budget separately for subscriptions, indexed capacity where applicable, and supporting AWS resources. Generated answers can be incomplete or incorrect, so retain human review for production decisions.

## Learn Amazon Q in lessons

7 short lessons on Amazon Q in 4 certification courses.

- AIB-C01 (beta): Amazon Q: assistants for workplace productivity (Premium), https://app.blowstack.com/lessons/amazon-q-assistants-for-workplace-productivity-aib-c01
- AIP-C01: Amazon Q: context-guided development with Q Developer (Premium), https://app.blowstack.com/lessons/amazon-q-context-guided-development-with-q-developer-aip-c01
- AIF-C01: Amazon Q vs Amazon Bedrock (Premium), https://app.blowstack.com/lessons/amazon-q-vs-amazon-bedrock-aif-c01
- CLF-C02: Amazon Q: generative AI assistants (Premium), https://app.blowstack.com/lessons/amazon-q-generative-ai-assistants-clf-c02
- AIB-C01 (beta): Amazon Q and Amazon Bedrock: ready-made assistants or custom applications (Premium), https://app.blowstack.com/lessons/amazon-q-and-amazon-bedrock-ready-made-assistants-or-custom-applications-aib-c01
- AIP-C01: Amazon Q and Amazon CodeWhisperer: capability boundaries (Premium), https://app.blowstack.com/lessons/amazon-q-and-amazon-codewhisperer-capability-boundaries-aip-c01

## Concepts related to Amazon Q

- [Unit Testing](https://blowstack.com/tools/cloud-concepts-hub/unit-testing): Unit testing verifies the behavior of a small, independently testable piece of code while controlling its dependencies.
- [Code Refactoring](https://blowstack.com/tools/cloud-concepts-hub/code-refactoring): Code refactoring is the restructuring of existing source code to improve its internal design without changing its externally observable behavior.
- [Performance Profiling](https://blowstack.com/tools/cloud-concepts-hub/performance-profiling): Performance profiling measures how an application spends time and consumes resources to identify bottlenecks and guide targeted improvements.
- [Security Quality Gates](https://blowstack.com/tools/cloud-concepts-hub/security-quality-gates): Security quality gates are enforced checkpoints that allow software changes to advance only when defined security acceptance criteria are satisfied.
- [Shift-Left Security](https://blowstack.com/tools/cloud-concepts-hub/shift-left-security): Shift-left security integrates security design, testing, and remediation into the earliest practical stages of software development and delivery.
- [Static Application Security Testing](https://blowstack.com/tools/cloud-concepts-hub/static-application-security-testing): Static Application Security Testing analyzes application source code or compiled artifacts for security weaknesses without running the application.
