I probably found your old answer with config Curator: Delete oldest indices based on ES cluster size - is this still fine or some options should be changed?
"excess of 25.5TB of data" - how is this counted? it count only this indexes with prefix? whole elasticsearch database size? or how 
Second question, if I have 2 actions, first for size and second for 30d old indexes, it will work fine or there is possible some problem of collisions between actions etc?