Streamline AWS Support with AWS Chatbot and Microsoft Teams
For platform teams, the main value here is not the chat UI itself but the integration boundary it creates between AWS Support, EventBridge, SNS, and Microsoft Teams. That chain turns support activity into a governed operational workflow, but it also introduces dependencies that must be designed deliberately: regional service availability, IAM permissions, channel type constraints, and message transformation logic all become part of the support path.
Architecturally, the event model matters. AWS Support events are not delivered to Teams directly; they are first normalized through EventBridge and then reshaped into a Chatbot-compatible payload. That means the quality of your notification experience depends on the stability of the transformation layer and on how carefully you map fields such as case identifiers and status changes into reusable metadata for downstream actions.
From an operations and security perspective, the workflow shifts responsibility into the chat environment without removing control requirements. Teams channel permissions, Chatbot guardrails, and AWS Support API access all need to align, otherwise notifications may arrive without actionable commands or, worse, expose capabilities more broadly than intended. Public-channel-only support also affects how teams segment incidents and who can observe support activity.
For enterprises running multiple accounts or managed services, the bigger implication is standardization. If the same channel receives support updates from several AWS accounts, custom actions can become a scalable pattern for acknowledgements, follow-up notes, and case triage. The trade-off is governance: shared channels reduce friction, but they require stricter naming, routing, and access conventions to keep incident handling understandable and auditable.
- Receive notifications on a new AWS Support case creation
- Receive notifications on an update to an AWS Support case
- Get support case status and latest updates
- Add a note into the Support case
Fig-1: Two-way communication between chat application and AWS services through AWS Chatbot.
Prerequisites
To get started, you need to configure AWS Chatbot with your Microsoft Teams app and appropriate administration level permissions is required.- Ensure Microsoft Teams is installed and approved by your organization administrator
- Verify that your Microsoft Teams administrator has approved the AWS Chatbot app for Microsoft Teams, and you have required IAM privileges in the AWS console.
- You have aย Business, Enterprise On-Ramp, or Enterprise Supportย plan to be able to use the AWS Support API. Referย AWS Supportย for more information.
Getting started
Follow steps inย Get started with Microsoft Teamsย tutorial to setup basic connectivity between Teams and AWS Chatbot. You need to consider following notes during the process: Notes:- Steps listed under โStep 1: Configure a Microsoft Teams clientโ are to be followed in your Teams channel. Ensure that the Teams channel is of typeย Public. Teams doesnโt currently support AWS Chatbot in private channels.
- Steps listed under โStep 2: Configure a Microsoft Teams channelโ are to be followed in your AWS console.
- You must set up โAmazon Simple Notification Serviceย (Amazon SNS) topicโ for notifications in your Teams channel to receive notification of new AWS Support cases. Create a new SNS Topic (of Type:Standard) without subscription and this step will automatically add a Chatbot subscription into the given SNS Topic.ย Noteย that since AWS Support service is currently available in US East (N. Virginia), US West (Oregon), and Europe (Ireland) regions, so you must setup your SNS topic in one of these regions.
- Forย Channel role, ensure at least โAWS Support command permissionโ and โRead-only command permissionsโ are added into your Chatbot role if creating a new IAM role.
- Forย Channel guardrail policies, ensure at least โSupportUserโ and โReadOnlyAccessโ are added.
- Steps listed under โStep 3: Test notifications from AWS services to Microsoft Teamsโ are to be followed in your AWS console, and verify the test message (refer Fig 2 below) in your Teams channel.
- Do not proceed furtherย until you have received the โtest messageโ in your Teams channel. This is an important step to ensure the setup is working as expected. Refer toย this pageย to troubleshoot further.
Fig-2: A sample default Chatbot message or notification showing successful integration.
Setup Teams notifications on new AWS Support case creation or updates
Amazon EventBridgeย is a serverless services that make easier for you to receive, filter, transform, route, and deliver AWS service events in your AWS cloud. You will use EventBridge to transform the AWS Support events into a Chatbot-compatible format, and route them to the Amazon SNS. SNS will then forward the notification to the Chatbot, which will ultimately send the notification to your Microsoft Teams channel. The diagram below illustrates the complete workflow.
Fig-3: An event journey from AWS Support to a transformed message in Microsoft Teams.
Create an Amazon EventBridge rule for AWS Support cases
Note that AWS Support service is currently available in US East (N. Virginia), US West (Oregon), and Europe (Ireland) regions, so you must setup the EventBridge rule & SNS topic in one of these regions to receive Support events. Region US East is used in this post. Follow theย Creating an EventBridge rule for AWS Support casesย guide to setup an event rule for events emitted by AWS Support service (Ref: Step-3, Fig-3). Consider following during the process:- Underย Event pattern, forย AWS service, chooseย Support, forย Event type, chooseย Support Case Update. It should look like below:
- Forย Target, use theย SNS topicย that you created as part of the pre-requisites. It has integration with AWS Chatbot endpoint.
Setup EventBridge transformation
You will need to transform the event to suit AWS Chatbot formatting (Ref: Step-4, Fig-3). Use parameters and transformation rules provided below. You can refer AWS Chatbotโsย Custom notificationsย section to learn further about custom notification event schema. To create a target input transformer as part of a rule:- Expand Additional settings, and Configure target input, select Input transformer
- Click on Configure Input transformer button to setup the transformation in a new window
- For the Sample event, use Support Case Update (keep copy for later reference)
- Under Target input transformer use:
- Under Template use below template:
- Click onย Generate outputย to see your final transformed event message. If all looks good, clickย Confirmย to close the window. Clickย Nextย to setup Tags and clickย Create ruleย to create the rule. You can change the Input transformation later as needed.
Test complete workflow
You can now test the end-to-end workflow by creating or updating an AWS Support case, and following message should appear in your Teams channel (Ref: Fig-3).
Fig-4: Custom message (notification) received upon an update to AWS Support case.
Responding to AWS Support cases within Teams channel
AWS Chatbot allows you toย run AWS commandsย directly from your chat channels. It also enables you to useย custom actions, which can be used to set up preconfigured action buttons that can be automatically added to your future similar / custom notification. These actions allow you to automate commonly used DevOps processes and incident response tasks. Using custom action, you can configure an action button to run either an AWS Command Line Interface (AWS CLI) or a Lambda function. In this case, we will use AWS CLI commands to interact with AWS Support cases via these custom actions.Creating a custom action
To create an AWS CLI command action- Choose the vertical ellipsis (3 dots) button on the bottom of the above. Support Case notification in your Teams channel (Ref: Fig-4). It should open a workflow in new window.
- Inย Manage actions, chooseย Create.
- Enter a custom action name, sayย
GetSupportCaseDetails. - Enter a name for your custom action button, sayย
GetCaseDetails. This name is shown on a button on your notification. - Forย Custom action type, chooseย CLI action.
- Enter below command
- support describe-cases โdisplay-id $caseId โmax-results 100 โquery Cases[0].[Status, Subject, RecentCommunications.Communications[0].Body] โregion us-east-1ย Note: Chatbot exposes predefined variables from your custom notifications to be used as variables for these custom actions. If you noticed in the previous section (Step-5 of Setup EventBridge transformation), we added โ
metadataโ: โcaseIdโ in the event transformation template. Letโs make use of it, so that same button/action can be used for all AWS Support case notifications and the Case ID is automatically substituted via this variable.
- support describe-cases โdisplay-id $caseId โmax-results 100 โquery Cases[0].[Status, Subject, RecentCommunications.Communications[0].Body] โregion us-east-1ย Note: Chatbot exposes predefined variables from your custom notifications to be used as variables for these custom actions. If you noticed in the previous section (Step-5 of Setup EventBridge transformation), we added โ
- Add our new variable by choosing + Add more variables.
- Variable name:ย
caseId - Name expression:ย
event.metadata.caseId
- Variable name:ย
- ย Chooseย Next.
- Verifyย Display criteriaย i.e. the conditions that must be met to display this custom action button on a specific notification. In this case they are:
- NotificationTypeย equalsย Custom.
- caseIdย has any value
- Chooseย Save. Wait until you get the message โSuccessfully createdย
GetSupportCaseDetailsโ. - You should get a message like below:
Fig-5: Snapshot showing a custom action button has been created.
Test Scenarios
- Letโs test the end-to-end flow by updating an AWS Support case. Following message should soon appear in your Teams channel. Notice the newย
GetCaseDetailsย custom action button now appearing with the latest chat message. The Chatbot is intelligent enough to recognize that the custom action button belongs to these types of messages, and it automatically applies the button.
Fig-6: Snapshot showing presence of the custom action button in a custom chat massage.
- Test the button action to fetch the case update in your Teams channel. Notice it should autofill the required variable i.e.ย
CaseIdย in this case. Chooseย Runย to fetch the case Status, Title and latest note.
Fig-7: Snapshot showing execution of the custom action button.
- You will receive a response with the latest case details, as per the defined CLI action. Example response below:
Fig-8: Snapshot showing output post execution of the custom action button.
What next?
Well, you can use the above information to effectively manage common Support case management tasks per your business needs. For example, if your AWS account is being managed byย AWS Managed Servicesย (AMS), their proactive monitoring will identify an issue, create an AWS Support case, and simultaneously request your approval before remediating a non-preapproved issue. To boost productivity, you can create custom action buttons, such as โApprovedโ or โNeed More Infoโ, within your Teams channel. These buttons allow you to add instructions directly into a Support case, enabling seamless communication with the AMS operations team. You can also use AWS Chatbot to manage your Support case management workflows for your multi-account cross-region applications in chat channels. For example, you can set up AWS Chatbot in multiple AWS accounts to send AWS Support notifications into the same Teams channel. All your custom action buttons setup in that channel will be automatically applied across related notifications from all AWS accounts. Depending on your ChatOps practices, you can choose to set up separate Microsoft Teams channels based on criteria such as AWS account, application, or environment (production/non-production). In addition, you can directly interact withย Amazon Q Developerย in Microsoft Teams and Slack messaging platforms that are configured with AWS Chatbot, to answer questions about AWS best practices, troubleshooting issues, or identifying next steps.Resources
- To learn about available AWS Support CLI commands, or variables in the request and response API calls, refer to theย Running AWS CLI commands from chat channelsย andย AWS Support APIย documentation.
- Referย Monitoring AWS services using AWS Chatbotย to use AWS Chatbot to monitor and receive notifications about other AWS services
Conclusion
In this blog, you learned how to use AWS Chatbot features, such asย Custom notificationsย andย Custom actionsย for Microsoft Teams, to enhance your ChatOps experience. Additionally, you gained insights on performing common AWS Support management tasks directly within the Microsoft Teams channel, such as receiving case notifications and making updates to cases, significantly enhancing your teamโs productivity.About the authors:
Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.
