Logstash s3 region us-east-2 not supported?


(Mike Nielsen) #1

My logstash 5.4.0 lab is in AWS us-east-2.

input {
   s3 {
   # 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", "ap-northeast-2", "sa-east-1", "us-gov-west-1", "cn-north-1", "ap-south-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", "ap-northeast-2", "sa-east-1", "us-gov-west-1", "cn-north-1", "ap-south-1"], got ["us-east-2"]
  region => "us-east-2"
  ...
}

Is it possible to add us-east-2 to the list against which the region is validated?


(Magnus Bäck) #2

This problem was reported in https://github.com/logstash-plugins/logstash-input-s3/issues/94 but the configuration actually resides in another plugin and was fixed in https://github.com/logstash-plugins/logstash-mixin-aws/pull/28. Could you try upgrading the logstash-mixin-aws plugin to v4.2.1?


(Mike Nielsen) #3

Magnus,

Thank you for taking the time to research the problem.

I couldn't seem to update the logstash-mixin-aws plugin:

I’m new to logstash, so maybe there’s something I’m missing? I would be grateful if you could steer me in the right direction.

[root@ip-192-168-158-179 logstash]# bin/logstash-plugin update logstash-mixin-aws
ERROR: Updated Aborted, message: Plugin logstash-mixin-aws is not installed so it cannot be updated, aborting
[root@ip-192-168-158-179 logstash]# bin/logstash-plugin install logstash-mixin-aws
Validating logstash-mixin-aws
logstash-mixin-aws is not a Logstash plugin

However logstash-plugin update gave me this:

Updated logstash-codec-fluent 3.0.2 to 3.1.1
Updated logstash-codec-netflow 3.3.0 to 3.4.0
Updated logstash-filter-date 3.1.3 to 3.1.5
Updated logstash-filter-fingerprint 3.0.2 to 3.0.3
Updated logstash-filter-geoip 4.0.4 to 4.1.1
Updated logstash-filter-grok 3.3.1 to 3.4.1
Updated logstash-filter-urldecode 3.0.2 to 3.0.3
Updated logstash-filter-useragent 3.0.3 to 3.1.1
Updated logstash-input-beats 3.1.12 to 3.1.15
Updated logstash-input-couchdb_changes 3.1.0 to 3.1.1
Updated logstash-input-elasticsearch 4.0.2 to 4.0.3
Updated logstash-input-http 3.0.3 to 3.0.4
Updated logstash-input-http_poller 3.1.1 to 3.3.0
Updated logstash-input-jdbc 4.1.3 to 4.2.0
Updated logstash-input-kafka 5.1.6 to 5.1.7
Updated logstash-input-log4j 3.0.3 to 3.0.5
Updated logstash-input-rabbitmq 5.2.2 to 5.2.3
Updated logstash-input-s3 3.1.2 to 3.1.4
Updated logstash-input-sqs 3.0.2 to 3.0.3
Updated logstash-input-twitter 3.0.3 to 3.0.4
Updated logstash-input-unix 3.0.2 to 3.0.3
Updated logstash-output-csv 3.0.2 to 3.0.3
Updated logstash-output-elasticsearch 6.3.0 to 7.3.1
Updated logstash-output-http 4.1.0 to 4.3.0
Updated logstash-output-kafka 5.1.5 to 5.1.6
Updated logstash-output-rabbitmq 4.0.6 to 4.0.7
Updated logstash-output-s3 4.0.5 to 4.0.7
Updated logstash-output-sns 4.0.2 to 4.0.3

My version:

[root@ip-192-168-158-179 logstash]# bin/logstash --version
logstash 5.4.0

(Mike Nielsen) #4

My upgrade seems to have fixed it.

Thank you Magnus.


(system) #5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.