Releases: abutaha/aws-es-proxy
v1.5
v1.3
v1.2
v1.1
v1.0
- Replaced glide with go modes
- aws-sdk-go updated to v1.30.4
- Replaced uuid generator with lightweight Mongo BSON ObjectID
- Implemented HTTP Basic Auth
- Implemented HTTP timeout
- Fixed Kibana redirection issues
- Removed all annoying 'log.Fatalln' lines.
- Removed restrictions on endpoints. Any Elasticsearch endpoint can be used with the proxy, not only Amazon Elasticsearch.
v0.9
v0.8
v0.7
-
Content-Type is now mandatory for ES 6+. More information here: https://www.elastic.co/blog/strict-content-type-checking-for-elasticsearch-rest-requests
-
This release is enforcing on user's entered value for Content-Type. This seems to be required for Kibana too.
v0.6
Release Notes
This version comes with major changes.
- Most of the code was rewritten.
- Added ability to disable signing the requests. This should make aws-es-proxy work with any ElasticSearch installation.
- Added functionality to log client requests and server responses to log files for debug.
Notes:
At the moment, the log files are not being automatically rotated, so keep an eye on the file size.
If you are going to use Kibana most of the time, we recommend you to not enable file logging option as this will generate huge amount of unreadable data (Kibana webapp will be entirely written to the log file).
v0.5
Release Notes:
-
Add header 'Content-Type: application/json' if specified in the calling client (e.g. curl). This is required for Amazon ElasticSearch 6.0
-
Auto refresh AWS Credentials (thanks to diranged@ for the patch)
-
Added DockerFile (thanks to em0ney@ for the patch)