[ISSUE] AWS OS shard limit reached causing blocked test environments

[Szik]

Related to

see slack channel:
https://camunda.slack.com/archives/C06BN4SRB6C/p1758805551787499

Epic:

Overview

• QA e2e AWS OS cluster reached limit of 3000 shards and tests using AWS OS failed.
• automatically deleted generated data created by e2e tests

Actions

• delete indices, index templates, aliases in shorter period such as 2 days (typical TTL of cluster)
• or: delete shards actively by workflow

Sub-tasks

• sub-task

[eamonnmoloney]

These shards are deleted automatically by this job https://github.com/camunda/camunda-platform-helm/blob/main/.github/workflows/cleanup-opensearch-entra.yaml

This is done each night. @Szik is this ticket still needed?

[Szik]

@eamonnmoloney should be okay
in case, a policy used now will take care on e2e shards when older than 48h
we can consider this closed