AWS Chatbot is now Amazon Q Developer. [Learn more](service-rename.md) # What is Amazon Q Developer in chat applications? Amazon Q Developer in chat applications enables DevOps and software development teams to use messaging program chat channels to monitor and respond to operational events in their AWS Cloud. Amazon Q Developer in chat applications processes AWS service notifications from Amazon Simple Notification Service (Amazon SNS), and forwards them to chat channels so teams can analyze and act on them immediately, regardless of location. Amazon Q Developer in chat applications also supports AWS CLI commands so you can manage AWS resources directly from your chat channels. **Topics** + [ ## Features of Amazon Q Developer in chat applications ](#chatbot-benefits) + [ ## How Amazon Q Developer in chat applications works ](#chatbot-works) + [ # Amazon Q Developer in chat applications rename - Summary of changes ](service-rename.md) + [ # Regions and quotas for Amazon Q Developer in chat applications ](chatbot-regions.md) + [ # Supported services for Amazon Q Developer in chat applications ](chatbot-services.md) + [ ## Amazon Q Developer in chat applications requirements ](#chatbot-requirements) + [ ## Accessing Amazon Q Developer in chat applications ](#chatbot-access) ## Features of Amazon Q Developer in chat applications Amazon Q Developer in chat applications enables ChatOps for AWS. *ChatOps* speeds software development and operations by enabling DevOps teams to use chat clients and chatbots to communicate and execute tasks. Amazon Q Developer in chat applications notifies chat users about events in their AWS services, so teams can collaboratively monitor and resolve issues in real time, instead of addressing emails from their SNS topics. Amazon Q Developer in chat applications also allows you to format incident metrics from Amazon CloudWatch as charts for viewing in chat notifications. Important features of the Amazon Q Developer in chat applications service include the following: + **Ask Amazon Q** – You can get Amazon Q Developer, Generative Artifical Intelligence (AI) assistant powered answers to your AWS questions directly in your chat channels. For more information about see [Chatting with Amazon Q Developer in chat channels](asking-questions.md). + **Supports Amazon Chime, Microsoft Teams, and Slack** – You can add Amazon Q Developer in chat applications to your Amazon Chime chat rooms, Microsoft Teams channels, or Slack channels in just a few clicks. + **Predefined AWS Identity and Access Management (IAM) policy templates** – Amazon Q Developer in chat applications provides chat room-specific permission controls through AWS Identity and Access Management (IAM). The available predefined templates make it easy to select and set up the permissions you want associated with a given channel or chat room. + **Receive notifications** – Use Amazon Q Developer in chat applications to receive notifications about operational incidents and other events from supported sources, such as operational alarms, security alerts, or budget deviations. To set up notifications in the Amazon Q Developer in chat applications console, choose the channels or chat rooms you want to receive notifications and then choose which Amazon Simple Notification Service (Amazon SNS) topics should trigger notifications. + **Customize notifications** – You can define and receive customized AWS service and application notifications directly in your chat channels. Custom notifications can be as succint or comprehensive you desire and use the same Amazon SNS-based mechanisms as default notifications. + **Create custom actions** – Custom actions transform your notifications into actionable items. A custom action appears as a button on your notifications. This button represents a Lambda function or CLI command that you define. You can use custom actions to retrieve telemetry information, run Lambda functions, run an automation runbook, and notify team members. When an issue arises, you can easily take action directly from your notifications. + **Monitor and manage AWS resources through the AWS CLI with Microsoft Teams and Slack** – Amazon Q Developer in chat applications supports CLI commands for most AWS services, making it easy to monitor and manage your AWS resources from your chat clients on desktop and mobile devices. Your teams can retrieve diagnostic information in real-time, change your AWS resources, run AWS SSM runbooks, and start long running jobs from a centralized location. Amazon Q Developer in chat applications commands use the standard AWS Command Line Interface syntax. + **Supports developer tools** – You can manage your Amazon Q Developer in chat applications resources using developer tools such as AWS software development kits (SDKs), the AWS Cloud Development Kit (AWS CDK), AWS CloudFormation, and AWS Cloud Control API. You can also use third party infrastructure as code (IaaC) providers such as [Terraform](https://www.hashicorp.com/blog/managing-resources-with-the-terraform-aws-cloud-control-provider). ## How Amazon Q Developer in chat applications works Amazon Q Developer in chat applications uses Amazon Simple Notification Service (Amazon SNS) topics to send event and alarm notifications from AWS services to your chat channels. Once an SNS topic is associated with a configured chat client, events and alarms from various services are processed and notifications are delivered to the specified chat channels and webhooks. For Microsoft Teams and Slack, after an administrator approves Amazon Q Developer in chat applications support for the tenant or workspace, anyone in the team or workspace can add Amazon Q Developer in chat applications to their chat channels. For Amazon Chime, users with AWS Identity and Access Management (IAM) permissions to use Amazon Chime can add Amazon Q Developer in chat applications to their webhooks. You use the Amazon Q Developer in chat applications console to configure chat clients to receive notifications from SNS topics. You can also run AWS CLI commands directly in chat channels using Amazon Q Developer. You can retrieve diagnostic information, configure AWS resources, and run workflows. To run a command, Amazon Q Developer in chat applications checks that all required parameters are entered. If any are missing, Amazon Q Developer in chat applications prompts you for the required information. Amazon Q Developer in chat applications then confirms if the command is permissible by checking the command against what is allowed by the configured IAM roles and the channel guardrail policies. For more information, see [Running AWS CLI commands from chat channels](chatbot-cli-commands.md) and [Understanding permissions](understanding-permissions.md). # Amazon Q Developer in chat applications rename - Summary of changes On February 19, 2025, we renamed AWS Chatbot to Amazon Q Developer. If you are a current user, there is no change in functionality or impact to your current usage, pricing, and setup. All features of AWS Chatbot are moving to Amazon Q Developer. Your code and Region availability will remain the same. **Note** Mentions of the name AWS Chatbot may persist in the CloudFormation guide, AWS General Reference entry, and user guide page URLs. Service principals, IAM permissions, console urls, organizations policy schemas, namespace, endpoints, and service-linked role names will remain unchanged. **Topics** + [ ## What's new? ](#rename-changes) + [ ## What's staying the same? ](#rename-not-changing) + [ ## Pricing ](#updated-pricing) + [ ## FAQs ](#FAQS) + [ ## Updating Slack bot user app mentions when sending messages to chat channels programmatically ](#update-slack-bot) ## What's new? AWS Chatbot is now called Amazon Q Developer. The name change is effective in Microsoft Teams and Slack chat applications, the AWS Management Console, and documentation. The following sections describe what parts of the service have changed with the rename and what actions you need to take to ensure that your workflows run smoothly after the renaming change. ### Renamed chat applications The AWS Chatbot for Microsoft Teams and AWS Chatbot for Slack chat applications are renamed Amazon Q Developer. You don’t need to reinstall or upgrade the chat applications in your Microsoft Teams teams or Slack workspaces. Notifications and interactions in the chat channels are updated to show Amazon Q Developer as the display name instead of AWS ### Updated @mentions in chat applications If you run tasks or ask questions in chat channels, you must tag the chat application by entering `Amazon Q` instead of `@aws`. Tagging the chat application isn’t case sensitive. For example if you previously entered `@aws Which of my EC2 instances are currently running in us-east-1`?, Enter `@Amazon Q Which of my EC2 instances are currently running in us-east-1?`. If you use Slack automation workflows to send commands to the AWS Chatbot chat application, previous references to `@aws` are automatically updated to `@Amazon Q`. If you're using webhooks to send `@aws` messages to the AWS Chatbot bot app programmatically, you'll need to change how you invoke the bot app programmatically. **Tip** Instead of entering `@Amazon Q`, you can enter `@Q` and choose the autocomplete recommendation that matches the app name. ### Renamed console in AWS Management Console The references to AWS Chatbot in the AWS Management Console are updated with the name Amazon Q Developer in chat applications. The workflows to create and manage chat configurations remain unchanged in the renamed console. ### Renamed AWS Organizations policies AWS Chatbot organization policies (Chatbot policies) are now called Amazon Q Developer in chat applications policies (chat applications policies). These policies allow you to control access to an organization’s accounts from chat applications like Microsoft Teams and Slack. For more information, see [Amazon Q Developer in chat applications organization policies](https://docs.aws.amazon.com/chatbot/latest/adminguide/chatbot-orgs-policy.html). The schema for the chat application policy remains unchanged. Your existing policies will continue to function as is. ### New service improvements management options With this launch, the setting to manage how AWS uses your content in chat applications for service improvement are now managed under Amazon Q Developer. Amazon Q Developer may use certain content from Amazon Q Developer Free tier for service improvement. You can opt-out of this at any time. For more information, see [Amazon Q Developer service improvement](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/service-improvement.html) in the *Amazon Q Developer User Guide*. ## What's staying the same? Your existing chat configurations in the chat applications will continue to work as they did previously. The APIs, SDK, service endpoints, IAM permissions, and Region availability are unaffected by this name change. You will retain: + Delivery of notifications for your alarms and operation events + Ability to run CLI-based tasks using action buttons, aliases, and typed inputs + Chat channel configurations including configured IAM permissions, channel guardrails, and Amazon SNS topic subscriptions + Customizations such as custom notifications, actions, and aliases + AWS Organizations Service control policies (SCPs) and chatbot management policies (now called [Amazon Q Developer in chat applications policies](#renamed-policies)) + Tags ## Pricing There is no change to your current usage and pricing. Non-generative AI features for sending notifications and running CLI-based commands using action buttons, aliases, and typed-commands are still available to you at no additional cost after the renaming. When you use Amazon Q Developer in chat applications, access is limited to the Amazon Q Developer Free tier, even when you are subscribed to Amazon Q Developer Pro tier. This update doesn't automatically enable identity-aware sessions, which are needed to chat with Amazon Q Developer at the Pro tier. For more information, see [Amazon Q Developer pricing](https://aws.amazon.com/q/developer/pricing/). ## FAQs ### If I use AWS Chatbot today, what changes for me? The chat application name changes from AWS Chatbot to Amazon Q Developer. Notifications and responses received in channels display the application name as Amazon Q instead of AWS. When you run tasks or ask questions from your chat channels, use `@Amazon Q` instead of `@aws`. Your Slack automation workflows that trigger commands within the AWS Chatbot app won't change with this renaming. If you currently send messages to the AWS Chatbot app programmatically using webhooks, you'll need to change how you invoke the bot app programmatically. To invoke the app, you can use the bot app member ID or change the bot app name in your workspace to `aws`. For more information, see [Updating Slack bot user app mentions when sending messages to chat channels programmatically](#update-slack-bot). ### Do I need an Amazon Q Developer subscription to continue using AWS Chatbot? No, you don't need a Amazon Q Developer subscription to continue using the non-generative AI features you previously used with AWS Chatbot. To enable Amazon Q Developer generative AI features in your chat channels, you need to add the `[AmazonQDeveloperAccess](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/managed-policy.html#amazonq-policy-developeraccess)` managed policy to your IAM role and channel guardrails. For more information, see [Chatting with Amazon Q Developer in chat channels](asking-questions.md). In chat applications, Amazon Q Developer access is limited to the Free tier only. For customers on Amazon Q Developer Pro tier, access is limited to Free tier usage limits. ### What should I do if I need to disable generative AI features of Amazon Q Developer in chat applications? To disable Amazon Q Developer generative AI features in a chat channel, you must remove the `[AmazonQDeveloperAccess](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/managed-policy.html#amazonq-policy-developeraccess)` managed policy from your IAM role or add restrictions to your channel guardrails. For more information, see [Manage access to Amazon Q Developer with policies](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/security_iam_manage-access-with-policies.html) in the *Amazon Q Developer User Guide*. You can also control what Amazon Q Developer features are available in your organization by creating a Service Control Policy (SCP) that specifies permissions for some Amazon Q Developer actions. For more information, see [Manage access with service control policies (SCPs)](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/security_iam_manage-access-with-policies.html#service-control-policies) in the *Amazon Q Developer User Guide*. ## Updating Slack bot user app mentions when sending messages to chat channels programmatically If you send messages programmatically to Slack chat channels using webhooks or APIs with messages formated as `<@aws> message`, you'll need to make a change to continue invoking the Slack bot user. ### (Recommended) Use member ID in @mention instead of the bot name Use member IDs instead of instead of `@aws` or `@Amazon Q` when mentioning users and the bot user. A member ID is a unique identifier assigned to each user within a Slack workspace. The member ID for the bot user is unique to each Slack workspace. Member IDs always resolve to the correct chat app, regardless of the display name. For more information, see [Mentioning Users](https://api.slack.com/reference/surfaces/formatting#mentioning-users) in the Slack API reference. **To update @mentions using a member ID** 1. Open Slack 1. Choose the bot user and open the **Profile** sidebar. 1. Choose the vertical ellipses (**⋮**). 1. Choose **Copy member ID**. 1. In your code, update mentions of `<@aws>` to `<@Member-ID>`. ### Workaround: Rename the bot in your workspace You can change the name of the bot user in your Slack workspace from Amazon Q to aws. This allows your existing programmatic invocations to continue functioning with `@aws` app mentions. **Note** This rename applies to your workspace, not just individual channels. **To rename the bot in your workspace** 1. Open Slack 1. Choose your workspace name in the sidebar. 1. Choose **Tools & settings** from the menu and choose **Manage apps**. 1. Choose the **App Details** tab. 1. In **App Details**, choose the **Configuration** tab. 1. In **Bot User**, choose **Edit**. 1. Change the bot user name from **Amazon Q** to **aws**. 1. Invoke the bot app using `@aws command` in your chat channels. # Regions and quotas for Amazon Q Developer in chat applications Although most AWS Regions are active by default for your AWS account, certain Regions are activated only when you manually select them. This document refers to those Regions as *opt-in Regions*. In contrast, Regions that are active by default, as soon as your AWS account is created, are referred to as *commercial Regions*, or simply, *Regions*. ## Supported Regions for Amazon Q Developer in chat applications Supported Regions include: + US East (Ohio) + US East (N. Virginia) + US West (N. California) + US West (Oregon) + Asia Pacific (Mumbai) + Asia Pacific (Osaka) + Asia Pacific (Seoul) + Asia Pacific (Singapore) + Asia Pacific (Sydney) + Asia Pacific (Tokyo) + Canada (Central) + Europe (Frankfurt) + Europe (Ireland) + Europe (London) + Europe (Paris) + Europe (Stockholm) + South America (São Paulo) You can combine Amazon SNS topics from multiple Regions in a single Amazon Q Developer in chat applications configuration. ### Opt-in Regions Opt-in Regions aren't enabled by default. You must manually enable these Regions to use them with Amazon Q Developer in chat applications. For more information about AWS Regions, see [Managing AWS Regions](https://docs.aws.amazon.com/general/latest/gr/rande-manage.html). The following opt-in Regions are supported: + Africa (Cape Town) + Asia Pacific (Hong Kong) + Asia Pacific (Hyderabad) + Asia Pacific (Jakarta) + Asia Pacific (Malaysia) + Asia Pacific (Melbourne) + Asia Pacific (Thailand) + Canada West (Calgary) + Europe (Milan) + Europe (Spain) + Europe (Zurich) + Israel (Tel Aviv) + Middle East (Bahrain) + Middle East (UAE) + Mexico (Central) ## Endpoints and quotas for Amazon Q Developer in chat applications Amazon Q Developer in chat applications currently supports service endpoints, however there are no adjustable quotas. For more information about Amazon Q Developer in chat applications endpoints and quotas, see [Amazon Q Developer in chat applications endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/chatbot.html). # Supported services for Amazon Q Developer in chat applications Amazon Q Developer in chat applications supports AWS services that emit events to Amazon EventBridge, including Amazon GuardDuty, CloudFormation, AWS Cost Anomaly Detection, and AWS Budgets. For a complete list of supported services, see the [https://docs.aws.amazon.com/eventbridge/latest/ref/welcome.html](https://docs.aws.amazon.com/eventbridge/latest/ref/welcome.html). Amazon Q Developer in chat applications also supports notifications for the following services: + Amazon CloudWatch + Amazon CodeCatalyst + AWS Cost Anomaly Detection Most AWS services that you can manage using the [AWS Command Line Interface (CLI)](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html) are also supported. Subsequently, you can manage your AWS resources from these services using AWS CLI commands directly from your chat channels. ## Amazon Q Developer in chat applications requirements To use Amazon Q Developer in chat applications, you need the following: + An AWS account to associate with Amazon Chime, Microsoft Teams, or Slack chat clients during Amazon Q Developer in chat applications setup. + Administrative privileges for your Amazon Chime chat room, Microsoft Teams tenant, or Slack workspace. You can be the Slack workspace owner or have the ability to work with workspace owners to get approval for installing Amazon Q Developer in chat applications. + Familiarity with AWS Identity and Access Management (IAM) and IAM roles and policies. For more information about IAM, see [What is IAM?](https://docs.aws.amazon.com/IAM/latest/UserGuide/) in the *IAM User Guide*. + Experience with the AWS services supported by Amazon Q Developer in chat applications, including experience configuring those services to subscribe to Amazon Simple Notification Service (Amazon SNS) topics to send notifications. For information about supported services, see [Using Amazon Q Developer in chat applications with Other AWS Services](related-services.md). To access Amazon CloudWatch metrics, Amazon Q Developer in chat applications requires an AWS Identity and Access Management (IAM) role with a permissions policy and a trust policy. You create this IAM role, with the required policies, [using the Amazon Q Developer in chat applications console](https://us-east-2.console.aws.amazon.com/chatbot/home?region=us-east-2#/chat-clients). You can use an existing IAM role, but it must have the required policies. ## Accessing Amazon Q Developer in chat applications You access and configure Amazon Q Developer in chat applications through the Amazon Q Developer in chat applications console at [https://console.aws.amazon.com/chatbot/](https://console.aws.amazon.com/chatbot/). You can also access the Amazon Q Developer in chat applications app from the [Slack app directory](https://amzn-aws.slack.com/apps/A6L22LZNH-aws-chatbot?settings=1).