Detect & correct RDS DB instances of older generation

Overview

Older generation instance types are more expensive and less performant than the current generation equivalents, you should be using the latest generation to reduce costs and increase performance.

This query trigger detects older generation RDS instances and then either sends a notification or attempts to perform a predefined corrective action.

Getting Started

By default, this trigger is disabled, however it can be configured by setting the below variables

rds_db_instances_of_older_generation_trigger_enabled should be set to true as the default is false.
rds_db_instances_of_older_generation_trigger_schedule should be set to your desired running schedule
rds_db_instances_of_older_generation_trigger_default_action should be set to your desired action (i.e. "notify" for notifications or "delete_instance" to delete the health check).

Then starting the server:

flowpipe server

or if you've set the variables in a .fpvars file:

flowpipe server --var-file=/path/to/your.fpvars

Pipeline

Correct RDS DB instances of older generation

Query

select
  concat(
    db_instance_identifier,
    ' [',
    region,
    '/',
    account_id,
    ']'
  ) as title,
  db_instance_identifier,
  region,
  _ctx ->> 'connection_name' as cred
from
  aws_rds_db_instance
where
  class like '%.t2.%'
  or class like '%.m3.%'
  or class like '%.m4.%'

Schedule

15m