AWS Chatbot Reviews

It quickly captures the order for which you want to raise an issue.

Sometimes if the issue is not related to order, it is a lot of struggle to get to the right place.

It is delivery-related, primarily queries and refunds.

I love how experts tend to the needs of customers in a very fast manor

I dislike nothing whatsoever I am fond of using AWS chatbot

This is a very wonderful software it will take you to the next level with ease on shopping and inquiries

I solve shopping problems and It makes it easier to get what I want right then.

They support amazon chime and Slack and its super simple to setup. The ability to receive notifications and have a bot chat with a customer is amazing.

Nothing, just needs to be developed a little further and will be perfect

Customer service when we are not in the office or readily available

The easiest way to allow maintenance and management of complex AWS resources through the simplest AWS Chime chat messages, you can manage all aspects of what is contained in AWS and through the APIs and webhooks you can also manage external resources not in cloud computing.

Integration with other chat applications is really scarce and sometimes completely absent, having everything on whatsapp would be much easier and visible for team members instead of having to open applications like Amazon Chime, it's not an operation that comes naturally out of the working hours, should be improved as the main competitor services.

Before starting to perform configuration, scaling or generic management of EC2 resources, EBS disks and VPC networks, I recommend that you practice test resources that you can create and delete immediately after spending only a few cents, webhooks are a powerful tool and can unfortunately cause damage in the event of oversights or improper use.

It helps us continuously and at any time to manage the automatic scaling of EC2 resources and to enable different VPC routing strategies to optimize network flows and better balance the communication of our services and those of our customers.

I think is very useful in planned and unplanned activities that are started, sometimes in urgency, during non-working hours, holidays or at night, it is possible to work from one's bed at home simply by chatting with your smartphone.

Easy to use, I integrated this into my website to auto handle customer chat

Noting till now. It's better then others

AllI integrated chatbot in my project, so that customer auto reply by entering his order id

Can use AWS Chatbot to receive notifications for health events, security bugs, etc. AWS Chatbot commands are familiar with the command line syntax. There are predefined identitiesIt and templates.

It takes a lot of work to setup everything for working of AWS Chatbox

It helped me getting notified of health events and security bugs.

This chatbot integrates well with AWS SNS and hence works really well with most AWS services which makes it super helpful for detecting issues. This chatbot can give notification via slack and most devops teams use Slack. It is a newly launched service and still in the process of getting better. People can even run lambda to some extend. Moreover, this can even run with Amazon chime chatrooms.

There could be filters that could be applied on the incoming messages.

There are ready made templates available and when I experimented, it was really easy to integrate with Slack, which is what my team used.

The chatbot is new and hence one feature I don't like that well is you can't push commands to the chatbot. It is mostly a listener right now. I believe more functionality must be on the roadmap.

We can't customize the messages as of now. Keep in mind that AWS chatbot is subject to rate limits from Slack , so it is a good idea to use filters and not let everything come in though into the channel as it might cause some issue.

Another thing is, only multiple regions are allowed and now multiple accounts. The SNS which hosts the AWS chatbot configuration can get the messages, so if there are multiple accounts, most likely you will need to create more Slack channels. This was a little bit of challenge in our use case.

I would suggest start basic with integration to a slack channel and let it be there. Push commands are there with some pre-defined templates available from Amazon's website. This is a really useful solution where the whole team can be added a central challenge such as Slack and everyone can keep track of the incoming messages. This makes collaboration really easy.

Another good thing is the inexpensive nature of the service means that you can experiment as there are no downcost and you pay as you go. This also supports SNS topics from multiple regions.

We use it to detect any operational issues without going into cloudwatch and looking at all the logs

Thanks to AWS ChatBot we are able to better integrate the daily operations of my company team so as to automatically start interactive procedures and complex scripts directly from a simple telegram chat from your smartphone, in total mobility and wherever you are.

In short, it is an excellent solution to save time and human resources by allowing automated operations to be performed on an external resource that is totally safe and risk-free for the data processed.

The possibility of hooking ChatBot to Linux CURL-type webhooks so as to perform complex requests such as filling in specific forms or uploading files should be arranged, so it would also be possible to integrate ChatBot with the Whatsapp, wechat and telegram APIs.

If your choice is Slack instead of Amazon Chime as chat engine to give orders to ChatBot and receive data, I suggest you rethink and use Slack only if you need to perform operations or issue complex orders, otherwise Amazon Chime is very easier and more immediate to configure.

We have included ChatBot with a view to supporting and speeding up everyday operations, some of which have been pending for weeks due to the impossibility of performing trivial fixing on specific machines, has fully covered the role assigned to it and we have had the opportunity to integrate it with existing systems like Zabbix and nagios core.

It's great to have a bot to ask about the status of your cloud computing resources on AWS.

it is even more fantastic if the same bot is able to warn you or the participants of a group chat on Amazon Chime of the occurrence of any problems or values ​​not suited to the type of SLA set.

Managing resources from a chat and being able to monitor them from the chat itself truly represents the turning point in the world of cloud computing.

Personally, I find the lack of an official or unofficial integration with other chats outside Amazon like Whatsapp, telegram or discord very heavy.

I hope that AWS will find a way to integrate it into existing chats without the need for entire teams to migrate to chatbot-supported chats.

After the initial deployment, seriously consider further integration in chatops emergency functions such as autoscaling or application of restrictive network security groups, you will need to manage any disasters or emergencies with a simple command without the need for heavy configurations and attempts to attack in progress.

Thanks to chatbot I configured some webhooks that can handle EC2 instances in cloud computing on AWS or migrate entire VPCs, turn on and off load balancers and apply restrictive security groups in case of attacks, all from a simple chat on my phone too out of office. it really helps to save a lot of time and work smart from home.

Imagine having the entire DevOps team working on Amazon AWS cloud computing resources in contact on an Amazon Chime or Slack chat, thanks to ChatBot it is possible to set infinite and personalized webhooks in order to obtain myriad of functions integrated with AWS without having to work with APIs and various additions to obtain functionality such as, by way of example only: proactive alerting in the case of EC2 instances with problems, non-regular latencies in the VPCs in use, high percentage of bounced mails in Amazon SES.

I think it's a real shame, despite the fact that it is born as an opponent of the same, the lack of support and the lack of integration with the API of the Telegram bots, the personalization would undoubtedly be greater and could be added in chat rooms with further monitoring systems or active ChatOps, I hope Amazon reconsiders its position in this regard.

If it is your first implementation of AWS ChatBot I recommend using native integration with Amazon Chime rather than the one with Slack, the required configuration is minimal and you will find yourself in few minutes to create commands and actions in GUI mode. Slack is for more advanced stuff and requires more integration with non-native Amazon methods and webhooks.

We have a bot ironically called "Wizzi" (from Wizard, or magician) with about 60 commands (webhooks) that we have configured without the need for skills in object-oriented programming languages ​​but with the simple AWS web interface that can easily manage the switchcases and the related commands sent to the bot itself, is shared between the DevOps teams and the systems engineers to monitor the status of the resources and receive notifications on Amazon Chime should there be any critical error or unexpected warning, we also configured the same to send at the request of the reports on the health status of the VPCs used by us as well as an emergency command to perform autoscaling of the EC2 in case of distributed denial of service attacks