Setup WPSOLR and Amazon AWS Elasticsearch
From WPSOLR 21.3.
This video suppose you already have an account at Amazon Elasticsearch.
You will see how to create an Amazon Elasticsearch index with a few clicks.
What is Amazon AWS Elasticsearch?
Amazon AWS Elasticsearch is a service to host Elasticsearch indexes, managed by Amazon AWS. Rather than installing Elasticsearch on your own servers, you get a subscription and let the service manage your indexes on your behalf. No need of manpower, or servers, anymore.
Here is the video tutorial to create and secure (authentication by user/secret) your first Elasticsearch cluster:
1 – Signup for a free test subscription at Amazon Elasticsearch
2 – Create a Key/Secret to secure your Elasticsearch indexes
2.1 – Navigate to your security credentials
2.2 – Navigate to your policies
2.3 – Click on Create policy button
2.4 – Add the Elasticsearch service to the new policy
2.5 – Add all Elasticsearch service actions (es:*) to the new policy
2.6 – Add all domains resources to the new policy
2.7 – Review the the new policy
2.8 – New policy has been created
2.9 – Navigate to your users menu. Click on Add user button
2.10 – Give new user a programmatic access: he will carry the access keys used by WPSOLR to access the index
2.11 – Attach new policy to new user
2.12 – Download user access keys before saving
2.13 – New user has been created
3 – Create a new Elasticsearch domain (aka “cluster”)
3.1 – Navigate to the Elasticsearch service page
3.2 – Click on Create a new domain button
3.3 – Select the latest Elasticsearch version
3.4 – Configure your domain instances
- Set a number of instances deployed in your domain
An instance is a VM (virtual machine). Each index in your domain will be split in shards and replicas (copy of shards). Each shard and each replica will be stored on exactly one instance. How many instance you need depends on: how many and how big indexes are, and how many shards and replicas are there per index.
- Select a VM type for each instance in your domain
The VM type defines how many resources (and of which quality) are given to each instance: RAM, disk, vCPUs.
3.5 – Configure your domain instances SSD storage
Fast disks are extremely important for Elasticsearch performance. Always choose SSD storage, not magnetic.
3.6 – Configure your domain network access: VPC or internet
Choose a VPC access if your WordPress is also hosted on Amazon AWS:
Or choose an internet access if your WordPress is not hosted on Amazon AWS:
3.7 – Copy your new user ARN (aka “user ID”)
3.8 – Select the domain template policy
3.9 – Paste your new user ARN in the template policy
3.10 – Copy the new domain endpoint to copy in WPSOLR later
Wait a few minutes, until the cluster is deployed. Then copy the endpoint that will later be pasted in WPSOLR.
3.11 – Summary. We now have: a new domain, with its endpoint, access key/secret, and region
4 – Create a new index in WPSOLR
Here is the video tutorial to create your first Amazon AWS Elasticsearch index in WPSOLR:
4.1 – Activate your WPSOLR license
4.2 – Select “Elasticsearch”, then “Amazon AWS” hosting
4.3 – Paste the Amazon domain Endpoint url
4.4 – Paste the AWS user access keys. The user is attached to the domain policy.
4.5 – Paste the domain region
Copy the domain’s region from your Amazon AWS console:
Then copy the region to WPSOLR’s index form:
4.6 – Index is created !
4.7 – Send your data to the index
4.8 – Perform a few searches