You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,6 +107,20 @@ Usage of ./aws-es-proxy:
107
107
Print user requests
108
108
```
109
109
110
+
## Docker
111
+
112
+
There is a docker image avaiable for aws-es-proxy. There is an image on docker hub called `gorillastack/aws-es-proxy`. To run the image:
113
+
114
+
```sh
115
+
# Prints usage info (-h)
116
+
docker run --rm -it gorillastack/aws-es-proxy
117
+
118
+
# Runs with custom command/args
119
+
docker run --rm -it gorillastack/aws-es-proxy ./aws-es-proxy -endpoint https://dummy-host.ap-southeast-2.es.amazonaws.com
120
+
```
121
+
122
+
To expose a port number other than the default 9200, pass an environment variable of `PORT_NUM` to docker with the port number you wish to expose for your service.
123
+
110
124
## Using HTTP Clients
111
125
112
126
After you run *aws-es-proxy*, you can now open your Web browser on [http://localhost:9200](http://localhost:9200). Everything should be working as you have your own instance of ElasticSearch running on port 9200.
0 commit comments