OpenSearch Domain Idle
A domain bills for its data and master nodes plus attached storage continuously, whether or not any search is issued.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Delete the idle OpenSearch domain. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
After a guided review, where you confirm the change, ZopNight deletes the resource, then checks the change took.
- Applies to
- OpenSearch Domains on AWS
- The fix, by hand
- Snapshot to S3: Snapshots → Create manual snapshot → choose your S3 repository.
- Identify ingest pipelines (Firehose, Logstash, Fluent Bit) pointing at this domain.
- To downsize: Actions → Update configuration → choose smaller instance type / fewer nodes (blue/green, multi-hour).
- To delete: Actions → Delete domain → type the domain name to confirm.
- Validate in CloudWatch that ingestion is failing over (or stopped) cleanly.
ZopNight does this for you after a guided review.
- Category
- Idle resources. Resources running but doing no useful work: zero invocations, no connections, no traffic.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-104- Full reference
Related checks
See the idle resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.