Support for AWS Elasticsearch Service (managed Elasticsearch)?

[wes-novack]

If I add an agent for an AWS Elasticsearch Service endpoint to the plugin.json config file, the plugin service fails to start and doesn't output any errors to the log file.

Version: 2.1.1

Config example:

{
  "agents": [    
    {
      "host" : "aws-elasticsearch-service-some-string.us-west-2.es.amazonaws.com",
      "port" : 80,
      "username": "",
      "password": "",
      "_name": "Optional. By default loaded from elasticsearch. Rename to 'name' if you need to customize it"
    }
  ]
 }

I did verify that I can access the endpoint from the plugin host server, and that I make at least one ES API call.

Eg;

# curl -XGET 'http://aws-elasticsearch-service-some-string.us-west-2.es.amazonaws.com/_cluster/health?pretty=true'
{
  "cluster_name" : "accountnum:aws-elasticsearch-service",
  "status" : "green",
  "timed_out" : false,
  "number_of_nodes" : 2,
  "number_of_data_nodes" : 2,
  "active_primary_shards" : 21,
  "active_shards" : 42,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 0,
  "number_of_pending_tasks" : 0
}

[schmod]

Looks like we'd need to route requests through the AWS Java SDK or sign all of the corresponding HTTP requests.

[izo3]

+1

[snakelab]

+1