- 최신
- 최다 투표
- 가장 많은 댓글
Based on the screenshot and filename format, these look like S3 server access logging logs.
Server access logging is useful for security, audit, object requests and understanding your AWS costs. When you set up logging on your bucket, it is enabled at the bucket level and logs to a configured destination bucket. It is best practice to log to a different bucket than to the one you are monitoring otherwise you will end up in an infinite loop since each time you write a new log file it will be seen as a new request and create another new log file. This can result in higher storage costs.
Would recommend verifying your server access logging configuration and ensuring they are directing to a different bucket.
For details, see https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerLogs.html https://aws.amazon.com/premiumsupport/knowledge-center/s3-server-access-logs-same-bucket/
And I think I can confirm that, I turned logging off on this bucket and confirmed that these files stopped being created. Thank you!