Jdbc 日志存储显示未知设置aws\u访问\u密钥\u id

我正在使用Amazon Elasticsearch服务2.3.4和Logstash 2.3.0

我的配置

input {
jdbc {
    # Postgres jdbc connection string to our database, mydb
    jdbc_connection_string => "jdbc:mysql://awsmigration.XXXXXXXXX.ap-southeast-1.rds.amazonaws.com:3306/admin?zeroDateTimeBehavior=convertToNull"
    # The user we wish to execute our statement as
    jdbc_user => "dryrun"
    jdbc_password => "dryruntesting"
    # The path to our downloaded jdbc driver
    jdbc_driver_library => "/opt/logstash/drivers/mysql-connector-java-5.1.39/mysql-connector-java-5.1.39-bin.jar"
    # The name of the driver class for Postgresql
    jdbc_driver_class => "com.mysql.jdbc.Driver"
    # our query
    statement => "SELECT * from Receipt"

    jdbc_paging_enabled => true
    jdbc_page_size => 200
}
}
output {
elasticsearch {
    index => "slurp_receipt"
    document_type => "Receipt"
    document_id => "%{uid}"
    hosts => ["https://search-XXXXXXXXXXXX.ap-southeast-1.es.amazonaws.com:443"]
    aws_access_key_id => 'XXXXXXXXXXXXXXXXX'
    aws_secret_access_key => 'XXXXXXXXXXXXXXX'
}
}

我得到了这个错误：

Fri Aug 26 07:30:13 UTC 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Unknown setting 'aws_access_key_id' for elasticsearch {:level=>:error}
Unknown setting 'aws_secret_access_key' for elasticsearch {:level=>:error}
Pipeline aborted due to error {:exception=>#<LogStash::ConfigurationError: Something is wrong with your configuration.>, :backtrace=>["/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/config/mixin.rb:134:in `config_init'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/outputs/base.rb:63:in `initialize'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/output_delegator.rb:74:in `register'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:181:in `start_workers'", "org/jruby/RubyArray.java:1613:in `each'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:181:in `start_workers'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:136:in `run'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/agent.rb:473:in `start_pipeline'"], :level=>:error}

Fri Aug 26 07:30:13 UTC 2016警告：不建议在没有服务器身份验证的情况下建立SSL连接。根据MySQL 5.5.45+、5.6.26+和5.7.6+的要求，如果未设置explicit选项，默认情况下必须建立SSL连接。为了符合不使用SSL的现有应用程序，verifyServerCertificate属性设置为“false”。您需要通过设置useSSL=false显式禁用SSL，或者设置useSSL=true并为服务器证书验证提供信任库。
elasticsearch{:level=>：error}的未知设置“aws\u访问\u密钥\u id”
elasticsearch的未知设置“aws\u secret\u access\u key”{:level=>：error}
由于错误{：exception=>#，：backtrace=>[“/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/config/mixin.rb:134:in`config_init'”，/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/outputs/base.rb:63:in`initialize'，“/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/output_delegator.rb:74:in‘register’”，/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:181:in‘start_workers’，‘org/jruby/RubyArray.java:1613:in‘each’”/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:181:in'start_workers'，/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/logstash/pipeline.rb:136:in'run'，/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-lib/java/pipeline's]，：level=>：error}

---

如何解决此问题？

aws\u access\u key\u id

和

aws\u secret\u access\u key

不是Logstash elasticsearch插件的有效配置选项。

---

cf

aws\u access\u key\u id

和

aws\u secret\u access\u key

不是Logstash elasticsearch插件的有效配置选项。

---

cf

假设您正在使用amazon_es插件，您的输出应该如下所示：

output {
    amazon_es {
        index => "slurp_receipt"
        hosts => ["https://search-XXXXXXXXXXXX.ap-southeast-1.es.amazonaws.com:443"]
        aws_access_key_id => 'XXXXXXXXXXXXXXXXX'
        aws_secret_access_key => 'XXXXXXXXXXXXXXX'
    }
}

---

假设您正在使用amazon_es插件，您的输出应该如下所示：

output {
    amazon_es {
        index => "slurp_receipt"
        hosts => ["https://search-XXXXXXXXXXXX.ap-southeast-1.es.amazonaws.com:443"]
        aws_access_key_id => 'XXXXXXXXXXXXXXXXX'
        aws_secret_access_key => 'XXXXXXXXXXXXXXX'
    }
}

---

我正在使用这个插件@code>amazon_es，而不是

elasticsearch

。请看Fairy的答案以获得一个正确的例子。我正在使用这个插件@code>amazon_es，而不是

elasticsearch>。你要使用的插件是
h
。有关正确的示例，请参阅Fairy的答案。