SearchStax Cloud Private AWS
If your application resides in a Virtual Private Cloud (VPC) on Amazon Web Services (AWS), SearchStax® can provide Solr instances either within your own VPC or in a separate VPC.
Security and Compliance Benefits
A Virtual Private Cloud is a logically-isolated portion of a public cloud environment. It is a virtual network with specific rules for accessing other portions of the cloud and the Internet in general.
A VPC provides a highly-secure environment that prevents unauthorized access, DDoS and other threats that can compromise your application and network security. The heightened security of the VPC helps you honor your compliance commitments.
How does SearchStax interact with your VPC to provide Solr services without compromising security?
For applications that demand high security and isolation, SearchStax Cloud Private-AWS effectively separates your search infrastructure from other applications and traffic using one of two VPC architectures:
- VPC Peering Option: Solr servers reside in our VPC. Application servers reside in your VPC. Communication is by VPC peering.
- Shared VPC Option: Solr servers reside within your VPC with your application servers.
VPC Peering Option
The VPC Peering Option deploys the Solr servers in a VPC. This VPC communicates with your application VPC through VPC peering.
This guarantees that all of the operational aspects of managing Apache Solr are handled by SearchStax personnel. There is some additional cost in terms of network latency during searches. SearchStax engineers do not need access to your VPC.
Shared VPC Option
The Shared VPC Option leverages SearchStax to deploy Solr environments on the same VPC as your application servers. This minimizes latency between your application and the Apache Solr cluster. The Solr servers are completely under your control. SearchStax engineers may need occasional access to your VPC to help manage the Solr deployment.
To implement either of these architectures, send us a message at the SearchStax Support Desk. Please include the following information:
- Shared option or Peering option?
- Which AWS region?
- How many deployments (and nodes) do you plan to build?
This will initiate a dialog about pricing and technical details.