Yes, some limitations and bugs are just ridiculously interesting. As a customer, I know my TAM would tell me this is much an organizational issue. One team push

Yes, some limitations and bugs are just ridiculously interesting. As a customer, I know my TAM would tell me this is much an organizational issue. One team pushed a feature, but the other team wasn't ready so the feature would just hold up in a pending state for months. I can't disclose which new feature's coming out, but essentially, yeah that feature won't come out until the other team gets their product updated. Another classic example is Directory Service's security group can only be found if you go to VPC / EC2 console page to search. The SG isn't even mentioned in the Directory Service console. I bought reserved instances for RDS and EC2, one of them accepts custom tagging, so you could name the purchase, but the other doesn't. If you use CloudFormation you want to make sure the resources are managed by the CFn. Your manual change could break the next CFn update. In some cases, rollback is not possible and will require AWS Support's intervention. Another example, say you have a cluster of 3 Cassandra nodes, you would build 3 EC2 from a single CFn stack. Well, time for server rotation (by that I meant taking the instance out and replace with a new one), one node at a time. Too bad you really can't out of the box. You have to build another stack with 3 instances, and then start configuring one node and swapping one node at a time plus changing the underlying dynamic inventory we got out of Ansible.