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.
Logging is part of every application, at least they should, but often logs contain sensitive information.
PII (Personally Identifiable Information), PHI (Protected Health Information), and other confidential data often end up in logs - often unintentionally. Storing raw, unmasked logs can lead to compliance violations (GDPR, HIPAA, SOC 2), security risks, and data exposure if logs are misused.
The easiest way to configure your CI/CD pipeline with AWS is to just create long-lived credentials, access and secret key, and store them in GitHub Actions.
While this method works, it has several security risks:
Sharing secrets across microservices creates security risks. Not only when one of the microservices is compromised, as then during rotation of single secret all of your microservices will be affected. Leading to potential downtimes.
