This setting must be a ["us-east-1", "us-west-1", "us-west-2", "eu-central-1", "eu-west-1", "ap-southeast-1", "ap-southeast-2", "ap-northeast-1", "sa-east-1", "us-gov-west-1", "cn-north-1"]

Expected one of ["us-east-1", "us-west-1", "us-west-2", "eu-central-1", "eu-west-1", "ap-southeast-1", "ap-southeast-2", "ap-northeast-1", "sa-east-1", "us-gov-west-1", "cn-north-1"], got ["us-east-2"]

region => "us-east-2" ... } } {:level=>:error} Error: Something is wrong with your configuration. {:level=>:error}

My configuration: s3 { bucket => "mybucketname" access_key_id => "key" secret_access_key => "secret" region => "us-east-2" prefix => "AWSLogs/89318..." type => "sometype" }

jordansissel commented 7 years ago

us-east-2 was only announced a month ago, so I'm not surprised the plugin hasn't received a patch to support it.

yaauie commented 6 years ago

Support for us-east-2 was added in version 4.2.1 of this plugin.

Please refer to the Working With Plugins docs for your version of Logstash to upgrade this plugin.

logstash-plugins / logstash-input-s3

Logstash S3 input doesn't recognise AWS region us-east-2 #94

This setting must be a ["us-east-1", "us-west-1", "us-west-2", "eu-central-1", "eu-west-1", "ap-southeast-1", "ap-southeast-2", "ap-northeast-1", "sa-east-1", "us-gov-west-1", "cn-north-1"]

Expected one of ["us-east-1", "us-west-1", "us-west-2", "eu-central-1", "eu-west-1", "ap-southeast-1", "ap-southeast-2", "ap-northeast-1", "sa-east-1", "us-gov-west-1", "cn-north-1"], got ["us-east-2"]