AWS Chatbot adds support to centrally manage access to AWS accounts from Slack and Microsoft Teams with AWS Organizations

AWS announces general availability of AWS Organizations support in AWS Chatbot. AWS customers can now centrally govern access to their accounts from Slack and Microsoft Teams with AWS Organizations. This launch introduces chatbot management policy type in AWS Organizations to control access to your organization's accounts from chat channels. Using Service Control Policies (SCPs), customers can also globally enforce permission limits on CLI commands originating from chat channels. With this launch, customers can use chatbot policies and multi-account management services in AWS Organizations to determine which permissions models, chat applications, and chat workspaces can be used to access their accounts. For example, you can restrict access to production accounts from chat channels in designated workspaces/teams. Customers can also use SCPs to specify guardrails on the CLI command tasks executed from chat channels. For example, you can specify deny all rds: delete-db-cluster CLI actions originating from chat channels. AWS Organizations support in AWS Chatbot is available at no additional cost in all [AWS Regions](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/) where AWS Chatbot is offered. Visit the [Securing your AWS organization in AWS Chatbot](https://docs.aws.amazon.com/chatbot/latest/adminguide/securing-orgs.html) documentation and [blog](https://aws.amazon.com/blogs/mt/managing-access-to-aws-accounts-from-microsoft-teams-and-slack-at-scale-using-aws-organizations-and-aws-chatbot) to learn more.