[GH-ISSUE #478] storing syslog into s3 bucket. #267

New issue

Closed

opened 2026-03-04 01:43:52 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:43:52 +03:00

Owner

Originally created by @yuvarajanlga on GitHub (Oct 3, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/478

Hi ,

I use s3 bucket to store the syslog . Its working fine. But the logs are updating in bucket after restarting the rsyslog service.

I configured s3 with IAM policy. And i mounted with the following command

s3fs netsafelogs /var/log/netsafe/ -o iam_role="auto"

Please let me know, how to frequently update the logs in s3bucket.

Originally created by @yuvarajanlga on GitHub (Oct 3, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/478 Hi , I use s3 bucket to store the syslog . Its working fine. But the logs are updating in bucket after restarting the rsyslog service. I configured s3 with IAM policy. And i mounted with the following command s3fs netsafelogs /var/log/netsafe/ -o iam_role="auto" Please let me know, how to frequently update the logs in s3bucket.

kerem closed this issue

2026-03-04 01:43:53 +03:00

kerem commented

2026-03-04 01:43:54 +03:00

Author

Owner

@brianabrams commented on GitHub (Jan 11, 2017):

Check out Logstash or AWS Cloudwatch Logs Agent. It may be a better option for your use case.

@brianabrams commented on GitHub (Jan 11, 2017): Check out Logstash or AWS Cloudwatch Logs Agent. It may be a better option for your use case.

kerem commented

2026-03-04 01:43:54 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 15, 2017):

@yuvarajanlga I'm sorry for my late reply.
In s3fs, the trigger to upload a file is to flush(or close) the file.
I think that syslog files mounting by s3fs is not good for performance.

Then you should use AWS Cloudwatch as @brianabrams said.

Thanks in advance for your help.
(I'm closing this issue, but if you have more problem please reopen this issue.)

@ggtakec commented on GitHub (Jan 15, 2017): @yuvarajanlga I'm sorry for my late reply. In s3fs, the trigger to upload a file is to flush(or close) the file. I think that syslog files mounting by s3fs is not good for performance. Then you should use AWS Cloudwatch as @brianabrams said. Thanks in advance for your help. (I'm closing this issue, but if you have more problem please reopen this issue.)

kerem referenced this issue

2026-03-04 01:53:58 +03:00

[PR #267] [MERGED] Added the _netdev option to the fstab example. #1437