Disable Access Logs? about cdk-serverless-clamscan HOT 8 CLOSED

If nobody has objections, I am going to open a PR to disable these access logs, on the logs bucket

from cdk-serverless-clamscan.

Also, I noticed, after deleting the cfn stack the access log bucket is still there and has new logs. Is that the expected behavior?

from cdk-serverless-clamscan.

Hi is there a way to disable access logs from writing to a bucket? I noticed that there are a lot of logs generated over time and I was wondering if there was a way to make it optional.

You can use this property to disable access logging.

Also, what kind of data is being stored in here?

Data related to who/what is accessing the s3 bucket that contains the virus scan definitions

Also, I noticed, after deleting the cfn stack the access log bucket is still there and has new logs. Is that the expected behavior?

Hmm, this may be because the access log bucket is logging to itself causing an infinite logging loop. This isn't the intended behavior and I don't really see a reason to have the logging bucket lg to itself

from cdk-serverless-clamscan.

Hmm, this may be because the access log bucket is logging to itself causing an infinite logging loop. This isn't the intended behavior and I don't really see a reason to have the logging bucket lg to itself

This confirms what I have seen so far, is there a way to go around this or maybe have the logging bucket also be deleted when the stack is deleted?

from cdk-serverless-clamscan.

The logs are there for those who need them for auditing purposes. It doesn't make sense to remove it by default.

In this case you can empty and delete the bucket after the fact

from cdk-serverless-clamscan.

I see thank you! Hmm but does there happen to be a way around the infinite loop?

from cdk-serverless-clamscan.

I think it would be reasonable to have a PR to make it so that the default access log bucket doesn't log to itself or any other bucket

from cdk-serverless-clamscan.

Ready for review! 🎉

from cdk-serverless-clamscan.