From 405b24cd18454419e73c6f2efa7ad6197901ff33 Mon Sep 17 00:00:00 2001 From: Andrew Date: Fri, 20 Jul 2018 21:14:35 -0700 Subject: [PATCH] Added section on privacy and security [skip ci] --- README.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 5b691c8..9335569 100644 --- a/README.md +++ b/README.md @@ -1053,7 +1053,7 @@ heroku addons:create bonsai heroku config:set ELASTICSEARCH_URL=`heroku config:get BONSAI_URL` ``` -For Found: +For Elastic Cloud (previously Found): ```sh heroku addons:create foundelasticsearch @@ -1086,7 +1086,7 @@ Create an initializer `config/initializers/elasticsearch.rb` with: ENV["ELASTICSEARCH_URL"] = "https://es-domain-1234.us-east-1.es.amazonaws.com" ``` -To use signed request, include in your Gemfile: +To use signed requests, include in your Gemfile: ```ruby gem 'faraday_middleware-aws-sigv4' @@ -1113,7 +1113,7 @@ rake searchkick:reindex CLASS=Product Create an initializer `config/initializers/elasticsearch.rb` with: ```ruby -ENV["ELASTICSEARCH_URL"] = "http://username:password@api.searchbox.io" +ENV["ELASTICSEARCH_URL"] = "https://username:password@host" ``` Then deploy and reindex: @@ -1122,6 +1122,12 @@ Then deploy and reindex: rake searchkick:reindex CLASS=Product ``` +### Privacy & Security + +We recommend encrypting data at rest and in transit (even inside your own network). This is especially important if you store personal data of your users. + +Bonsai, Elastic Cloud, and Amazon Elasticsearch all support encryption at rest and HTTPS. + ### Automatic Failover Create an initializer `config/initializers/elasticsearch.rb` with multiple hosts: -- libgit2 0.21.0