![]() ![]() It’s roughly here that, as they say, our troubles begin. Never one to spy an ill-defined buzzword without enthusiastically launching a service into the category, AWS created a full-on service called, of course, AWS Chatbot. If it isn’t, your deepest chat secrets are but a SQL query away.Īnyway, some enterprising folks eventually instrumented Slack a bit, because “Jimothy, do you want to go to lunch?” isn’t that far removed from “AWS, deploy to production.” The sound effect Slack plays when that message arrives is the creeeeak of Pandora’s Docker Container opening. Slack’s security team is excellent, because it pretty darn well has to be. All of your Slack messages live not in some ephemeral database like an early version of MongoDB, but rather as rows in MySQL. People treat chat as if it were ephemeral, with messages gone soon after they’re sent - but this isn’t Snapchat we’re talking about here. This is largely considered a boon for regulators looking to simplify their e-discovery. Why? While people store code and databases and naughty videos in their AWS accounts, they talk about things ranging from lunch plans to mergers and acquisitions to their passwords to their extramarital affairs to their insider trading crimes within Slack. Slack, a Salesforce company, is also the single organization I would attempt to breach if I were looking to do some real damage. I do not understand nor endorse this behavior and neither should you, because Teams is trash. Yes, some people use Microsoft Teams for work instead. Unless you’ve been living in a hole for the last decade, you’ve encountered Slack. You see, there seems to be a large-scale aversion to discussing the risks of ChatOps in public, and I can’t shake the feeling that this is going to bite all of us in the end. I’m afraid that’s going to be a big problem. There is no additional charge to use the Chatbot and it is available in any public AWS region.People tend to think of ChatOps as “a conversation-driven means of running software.” But that, my friends, is an oversimplification that misses a crucial point.ĬhatOps is “the novel operational practice of expanding your security perimeter to anyone who has access to the right Slack channel or to Slack’s production infrastructure.” This is obviously my own definition, and people tend not to talk about it this way. Many teams even prefer that operational events and notifications come through chat rooms where the entire team can see the notifications and discuss next steps.” “Bots help facilitate these interactions, delivering important notifications and relaying commands from users back to systems. Amazon SNS is a web service that coordinates and manages all the delivery of messages to AWS clients and subscribing endpoints, meaning the bot is clearly intended for use solely within an AWS environment.ĪWS’s product manager Ilya Bezdelev outlined the rationale behind the bot, saying: “DevOps teams widely use chat rooms as communications hubs where team members interact - both with one another and with the systems that they operate. The Chatbot service uses Amazon’s Simple Notification Service (Amazon SNS) to deliver the alerts. These capabilities mean that in addition to DevOps teams receiving chat room messages about issues such as billing and cost management, operating metrics for AWS services, and security threat and compliance alerts, the new Systems Manager links also provide notifications about configuration compliance or status changes for a Run Command. Originally launched in beta at the end of the July, the bot is able to receive notifications from AWS Systems Manager, in addition to those already established for Amazon Cloud Watch, AWS Health, AWS Budgets, AWS Security Hub, Amazon GuardDuty and AWS CloudFormation. A key feature of the Chatbot is that it can be integrated into the teams’ Slack channels or their Amazon Chime chat rooms, enabling it to send through security or resource alerts. ![]() The recently launched AWS Chatbot acts an interactive agent for DevOps teams who are seeking to monitor resources across their AWS ecosystems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |