[FR] To make the Obsolete Snapshot Cleanup a Policy setting rather than a global setting.

[Justin.christjohn]

Our current environment includes about 75 accounts, most are separated between Production and Non-Production. Our non-prod retention is only 2 weeks and we have customers stating that once an instance is terminated, the want no more than 7 calendar days of retention. However, we have production accounts with 1 year retention and customers want to decommission systems and keep the final backup for the full year of retention. This causes a conflict with the obsolete snapshot removal feature since it is set globally rather than at the account or policy level. Today we have to manually remove the "obsolete" snapshots from our non-prod accounts and that takes up time and resources that are better spent elsewhere.

[nielsengelen]

Hi Justin,

Understood the use case. I fear that the only workaround (besides manually deleting them) would be to run 2 VB for AWS where you have 2 types of retention or create a script that could potentially do this. I'll verify internally if there is maybe another solution and will report back.

Regardless, we'll look into how to handle this for a future enhancement of the product to make it easier.

Thanks!