Permissions on subfolders about logstash-output-s3 HOT 3 OPEN

The problem here is due to the fact that we try to write a test file at the root of the bucket to validate the credentials when we start logstash.

Bad credentials are really the major problem we encounter when we debug stuff with users, I think we could allow people to disable the check when they have special permission on their bucket.

from logstash-output-s3.

For others: You can add the resource "arn:aws:s3:::{bucket_name}/logstash-programmatic-access-test-object-*" to your policy as this is the path that it tries to write to, rather than granting full bucket access.

from logstash-output-s3.

@ph I think all it would take to solve this issue is to write the test file to the prefix specified in the config rather than the root of the bucket.

Would you merge a PR that would do this?

from logstash-output-s3.