AWS Config provides the capability to assess, audit, and evaluate the configurations and relationships of resources within your AWS account. But how can this service be utilized for cost optimization? For instance, consider a scenario where you receive alerts for any deployment of an oversized Amazon Relational Database Service (Amazon RDS) instance. Using a larger instance type than necessary can lead to unexpected costs, impacting your overall budget.
This blog post illustrates how to create a custom rule in AWS Config to optimize expenses by monitoring database instances. In cases where multiple accounts are in use, customers might want to enforce the use of cost-effective database instances and be notified of any compliance breaches. For example, a testing account doesn’t need a production-sized instance for application development. A custom AWS Config rule will check the database instance type running in the account. If a non-compliant instance type is identified, AWS Config will flag the violation.
Solution Overview
The architecture of this solution is depicted in the following diagram:
Leave a Reply