- Refactoring, reuse code to manage
additional_settings
from mixin-aws #237
- Fix missing
metadata
andtype
of the last event #223
- Refactor: read sincedb time once per bucket listing #233
- Feat: cast true/false values for additional_settings #232
- Add ECS v8 support.
- Fixed unprocessed file with the same
last_modified
in ingestion. #220
- [DOC]Added note that only AWS S3 is supported. No other S3 compatible storage solutions are supported. #208
- [DOC]Added example for
exclude_pattern
and reordered option descriptions #204
- Added support for including objects restored from Glacier or Glacier Deep #199
- Added
gzip_pattern
option, enabling more flexible determination of whether a file is gzipped #165 - Refactor: log exception: class + unify logging messages a bit #201
- Fixed link formatting for input type (documentation)
- Skips objects that are archived to AWS Glacier with a helpful log message (previously they would log as matched, but then fail to load events) #160
- Added
watch_for_new_files
option, enabling single-batch imports #159
- Added ability to optionally include S3 object properties inside @metadata #155
- Fixed error in documentation by removing illegal commas #154
- #136 Avoid plugin crashes when encountering 'bad' files in S3 buckets
- Log entry when bucket is empty #150
- Symbolize hash keys for additional_settings hash #148
- Docs: Set the default_codec doc attribute.
- Improve error handling when listing/downloading from S3 #144
- Add documentation for endpoint, role_arn and role_session_name #142
- Add support for additional_settings option #141
- Add support for auto-detecting gzip files with
.gzip
extension, in addition to existing support for*.gz
- Improve performance of gzip decoding by 10x by using Java's Zlib
- Change default sincedb path to live in
{path.data}/plugins/inputs/s3
instead of $HOME. Prior Logstash installations (using $HOME default) are automatically migrated. - Don't download the file if the length is 0 #2
- Update gemspec summary
- Fix missing last multi-line entry #120
- Fix some documentation issues
- Avoid parsing non string elements #109
- The plugin will now include the s3 key in the metadata #105
- Fix an issue when the remote file contains multiple blob of gz in the same file #101
- Make the integration suite run
- Remove uneeded development dependency
- Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
- breaking,config: Remove deprecated config
credentials
andregion_endpoint
. Please use AWS mixin.
- Republish all the gems under jruby.
- Update the plugin to the version 2.0 of the plugin api, this change is required for Logstash 5.0 compatibility. See elastic/logstash#5141
- Depend on logstash-core-plugin-api instead of logstash-core, removing the need to mass update plugins on major releases of logstash
- New dependency requirements for logstash-core for the 5.0 release
- Fix for Error: No Such Key problem when deleting
- Do not raise an exception if the sincedb file is empty, instead return the current time #66
- Plugins were updated to follow the new shutdown semantic, this mainly allows Logstash to instruct input plugins to terminate gracefully, instead of using Thread.raise on the plugins' threads. Ref: elastic/logstash#3895
- Dependency on logstash-core update to 2.0