Browse categories
Explore
Fiverr Pro
English
$
USD
I will set up, fix, or tune your elasticsearch or elk stack cluster
About this Gig
Your cluster is yellow, shards will not assign, queries crawl, or you need Elasticsearch built right the first time. I ran a 426-node Elasticsearch cluster with Kibana and Logstash in AWS for a U.S. government cyber operations customer. Yours is a quiet afternoon.
What I do:
Fix: red or yellow health, unassigned shards, node will not join, heap pressure, slow queries, disk watermark lockouts, failed upgrades.
Build: single node to multi-node on RHEL, Ubuntu, Docker, or Kubernetes. Elasticsearch or OpenSearch.
Tune: shard sizing, ILM, mappings, refresh and merge, heap and GC, hot-warm tiers.
Secure: TLS, users and roles, API keys, Kibana spaces.
Ingest: Logstash, Filebeat, Metricbeat, ingest pipelines.
Protect: snapshots, restore tests, monitoring and alerts.
Document: a runbook your team can run without me.
Platforms: Elasticsearch 7 and 8, OpenSearch, Elastic Cloud, AWS OpenSearch, self-hosted on any Linux.
How it works: send SSH or cluster API access, tell me what is wrong or what you need, and I start the same day. Every order ends with a plain-English summary.
22 years Air Force enterprise IT and cyber ops, then ManTech and Raytheon. CEH, Security+, PMP, ITIL.
Database type:
Distributed database
•
Non-relational database
My Portfolio
FAQ
What access do you need?
SSH to the nodes with sudo, or an Elasticsearch API user with cluster admin rights, or both. For Elastic Cloud or AWS OpenSearch, a console login scoped to the cluster. Send it through Fiverr messages after purchase, never in the order requirements. Access is removed when the order closes.
Will you touch production without a backup?
No. Before any change that can lose data, I confirm a snapshot repository exists and take one, or tell you why I cannot and let you decide. Index settings changes are staged on a test index first when the cluster allows it.
Do you work with OpenSearch, Elastic Cloud, or AWS OpenSearch Service?
Yes to all three. OpenSearch is a fork of Elasticsearch 7.10, so the cluster mechanics are the same. On managed services I work within what the provider exposes; some node-level fixes are not possible there and I will say so up front.
