This is welcome. I got a rude awakening the first time I turned config rules on when the bill came in, and it kept coming even after they were killed in the UI.

This is welcome. I got a rude awakening the first time I turned config rules on when the bill came in, and it kept coming even after they were killed in the UI. I had racked up over $100 in a few months in config bills with the rules being disabled but in an odd state. Thankfully AWS gave us a credit, but I haven't really wanted to mess with them since. I'll give them another look now that the pricing is more in line with a usage model.