- Amazon Q Business - Workflow
- Amazon Q Business - Key Concepts
- Amazon Q Business - Subscription Tiers & Index Types
- Amazon Q Business - Service Quotas
- Amazon Q Business - Document Attributes
- Amazon Q Business - Setup
- Amazon Q Business - Identity Center Directory
- Amazon Q Business - Identity Center Integrated Application
- Amazon Q Business - Identity Federation Application
- Amazon Q Business - Data Sources Connectors
- Amazon Q Business - Enhance Application
- Amazon Q Business - Features
- Amazon Q Business - Security
- Amazon Q Business - Monitoring
- Amazon Q Business API Reference
- Amazon Q Business - API Overview
- Amazon Q Business - API References
- Amazon Q Business - Supported Actions
- Amazon Q Business - Supported Data Types
- Amazon Q Business - Common Parameters
- Amazon Q Business - Common Errors
- Amazon Q Developer User Guide
- Amazon Q Developer - Introduction
- Amazon Q Developer - Getting Started
- Amazon Q Developer - On AWS
- Amazon Q Developer - In IDE
- Amazon Q Developer - Command Line
- Amazon Q Developer - Customization
- Amazon Q Developer - Security
- Amazon Q Developer - Monitoring
- Amazon Q Developer - Supported Region & Service Rename
- Amazon Q Developer - Document History
Amazon Q Developer - Supported Region & Service Rename
Amazon Q Developer stores data in US-based AWS Regions, regardless of usage location. Conversations are stored in US East (N. Virginia), while troubleshooting data is stored in US West (Oregon) and IDE interaction data is stored in US East (N. Virginia).
AWS Regions And OPT Regions
You can access Amazon Q Developer through various platforms, including the AWS Management Console, AWS Console Mobile Application, AWS website, AWS Documentation website, and AWS Chatbot in the following AWS regions
| US Region. | Opt-in Regions |
|---|---|
| US East (Ohio) | Africa (Cape Town) |
| US East (N. Virginia) | Asia Pacific (Hong Kong) |
| US West (N. California) | Asia Pacific (Hyderabad) |
| US West (Oregon) | Asia Pacific (Jakarta) |
| Asia Pacific (Mumbai) | Asia Pacific (Melbourne) |
| Asia Pacific (Osaka) | Europe (Milan) |
| Asia Pacific (Seoul) | Europe (Spain) |
| Asia Pacific (Singapore) | Europe (Zurich) |
| Asia Pacific (Sydney) | Middle East (Bahrain) |
| Asia Pacific (Tokyo) | Middle East (UAE) |
| Canada (Central) | Israel (Tel Aviv) |
| Europe (Frankfurt) | |
| Europe (Ireland) | |
| Europe (London) | |
| Europe (Paris) | |
| Europe (Stockholm) | |
| South America (So Paulo) |
Q Developer Service Rename
As of April 30, 2024, Amazon CodeWhisperer is now part of Amazon Q Developer. This section will guide you to the relevant parts of this guide for documentation on features you previously used through CodeWhisperer.
When transitioning from CodeWhisperer to Amazon Q Developer, consider the following significant changes:
- The administrative setup at the professional tier (Amazon Q Developer Pro) is different than it was for CodeWhisperer Professional.
- You can chat with Amazon Q Developer in the AWS Management Console, and on the AWS documentation and marketing websites.
The following familiar features of CodeWhisperer are available as part of Amazon Q Developer, with a few changes:
- Coding suggestions in a third-party IDE
- Coding suggestions in the context of another AWS service
- Suggestions at the command line
- Customizations
- Security scans
- Dashboard