Use plugin-api-v1 branch from original repo
plugin version 2.0.6 ( also shipped with logstash installer v2.3.3 )
-
feature add path field to event, so you can use grok plugin to match path, and specify your own fields.
-
bug fix bug when specify region => "cn-north-1".
one way, is to install 2.0.6 plugin, and replaced lib/logstash/inputs/s3.rb with one from this repo.
another way, is to download this repo, build gem, and install from your local path
git clone https://github.com/GrayJoy/logstash-input-s3.git
cd logstash-input-s3/
# use plugin-api-v1 branch
gem build logstash-input-s3.gemspec
bin/logstash-plugin install /path/to/logstash-input-s3-2.0.6.gem
input {
s3 {
sincedb_path => "/dev/null"
bucket => "<bucket>"
access_key_id => "<access_key_id>"
secret_access_key => "<secret_access_key>"
region => "cn-north-1"
filename_type => "basename"
}
}
filter {
grok {
match => { "path" => "%{GREEDYDATA:name}_%{NUMBER:num}.tar.gz" }
break_on_match => false
}
}
set conf filename_type to "basename", output the file basename to the path field
"path" => "sdsdsd_12.tar.gz"
set conf filename_type to "fullname", output the filename with directory to the path field
"path" => "uploads/sdsdsd_12.tar.gz"
---- ✄ original readme -----------------------
This is a plugin for Logstash.
It is fully free and fully open source. The license is Apache 2.0, meaning you are pretty much free to use it however you want in whatever way.
This plugin reads from your S3 bucket, and would require the following permissions applied to the AWS IAM Policy being used:
s3:ListBucket
to check if the S3 bucket exists and list objects in it.s3:GetObject
to check object metadata and download objects from S3 buckets.
You might also need s3:DeleteObject
when setting S3 input to delete on read.
And the s3:CreateBucket
permission to create a backup bucket unless already
exists.
For buckets that have versioning enabled, you might need to add additional permissions.
More information about S3 permissions can be found at - http://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html
Logstash provides infrastructure to automatically generate documentation for this plugin. We use the asciidoc format to write documentation so any comments in the source code will be first converted into asciidoc and then into html. All plugin documentation are placed under one central location.
- For formatting code or config example, you can use the asciidoc
[source,ruby]
directive - For more asciidoc formatting tips, see the excellent reference here https://github.com/elastic/docs#asciidoc-guide
Need help? Try #logstash on freenode IRC or the https://discuss.elastic.co/c/logstash discussion forum.
-
To get started, you'll need JRuby with the Bundler gem installed.
-
Create a new plugin or clone and existing from the GitHub logstash-plugins organization. We also provide example plugins.
-
Install dependencies
bundle install
- Update your dependencies
bundle install
- Run tests
bundle exec rspec
- Edit Logstash
Gemfile
and add the local plugin path, for example:
gem "logstash-filter-awesome", :path => "/your/local/logstash-filter-awesome"
- Install plugin
# Logstash 2.3 and higher
bin/logstash-plugin install --no-verify
# Prior to Logstash 2.3
bin/plugin install --no-verify
- Run Logstash with your plugin
bin/logstash -e 'filter {awesome {}}'
At this point any modifications to the plugin code will be applied to this local Logstash setup. After modifying the plugin, simply rerun Logstash.
You can use the same 2.1 method to run your plugin in an installed Logstash by editing its Gemfile
and pointing the :path
to your local plugin development directory or you can build the gem and install it using:
- Build your plugin gem
gem build logstash-filter-awesome.gemspec
- Install the plugin from the Logstash home
# Logstash 2.3 and higher
bin/logstash-plugin install --no-verify
# Prior to Logstash 2.3
bin/plugin install --no-verify
- Start Logstash and proceed to test the plugin
All contributions are welcome: ideas, patches, documentation, bug reports, complaints, and even something you drew up on a napkin.
Programming is not a required skill. Whatever you've seen about open source and maintainers or community members saying "send patches or die" - you will not see that here.
It is more important to the community that you are able to contribute.
For more information about contributing, see the CONTRIBUTING file.