Start a conversation

OpenSearch Idle Serverless Collections

Opportunity Name:

Idle OpenSearch Serverless Collection Finder

AWS Resource Type:

Amazon OpenSearch Serverless

Opportunity Description: 

This finder identifies idle OpenSearch serverless collections that incur unnecessary costs. By analyzing resource utilization over a 30-day period, the finder highlights collections with no activity, such as ingestion or search requests. These collections can then be safely deleted to realize cost savings without impacting performance.

OpenSearch serverless collections utilize OpenSearch Capacity Units (OCUs) for their operation, contributing to ongoing costs. Idle collections can be removed to eliminate these costs.

Many idle collections are remnants of discontinued features (e.g., Bedrock Knowledge Bases), dev/test environments, or abandoned resources. By detecting complete inactivity and confirming that no ingestion or query activity occurred, CloudFix provides confident recommendations for deletion - helping you eliminate waste and clean up your serverless footprint.

Criteria for Identifying the Opportunity:

  1. Resource Existence:
    • The account must have OpenSearch serverless collections.
  2. Idle Collection Validation:
    • The finder evaluates all serverless collections within a region/account together, and recommends deletion only when every collection in that region has had no recorded activity for ingestion or search requests over the past 30 days (evaluated using 5-minute interval metrics). If even one collection in the region is active, none of the region's collections are flagged.
    • Metrics analyzed:
      • IngestionDataRate
      • SearchRequestRate
  3. Tags Validation:
    • Collections tagged with cloudfix:dontFixIt are excluded. This tag is case-sensitive.
  4. Cost Analysis:
    • Savings are calculated based on the cost reported in the AWS Cost and Usage Report (CUR).

Potential Savings:

The potential savings are equivalent to the annualized cost of maintaining the identified idle collections. The savings are calculated using the CUR data for OCU usage over the past 30 days. If all collections in a region are idle, 100% of that region's OpenSearch Serverless cost is considered waste.

Example: if a region incurs $350/month in charges for idle collections, the projected annual savings is $4,200.

What Happens When the Fixer is Executed?

CloudFix generates recommendations to delete idle OpenSearch serverless collections. The actual deletion must be performed manually, as automatic deletion is outside the scope of this feature.

Is It Possible to Roll Back Once CloudFix Implements the Fixer?

Yes, rollback is possible if collections are manually deleted. Backup strategies, if required, should be managed prior to deletion as this feature does not include automated backups.

Can CloudFix Implement the Fix Automatically Once I Accept the Recommendation?

No, this feature provides deletion recommendations for idle collections. The action must be manually implemented by the user or through professional services.

Does the Fix Require Downtime?

No, there is no downtime associated with identifying idle OpenSearch serverless collections.

Additional Resources:

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted
  3. Updated

Comments