-
Notifications
You must be signed in to change notification settings - Fork 102
Troubleshooting Elastic Cloud and Quepid
Eric Pugh edited this page Oct 18, 2022
·
3 revisions
Elastic Cloud is a hosted platform from Elastic.co for Elasticsearch.
For adding CORS to your Elastic Cloud instance,
- Go to https://cloud.elastic.co/home
- Click on the gear icon next to your Elastic Cloud deployment
- Under your deployment name -> Click Edit
- Click on Manage user settings and extensions
- In the User Settings window to add a locally running Quepid,
http.cors:
enabled: true
allow-origin: /https?:\/\/localhost(:[0-9]+)?/
allow-credentials: true
allow-headers: "X-Requested-With, Content-Type, Content-Length, if-modified-since, Authorization"
If you are using the hosted quepid do app.quepid.com
instead of localhost
.
- Click Back button to close the window
- Scroll down and click on Save button to save the changes to the yaml configuration file
- This will restart Elasticsearch instance wait for it to come back online
For adding API Key to your Elastic Cloud instance,
- Go to https://cloud.elastic.co/home
- Click on the gear icon next to your Elastic Cloud deployment
- Under your deployment name -> Click Security
- Click the link that says "Make security changes in Kibana"
- On the left Nav, under Security, click API Keys.
- Make a key. Copy the key and use it in Quepid under the Advanced --> Custom Headers configuration pane.