AWS DevOps Agent - US East
AWS DevOps Agent App for SlackAWS DevOps Agent is an AI-powered service that helps engineering and operations teams investigate incidents, identify root causes, and develop mitigation and prevention recommendations. The AWS DevOps Agent App for Slack connects an AWS DevOps Agent Agent Space to selected Slack channels, allowing responders to receive operational updates and interact with the agent where they already collaborate.Receive investigation updates in SlackAfter a Slack channel is associated with an Agent Space, AWS DevOps Agent can post operational information to that channel, including:• Incident and investigation notifications
• Investigation progress and key findings
• Root cause summaries
• Recommended mitigation and prevention actions
• Links to additional investigation details in AWS DevOps AgentCustomers control which Agent Spaces and Slack channels are connected. AWS DevOps Agent posts only to channels configured through an association in the AWS DevOps Agent console. For private channels, the app must also be added to the channel.Interact with AWS DevOps Agent from SlackWhen bidirectional communication is enabled for an associated private channel, authorized channel members can mention AWS DevOps Agent to interact with the connected Agent Space directly from Slack.Team members can use natural-language messages to:• Ask operational questions
• Start or continue investigations
• Request investigation findings and supporting evidence
• Provide additional incident context
• Guide the next steps of an investigation
• Receive responses in the Slack conversationBidirectional communication is not enabled automatically. It must be explicitly configured for the channel in the AWS DevOps Agent console. Bidirectional communication is supported only in configured private channels, and the AWS DevOps Agent app must be added to the channel.Installation and configurationInstallation begins in the AWS Management Console because the Slack workspace must be securely associated with an AWS account, AWS Region, and AWS DevOps Agent configuration. A public installation button cannot complete this account-specific configuration.To connect a Slack workspace:1. Sign in to the AWS Management Console and open AWS DevOps Agent.
2. Open Capability Providers.
3. Find Slack under Communication and choose Register.
4. Authorize and hit Next.
5. Sign in to the Slack workspace and approve the requested permissions.
6. Return to AWS DevOps Agent and open the Agent Space that you want to connect.
7. Add a Slack connection and enter the destination Slack channel ID.
8. If the destination is a private channel, add the AWS DevOps Agent app from the channel's Integrations settings.
9. Optionally enable bidirectional communication for the private channel and complete its required AWS configuration.Installing and configuring the app requires:• An AWS account with access to AWS DevOps Agent
• A configured AWS DevOps Agent Agent Space
• Permission to configure AWS DevOps Agent resources
• Permission to install and authorize applications in the selected Slack workspace
• The IDs of the Slack channels that will be connectedThe AWS DevOps Agent console selects the appropriate regional Slack application for the AWS Region where the Agent Space is configured.For complete installation, configuration, and testing instructions, see the AWS DevOps Agent Slack integration documentation.AI-generated contentAWS DevOps Agent uses large language models to generate investigation findings, root-cause analyses, mitigation recommendations, and conversational responses. These outputs might be inaccurate or incomplete. Verify AI-generated information before acting on it. AWS handles information in accordance with the AWS Privacy Notice.
• Investigation progress and key findings
• Root cause summaries
• Recommended mitigation and prevention actions
• Links to additional investigation details in AWS DevOps AgentCustomers control which Agent Spaces and Slack channels are connected. AWS DevOps Agent posts only to channels configured through an association in the AWS DevOps Agent console. For private channels, the app must also be added to the channel.Interact with AWS DevOps Agent from SlackWhen bidirectional communication is enabled for an associated private channel, authorized channel members can mention AWS DevOps Agent to interact with the connected Agent Space directly from Slack.Team members can use natural-language messages to:• Ask operational questions
• Start or continue investigations
• Request investigation findings and supporting evidence
• Provide additional incident context
• Guide the next steps of an investigation
• Receive responses in the Slack conversationBidirectional communication is not enabled automatically. It must be explicitly configured for the channel in the AWS DevOps Agent console. Bidirectional communication is supported only in configured private channels, and the AWS DevOps Agent app must be added to the channel.Installation and configurationInstallation begins in the AWS Management Console because the Slack workspace must be securely associated with an AWS account, AWS Region, and AWS DevOps Agent configuration. A public installation button cannot complete this account-specific configuration.To connect a Slack workspace:1. Sign in to the AWS Management Console and open AWS DevOps Agent.
2. Open Capability Providers.
3. Find Slack under Communication and choose Register.
4. Authorize and hit Next.
5. Sign in to the Slack workspace and approve the requested permissions.
6. Return to AWS DevOps Agent and open the Agent Space that you want to connect.
7. Add a Slack connection and enter the destination Slack channel ID.
8. If the destination is a private channel, add the AWS DevOps Agent app from the channel's Integrations settings.
9. Optionally enable bidirectional communication for the private channel and complete its required AWS configuration.Installing and configuring the app requires:• An AWS account with access to AWS DevOps Agent
• A configured AWS DevOps Agent Agent Space
• Permission to configure AWS DevOps Agent resources
• Permission to install and authorize applications in the selected Slack workspace
• The IDs of the Slack channels that will be connectedThe AWS DevOps Agent console selects the appropriate regional Slack application for the AWS Region where the Agent Space is configured.For complete installation, configuration, and testing instructions, see the AWS DevOps Agent Slack integration documentation.AI-generated contentAWS DevOps Agent uses large language models to generate investigation findings, root-cause analyses, mitigation recommendations, and conversational responses. These outputs might be inaccurate or incomplete. Verify AI-generated information before acting on it. AWS handles information in accordance with the AWS Privacy Notice.
AWS DevOps Agent - US East will be able to view:
AWS DevOps Agent - US East will be able to do:
Review the details to better understand this app’s security practices. To learn more about assessing apps for your workspace visit our Help Center.
General
Developer
Amazon Web Services, Inc.
Company headquarters location
United States
Terms of service
Privacy & data governance
Data retention policy
You can find information on data retention in the AWS customer agreement site (https://aws.amazon.com/agreement/). If you have any specific questions about data retention, please reach out to your AWS account manager or AWS support (https://aws.amazon.com/contact-us/). When the Slack App is uninstalled, the AWS DevOps Agent removes the Slack workspace and channel identifiers, as well as any relevant metadata.
Data archiving and removal policy
You can find information on data archival in the AWS customer agreement site (https://aws.amazon.com/agreement/). If you have any specific questions about data archival, please reach out to your AWS account manager or AWS support (https://aws.amazon.com/contact-us/). When the Slack App is uninstalled, the AWS DevOps Agent removes the Slack workspace and channel identifiers, as well as any relevant metadata.
Data storage policy
You can find information on data storage in the AWS customer agreement site (https://aws.amazon.com/agreement/). If you have any specific questions about data storage, please reach out to your AWS account manager or AWS support (https://aws.amazon.com/contact-us/). When the Slack App is uninstalled, the AWS DevOps Agent removes the Slack workspace and channel identifiers, as well as any relevant metadata.
Data hosting company
AWS
App/service has sub-processors
no
App/service uses large language models (LLM)
yes
LLM model(s) used
Amazon Bedrock (multiple foundation models)
LLM retention settings
Customer data is stored in the region where the Agent Space is created. Investigation journals, chat messages, and operational data are retained for the lifetime of the Agent Space.
LLM data tenancy policy
AWS DevOps Agent uses Amazon Bedrock for inference processing. Customer data is isolated per Agent Space and per AWS account. AWS does not use agent data, chat messages, or data from integrated data sources to train models or improve the product.
LLM data residency policy
Data is stored in the AWS region where the Agent Space is created. Inference requests are processed within the customer's geography: US requests stay in the US, EU requests stay in the EU, Australia in Australia, and Japan in Japan.
Certifications & compliance
Data deletion request procedure
Customer data is deleted when customer deletes their Slack app integrations and AgentSpace from AWS DevOps Agent management console.
HIPAA compliant
no
While this app may offer HIPAA compliance, Slack does not have a business associate agreement with any third-party application providers, including those in the Slack Marketplace, so you are responsible for validating the provider's compliance and executing an appropriate agreement before enabling.
Security
Supports Security Assertion Markup Language (SAML)
no
Has a dedicated security team
yes
Contact for security issues
aws-security@amazon.com
Has a vulnerability disclosure program
no
Has a bug bounty program
no
Requires third party authorization/connections
no
Uses token rotation
yes