Kendra Cleanup Idle Indexes

Opportunity Name:

Kendra Cleanup Idle Indexes

AWS Resource Type:


Opportunity Description:

Kendra Indexes generate costs even when not being used. This FF finds and removes indexes idle for more than 31 days.

Criteria for identifying the opportunity:

The FF finds Kendra indexes:

  • No queries for at least 31 days (determined by IndexQueryCount)
  • Were created more than 31 days ago
  • Are in the active or failed state. 

Potential savings:

As the index will be deleted, we will save all its costs.

What happens when the Fixer is executed?

The current configuration is saved to S3, then we delete the index.

Is it possible to rollback once CloudFix implements the fixer?

Yes, by manually initiating the rollback document (Cloudfix-Runbook-KendraCleanupIdleIndexes-Rollback).  

When started, the change request will recreate the Kendra index with the previous configuration:

  • Bucket name: cloudfix-fixer-executions{account id}-prod
  • Bucket Key: KendraCleanUpIdleIndexes/{index_id}.json

After restoring the index, the customer can decide when to restore the data sources. 

Can CloudFix implement the fix automatically once I accept the recommendation?


Does this fix require downtime?


Additional Resources:



Article is closed for comments.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request