-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(aws_docdb): support audit logging #17478
Comments
Thanks for opening the issue @ahammond! As always, we encourage community contributions, so if you'd like to open us a Pull Request adding this feature, that would be fantastic! Our "Contributing" guide: https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md. Thanks, |
So maybe you can review my pr or give me some tipps? |
Will do 🙂. |
closes #17478 *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
closes aws#17478 *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
closes aws#17478 *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Description
In order to use data stores while remaining HIPAA compliant, we need to log an audit trail. DocDB has support for this https://docs.aws.amazon.com/documentdb/latest/developerguide/event-auditing.html#event-auditing-enabling-auditing but it doesn't look like there's any way to enable this via CDK. We had a similar problem with RDS and solved it using a CustomResource lambda. Is there something like this for DocDB?
Use Case
HIPAA compliance
Proposed Solution
new aws_docdb.DatabaseCluster(this, 'Name', { audit: true, ... });
When this is enabled, it would automatically create a customer Parameter Group to match the DB with
audit_logs: 'enabled'
and then it would trigger a custom resource that would run the equivalent ofOther information
No response
Acknowledge
The text was updated successfully, but these errors were encountered: