Get the latest news and information about the ObjectRocket platform and its fully managed instances.
Free 30-Day Trial
Provision a single Redis (500MB), MongoDB with MMAPv1 (up to 5GB), or Elasticsearch with Kibana (512MB RAM / 4GB Disk) instance and experience the ObjectRocket platform backed by Fanatical Support® free for your first 30 days.
There's probably been a time when you said to yourself I wish Elasticsearch did _____ by itself. Luckily for you, Curator fills in a lot of those blanks. Curator has the ability to remove or close old indexes, create and modify aliases, control your snapshots, and many other handy features. We'll be highlighting a few key uses of Curator here, but feel free to read through the official documentation if you're looking for additional guidance.
One of the coolest new features in Elasticsearch 5 is the ingest node, which adds some Logstash-style processing to the Elasticsearch cluster, so data can be transformed before being indexed without needing another service and/or infrastructure to do it. A while back, we posted a quick blog on how to parse csv files with Logstash, so I'd like to provide the ingest pipeline version of that for comparison's sake.
Anybody who looks at the ObjectRocket for Elasticsearch page should (hopefully) notice that we mention dedicated containers and our high-performance hardware environment a number of times. Last week we posted a performance comparison between ourselves and a couple of the other Elasticsearch services to give you some insight into the results of our design. Now that you've seen the results, I thought it was about time that we walked through the architecture, where we designed for performance, and the other considerations we had to keep in mind.
As data platforms continue to expand and transform there's one aspect that never seems to change; everyone still wants a backup copy of their data! The evolution of technology still demands a need to have access to backups in order to restore to a local development environment, a copy for safe keeping or compliance, and various other use cases. This walkthrough will show you how to leverage the S3 repository plugin with your ObjectRocket for Elasticsearch instance.
Best practice dictates that every database user should only be assigned a minimum set of privileges that on the one hand allows the user to fulfill their mission, and on the other hand minimises the impact of a security breach. For example: a database user used for reporting; it is not nessesary and doesn’t make sense to provide write access since read-only access is adequate.
Have you every spent time dreaming of a fully automated Elasticsearch environment? If so, stay tuned as this post will walk you through some of ObjectRocket's basic API features for our Elasticsearch product. Using the ObjectRocet API will allow you to create instances, users, acls, and more on demand.