standard
turbot/aws_thrifty
- Detect & correct DynamoDB table with stale data
- Detect & correct EBS snapshots exceeding max age
- Detect & correct EBS volumes attached to stopped instances
- Detect & correct EBS volumes exceeding max size
- Detect & correct EBS volumes if unattached
- Detect & correct EBS volumes using gp2
- Detect & correct EBS volumes using io1
- Detect & correct EBS volumes with low IOPS
- Detect & correct EBS volumes with low usage
- Detect & correct EC2 application load balancers if unused
- Detect & correct EC2 classic load balancers if unused
- Detect & correct EC2 gateway load balancers if unused
- Detect & correct EC2 instances exceeding max age
- Detect & correct EC2 instances large
- Detect & correct EC2 instances of older generation
- Detect & correct EC2 instances without graviton
- Detect & correct EC2 network load balancers if unused
- Detect & correct EKS node groups without graviton
- Detect & correct Elasticache clusters exceeding max age
- Detect & correct EMR Clusters idle 30 mins
- Detect & correct Lambda functions without graviton
- Detect & correct RDS DB instances exceeding max age
- Detect & correct RDS DB instances of older generation
- Detect & correct RDS DB instances with low connection count
- Detect & correct RDS DB instances without graviton processor
- Detect & correct Route53 health checks if unused
- Detect & correct Route53 records with lower TTL
- Detect & correct S3 buckets without lifecycle policy
- Detect & correct SecretsManager secrets if unused
- Detect & correct VPC EIPs if unattached
- Detect & correct VPC NAT gateways if unused
Get Involved
Version
Overview
RDS instances can be costly to run, especially if they're rarely used, instances with low average connection counts per day should be reviewed to determine if they're still required.
This query trigger detects RDS instances with low average daily connections 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_with_low_connection_count_trigger_enabled
should be set totrue
as the default isfalse
.rds_db_instances_with_low_connection_count_trigger_schedule
should be set to your desired running schedulerds_db_instances_with_low_connection_count_default_action
should be set to your desired action (i.e."notify"
for notifications or"delete_instance"
to delete the instance).
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
Query
with rds_db_usage as ( select db_instance_identifier, round(sum(maximum) / count(maximum)) as avg_max, region, account_id, sp_connection_name from aws_rds_db_instance_metric_connections_daily where date_part('day', now() - timestamp) <= 30 group by db_instance_identifier, region, account_id, sp_connection_name)select concat( db_instance_identifier, ' [', region, '/', account_id, ']' ) as title, db_instance_identifier, region, sp_connection_name as connfrom rds_db_usagewhere avg_max = 0
Schedule
15m
Tags
category = Cost
class = unused
plugin = aws
service = AWS/RDS