AI agents are getting scary good. Tools like clawbot can understand your codebase, write features, fix bugs, and commit changes - all without much human input.
But that doesn’t mean you should let them run wild.
Regardless of whether you’re working on a product in a regulated industry like healthcare or finance, or building products that do not require such strict rules, maintaining control over your repositories is essential.
Streaming GitHub audit log to one centralized place is quite often used to maintain compliance or improve security within the organization, or both.
If you are reading this post, you are having trouble setting up this stream to your AWS S3. I will show you two common mistakes that I experienced and solved.
Many people do not like to write documentation, or if they do, it’s often detached from the source code, leading to it quickly becoming outdated.
This is a common problem I’ve noticed in the majority of closed-source codebases I’ve had the chance to work with. I can only hope that I was the unlucky one, and your case is different :)
If you use GitHub to store your repositories, you may also be utilizing GitHub Actions. I’ve been using it for several years across multiple projects. There have been a few instances where I had to debug a failing workflow.
