This isn't really for a production environment. In prod you know what resources you have/need so you generally won't have anything in there that are "abandoned" per se. However, you could run this in the dry run mode and use the logs to see what you should and shouldn't clean up yourself.
Regarding Elastic Beanstalk, that's a great pick up. This is something I implemented for CloudFormation but completely forgot that Elastic Beanstalk creates resources in your account on your behalf. I'll work on adding those resources to the allowlist if the Elastic Beanstalk Application is allowlisted. Thanks.
Agree. First thing I thought when I read that. The first example wasn't particularly "nice" but they told me like it is rather than "we've passed it to our product team" which won't go anywhere anyway.
