I started working on marbot in 2016. Five years later I want to share my chatbot with you. As you can see, our marketing skills are not that well developed...
We started with Slack support and added Microsoft Teams support last year. Today, ~1,000 teams are using marbot to configure AWS monitoring, receive alerts, and solve incidents as a team.
I would be very happy to hear your thoughts. Maybe we have marbot users her as well?
PS: marbot itself is not open source. But all the required monitoring configuration (CloudFormation and Terraform) is and can be used without marbot: https://github.com/marbot-io
Cloudtrail and config buckets should be in a separate account with no access at all (besides root) otherwise an attacker can delete the cloudtrail logs and you have no idea what he did
Michael Wittig is author of Amazon Web Services in Action (Manning). He helps his clients to gain value from Amazon Web Services. As a software engineer he develops cloud-native real-time web and mobile applications. He migrated the complete IT infrastructure of the first bank in Germany to AWS. He has expertise in distributed system development and architecture, with experience in algorithmic trading and real-time analytics.
I started working on marbot in 2016. Five years later I want to share my chatbot with you. As you can see, our marketing skills are not that well developed...
We started with Slack support and added Microsoft Teams support last year. Today, ~1,000 teams are using marbot to configure AWS monitoring, receive alerts, and solve incidents as a team.
I would be very happy to hear your thoughts. Maybe we have marbot users her as well?
PS: marbot itself is not open source. But all the required monitoring configuration (CloudFormation and Terraform) is and can be used without marbot: https://github.com/marbot-io