I’m happy to announce that, beginning immediately, you need to use AWS Chatbot to troubleshoot and function your AWS assets from Microsoft Groups.
Speaking and collaborating on IT operation duties by way of chat channels is named ChatOps. It lets you centralize the administration of infrastructure and functions, in addition to to automate and streamline your workflows. It helps to supply a extra interactive and collaborative expertise, as you possibly can talk and work together with your colleagues in actual time by way of a well-known chat interface to get the job executed.
AWS Chatbot Advantages
When utilizing AWS Chatbot for Microsoft Groups or different chat platforms, you obtain notifications from AWS companies straight in your chat channels, and you may take motion in your infrastructure by typing instructions with out having to change to a different device.
Usually you wish to obtain alerts about your system well being, your finances, any new safety menace or threat, or the standing of your CI/CD pipelines. Sending a message to the chat channel is so simple as sending a message on an Amazon Easy Notification Service (Amazon SNS) subject. Because of the native integration between Amazon CloudWatch alarms and SNS, alarms are mechanically delivered to your chat channels with no extra configuration step required. Equally, due to the combination between Amazon EventBridge and SNS, any system or service that emits occasions to EventBridge can ship data to your chat channels.
However ChatOps is greater than the flexibility to identify issues as they come up. AWS Chatbot lets you obtain predefined CloudWatch dashboards interactively and retrieve Logs Insights logs to troubleshoot points straight from the chat thread. It’s also possible to straight sort within the chat channel most AWS Command Line Interface (AWS CLI) instructions to retrieve extra telemetry information or useful resource data or to run runbooks to remediate the problems.
Typing and remembering lengthy instructions is troublesome. With AWS Chatbot, you possibly can outline your individual aliases to reference incessantly used instructions and their parameters. It reduces the variety of steps to finish a process. Aliases are versatile and might include a number of customized parameters injected on the time of the question.
And since chat channels are designed for dialog, you can even ask questions in pure language and have AWS Chatbot reply you with related extracts from the AWS documentation or help articles. Pure language understanding additionally lets you make queries reminiscent of “present me my ec2 cases in eu-west-3.”
Let’s Configure the Integration Between AWS Chatbot and Microsoft Groups
Getting began is a two-step course of. First, I configure my staff in Microsoft Groups. As a Groups administrator, I add the AWS Chatbot utility to the staff, and I be aware of the URL of the channel I wish to use for receiving notifications and working AWS assets from Microsoft Groups channels.
Second, I register Microsoft Groups channels in AWS Chatbot. I additionally assign IAM permissions on what channel members can do on this channel and affiliate SNS subjects to obtain notifications. I could configure AWS Chatbot with the AWS Administration Console, an AWS CloudFormation template, or the AWS Cloud Improvement Equipment (AWS CDK). For this demo, I select to make use of the console.
I open the Administration Console and navigate to the AWS Chatbot part. On the highest proper aspect of the display screen, within the Configure a chat consumer field, I choose Microsoft Groups after which Configure consumer.
At this stage, Chatbot redirects my browser to Microsoft Groups for authentication. If I’m already authenticated, I will probably be redirected again to the AWS console instantly. In any other case, I enter my Microsoft Groups credentials and one-time password and wait to be redirected.
At this stage, my Microsoft Groups staff is registered with AWS Chatbot and able to add Microsoft Groups channels. I choose Configure new channel.
There are 4 sections to enter the main points of the configuration. Within the first part, I enter a Configuration identify for my channel. Optionally, I additionally outline the Logging particulars. Within the second part, I paste—once more—the Microsoft Groups Channel URL.
Within the third part, I configure the Permissions. I can select between the identical set of permissions for all Microsoft Groups customers in my staff, or I can set Consumer-level roles permission to allow user-specific permissions within the channel. On this demo, I choose Channel function, and I assign an IAM function to the channel. The function defines the permissions shared by all customers within the channel. For instance, I can assign a task that enables customers to entry configuration information from Amazon EC2 however not from Amazon S3. Underneath Channel function, I choose Use an present IAM function. Underneath Present function, I choose a task I created for my 2019 re:Invent speak about ChatOps:
chatbot-demo. This function provides read-only entry to all AWS companies, however I might additionally assign different roles that may enable Chatbot customers to take actions on their AWS assets.
To mitigate the danger that one other particular person in your staff unintentionally grants greater than the required privileges to the channel or user-level roles, you may also embody Channel guardrail insurance policies. These are the utmost permissions your customers may need when utilizing the channel. At runtime, the precise permissions are the intersection of the channel or user-level insurance policies and the guardrail insurance policies. Guardrail insurance policies act like a boundary that channel customers won’t ever escape. The idea is just like permission boundaries for IAM entities or service management insurance policies (SCP) for AWS Organizations. On this instance, I connect the ReadOnlyAccess managed coverage.
The fourth and final part lets you specify the SNS subject that would be the supply for notifications despatched to your staff’s channel. Your functions or AWS companies, reminiscent of CloudWatch alarms, can ship messages to this subject, and AWS Chatbot will relay all messages to the configured Microsoft Groups channel. Because of the combination between Amazon EventBridge and SNS, any utility in a position to ship a message to EventBridge is ready to ship a message to Microsoft Groups.
For this demo, I choose an present SNS subject:
alarmme within the
us-east-1 Area. You’ll be able to configure a number of SNS subjects to obtain alarms from numerous Areas. I then choose Configure.
On the AWS Chatbot configuration web page, I first choose the Ship take a look at message. I even have an alarm outlined when my estimated billing goes over $500. On the CloudWatch part of the Administration Console, I configure the alarm to put up a message on the SNS subject shared with Microsoft Groups.
Inside seconds, I obtain the take a look at message and the alarm message on the Microsoft Groups channel.
Then I sort a command to grasp the place the billing alarm comes from. I wish to perceive what number of EC2 cases are operating.
On the chat consumer channel, I sort
@aws to pick out Chatbot because the vacation spot, then the remainder of the CLI command, as I might do in a terminal:
ec2 describe-instances --region us-east-1 --filters "Title=structure,Values=arm64_mac" --query "Reservations.Cases.InstanceId"
Chatbot solutions inside seconds.
I can create aliases for instructions I incessantly use. Aliases could have placeholder parameters that I can provide at runtime, such because the Area identify for instance.
I create an alias to get the checklist of my macOS occasion IDs with the command:
aws alias create mac ec2 describe-instances --region $area --filters "Title=structure,Values=arm64_mac" --query "Reservations.Cases.InstanceId"
Now, I can sort
@aws alias run mac us-east-1 as a shortcut to get the identical consequence as above. I may handle my aliases with the
@aws alias checklist,
@aws alias get, and
@aws alias delete instructions.
I don’t learn about you, however for me it’s laborious to recollect instructions. Once I use the terminal, I depend on auto-complete to remind me of varied instructions and their choices. AWS Chatbot gives related command completion and guides me to gather lacking parameters.
When utilizing AWS Chatbot, I may ask questions utilizing pure English language. It could actually assist to search out solutions from the AWS docs and from help articles by typing questions reminiscent of
@aws how can I tag my EC2 cases? or
@aws how do I configure Lambda concurrency setting?
It could actually additionally discover assets in my account when AWS Useful resource Explorer is activated. For instance, I requested the bot:
@aws what are the tags for my ec2 assets? and
@aws what Areas do I've Lambda service?
And I acquired these responses.
You can begin to make use of AWS Chatbot with Microsoft Groups immediately. AWS Chatbot for Microsoft Groups is out there to obtain from Microsoft Groups app at no extra price. AWS Chatbot is out there in all public AWS Areas, at no extra cost. You pay for the underlying assets that you just use. You may incur fees out of your chat consumer.
Get began immediately and configure your first integration with Microsoft Groups.