Closed umitseremet closed 5 years ago
it looks like the snapshot action does an implicit filter on instance type and is currently catching all t* instance types, instead of t1. It should be logging any implicit filtering (its not afaics), and it needs to be updated for the check on t2 instance types, per aws recent nov 2018 addition of support for backup/restore/snapshot on t2.
https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/WhatsNew.html
Hi,
When I want to create a snapshot for t-type Redis via c7n it can not be created while other types (r and m) can be created. Is there a special reason for that? Because I can create a manual snapshot for all type of Redises but C7N can trigger snapshot just for "r" and "m" type Redises.
In the documentation(https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/backups.html#backups-constraints) it says:
But there is not a negative definition for t2 types and I test t2 type;
Test Redises are totally identical except their types (t vs m)
Result is snapshots just for m-type one but not for t-type one, although I have tested it for several times:
Policy and Local-Run logs are below for my test Redises:
policy
custodian-run.log
update: omit json resource files