Logstash s3 input not recognized -- Couldn't find any input plugin named 's3'

Description

I just configured s3 input in my logstash.conf file. Logstash shows the following error when I try to start it. The same logstash.conf file (absolutely without any changes) works fine with logstash 1.2.1 but blows up with logstash 1.3.1.

My logstash.conf file:
------------------------------

input { s3 { sincedb_path => "C:/path/to/sincedb/.sincedb" type => "wsgLogs" debug => true bucket => "some-s3-bucket-name" credentials => "c:/path/to/credentials.txt" region => "us-east-1" prefix => "some-file-prefix" interval => 5 } } filter { if [type] == "wsgLogs" { grok { match => [ "message", "%{DATA:code}: %{GREEDYDATA:msg}"] } } } output { stdout { debug => true } }

Here is the error that I get:
----------------------------------

+---------------------------------------------------------+ | An unexpected error occurred. This is probably a bug. | | You can find help with this problem in a few places: | | | | * chat: #logstash IRC channel on freenode irc. | | IRC via the web: http://goo.gl/TI4Ro | | * email: logstash-users@googlegroups.com | | * bug system: https://logstash.jira.com/ | | | +---------------------------------------------------------+ The error reported is: Couldn't find any input plugin named 's3'. Are you sure this is correct? Trying to load the s3 input plugin resulted in this error: no such file to load -- file:/C:/dev/monitoring/trunk/t ools/logstash/logstash-1.3.1-flatjar.jar!//lib/aws/core/configuration

Gliffy Diagrams

Activity

Show:

Jordan Sissel January 10, 2014 at 12:56 AM

Dup of LOGSTASH-1718; fixed in master and 1.3.x branches. Will show up in the next release!

Sorry for the bugs slightly smiling face

Fixed

Details

Assignee

Reporter

Fix versions

Affects versions

Created December 18, 2013 at 7:22 PM
Updated January 10, 2014 at 12:56 AM
Resolved January 10, 2014 at 12:56 AM