Three mechanisms protect an Opensolr index, and they compose: who may reach which request handler, who may authenticate, and what the traffic looks like on the wire.
01 · IP access rules, per request handler
Rules are set per handler, not per index
You can restrict /select, /update and the rest independently, so reads and writes do not have to share a policy.
Allow a list, or allow all
Name the individual addresses that may reach a handler, or keep the all wildcard where a restriction would get in the way.
Write access belongs to your servers
The common shape: /update limited to your backend addresses, /select left broader.
02 · HTTP authentication
A username and password on every request
Applies to every request handler, including the Solr admin interface.
Credentials are yours to change
Set them in the Security tab of your index control panel. Defaults are documented in default HTTP auth credentials.
Combine it with the IP rules
Authentication answers who you are; the IP rules answer where you may be. Sensitive indexes want both.
03 · SSL connections
Every connection on the platform, the website and every cloud server included, is encrypted with TLS. There is nothing to configure: use https:// and your data and credentials are protected in transit.
Security settings, in the index control panel.
Setting up security for a sensitive index?
Tell us what the index holds and who has to reach it. We will suggest the rule set, and there is a deeper walkthrough in securing your index with HTTP authentication.