Furthermore, transitioning from Cloudformation to Terraform is much, much easier than the reverse - you can't import existing resources into CloudFormation management, period (you can't even write the aws-prefixed tags to try to confuse it unless you're an AWS employee or something).
Nothing wrong with starting with CloudFormation or any other provider-native deployment description language if you're 100% in AWS and will stay that way. For the rest of us, Terraform is basically the only choice that can work besides paying for eye-watering expensive boutique tools that were developed a decade ago and have more limitations than Terraform.
If your things are wandering out of compliance by themselves, you have bigger problems, imho.
But what I prefer about CF is the “easy button”. If something weird happens or I can’t figure out something, I can use our business support plan with AWS.
As of 2 weeks ago[0] drift detection exists, but coverage is poor[1].
[0] https://aws.amazon.com/about-aws/whats-new/2018/11/aws-cloud...
[1] https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...
https://itnext.io/things-i-wish-i-knew-about-terraform-befor...