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
"1.4 Kdb+ Software Evaluations. End User shall not distribute or otherwise make available to any third party any report regarding the performance of the Kdb+ Software, Kdb+ Software benchmarks or any information from such a report unless End User receives the express, prior written consent of Kx to disseminate such report or information."
I'd say the biggest advantage is that it slots in easily to an existing environment that is not necessarily managed strictly.
I've found depending on how strict your change management policies are, IAM creds can collect cruft over time as people push new policies in ad-hoc. So iamy is handy for such a situation
- iamy can sync in both directions - pull and push IAM config. So you can easily pull down the ad-hoc changes
- In order to use CFN you need to have access, so there is a chicken-egg scenario if you want to manage ALL users in config
- iamy gives you a nice execution plan of aws cli commands, CFN can be opaque
And iamy does ignore any resource managed by CFN, so it works well as complimentary tool.
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