{"action":"closed","issue":{"url":"https://api.github.com/repos/taskrabbit/elasticsearch-dump/issues/422","repository_url":"https://api.github.com/repos/taskrabbit/elasticsearch-dump","labels_url":"https://api.github.com/repos/taskrabbit/elasticsearch-dump/issues/422/labels{/name}","comments_url":"https://api.github.com/repos/taskrabbit/elasticsearch-dump/issues/422/comments","events_url":"https://api.github.com/repos/taskrabbit/elasticsearch-dump/issues/422/events","html_url":"https://github.com/taskrabbit/elasticsearch-dump/issues/422","id":313521663,"number":422,"title":"AWS Elasticsearch requests fails on first scroll request","user":{"login":"jeff-hager-dev","id":9480444,"avatar_url":"https://avatars1.githubusercontent.com/u/9480444?v=4","gravatar_id":"","url":"https://api.github.com/users/jeff-hager-dev","html_url":"https://github.com/jeff-hager-dev","followers_url":"https://api.github.com/users/jeff-hager-dev/followers","following_url":"https://api.github.com/users/jeff-hager-dev/following{/other_user}","gists_url":"https://api.github.com/users/jeff-hager-dev/gists{/gist_id}","starred_url":"https://api.github.com/users/jeff-hager-dev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeff-hager-dev/subscriptions","organizations_url":"https://api.github.com/users/jeff-hager-dev/orgs","repos_url":"https://api.github.com/users/jeff-hager-dev/repos","events_url":"https://api.github.com/users/jeff-hager-dev/events{/privacy}","received_events_url":"https://api.github.com/users/jeff-hager-dev/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-04-11T23:27:30Z","updated_at":"2018-04-13T14:37:54Z","closed_at":"2018-04-13T14:37:54Z","author_association":"NONE","body":"## Enviroment Info\r\n- Elasticsearch Command: 2.3\r\n- Elasticdump version 1.7\r\n- Node version: v8.10.0\r\n- Full command: See below\r\n- Unfortunately I am not able to provide a data set at this time but it appears to be more of an issue of signing the requests for AWS then the data output. What data I get from the first request has been correct.\r\n\r\n## Error Info:\r\n\r\nWhen trying to interact with AWS elasticsearch service the first call goes through just fine and retreives the data. When the second call pass is made to get the next group it fails. The errors are different depending on the arguments I use.\r\n\r\n### Example 1 command: \r\n```\r\nelasticdump --limit=300 --type=data --input=https://elasticsearch-url.com/the-index \r\n--output=./output-file.json --awsAccessKeyId=\"some-access-key\" \r\n--awsSecretAccessKey=\"super-secret\"\r\n```\r\n\r\nError Message: \r\n```\r\nThe request signature we calculated does not match the signature you provided. Check your AWS \r\nSecret Access Key and signing method. Consult the service documentation for details.\r\n```\r\n\r\n\r\n### Example 2 command: \r\n```\r\nelasticdump --limit=300 --type=data --input=https://elasticsearch-url.com/the-index\r\n --output=./output-file.json --awsChain\r\n```\r\n\r\nError Message:  \r\n```\r\nevents.js:183\r\n      throw er; // Unhandled 'error' event\r\n      ^\r\n\r\nError: {\"message\":null}\r\n```\r\n\r\nHere the request is returning a `400: Bad Request` causing the  error to be tossed.\r\n\r\n\r\nI have been debugging this for about a day now, so any help would be greatly appreicated!\r\n"}}
{"actor":{"display_login":"ferronrsmith"}}