Engineers often reuse Terraform code without considering potential cost implications, such as using outdated database versions or expensive storage configurations, leading to unexpected cloud expenses. These oversights are not due to negligence but rather the result of prioritizing quick and reliable deployment, as engineers typically aren't aware of extended support fees or outdated defaults like AWS's gp2 volumes. In response, new FinOps policies have been introduced to preemptively address these issues, covering AWS services with extended support fees and flagging inefficient storage defaults. Additional policies target non-production environments, encouraging appropriate configurations to prevent unnecessary expenses. The policies also promote the use of negotiated discounts by steering engineers towards preferred configurations and provide metadata to assess the risk and effort involved in implementing changes. These enhancements, available in Infracost Cloud, aim to optimize cloud spending by enabling organizations to catch cost issues early, with customizable risk assessments and Autofix suggestions facilitating informed decision-making.