Benchmark: Auto Scaling
Overview
This section contains recommendations for configuring Auto Scaling resources and options.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-compliance
Start the Powerpipe server:
steampipe service startpowerpipe server
Open http://localhost:9033 in your browser and select Auto Scaling.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.foundational_security_autoscaling
Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.foundational_security_autoscaling --share
Controls
- 1 Auto Scaling groups associated with a load balancer should use load balancer health checks
- 2 Amazon EC2 Auto Scaling group should cover multiple Availability Zones
- 3 Auto Scaling group should configure EC2 instances to require Instance Metadata Service Version 2 (IMDSv2)
- 4 Auto Scaling group launch configuration should not have metadata response hop limit greater than 1
- 5 Amazon EC2 instances launched using Auto Scaling group launch configurations should not have Public IP addresses
- 6 Auto Scaling groups should use multiple instance types in multiple Availability Zones
- 9 EC2 Auto Scaling groups should use EC2 launch templates