library
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
Detect & correct EC2 instances without graviton processor
EC2 instances without graviton processor incur cost over time, with graviton processor (arm64 - 64-bit ARM architecture), you can save money in two ways: First, your instances run more efficiently due to the Graviton architecture. Second, you pay less for the time that they run. In fact, EC2 instances powered by Graviton are designed to deliver up to 19 percent better performance at 20 percent lower cost.
This query trigger identifies EC2 instances without graviton processor and then either sends a notification or attempts to perform a predefined corrective action.
Getting Started
By default, this trigger is disabled, but it can be configured by setting the following variables:
ec2_instances_without_graviton_trigger_enabled
should be set totrue
as the default isfalse
.ec2_instances_without_graviton_trigger_schedule
should be set to your preferred schedule.ec2_instances_without_graviton_default_action
should be set to the desired action (e.g.,"notify"
for notifications or"terminate_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
select concat(instance_id, ' [', region, '/', account_id, ']') as title, instance_id, region, _ctx ->> 'connection_name' as credfrom aws_ec2_instancewhere platform != 'windows' and architecture != 'arm64';
Schedule
15m