For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex CloudApplication Security

EC2 Auto Scaling groups are not utilizing EC2 launch templates misconfiguration detected in code

Rule Details

Cortex AppSec Rule ID

APPSEC_AWS_315

Category - Subcategory

Compute - Unsanctioned Resource Or Type

Provider

AWS

Severity

MEDIUM

Framework

Terraform, Terraform Plan

Impact

This rule is checking to verify that EC2 Auto Scaling groups in AWS are utilizing EC2 launch templates. EC2 launch templates define instance configuration for compute resources. They provide a way for you to save a launch configuration that you can reuse, which helps in maintaining the consistency of configurations and also speeds up the deployment process.

Not using EC2 launch templates can lead to several issues:

  1. Inconsistency: Manual configuration for every instance may lead to inconsistencies and errors, which can in turn lead to security vulnerabilities.

  2. Slow Deployment: Not using launch templates can result in a slower deployment process. Every time you need to launch a new instance, you would have to manually configure all the settings.

  3. Troubleshooting Difficulty: If instances are manually configured, troubleshooting can become complex as you need to identify the configuration for each instance separately.

  4. Scaling inefficiencies: Since auto-scaling groups adjust the number of instances on the fly according to load, not using a standard launch template would make this scaling inefficient and error-prone.

Therefore, it is important for the best practice and efficient deployments to use EC2 launch templates in AWS auto-scaling groups.

How to Fix

Resource: aws_autoscaling_group

  • Arguments: launch_template

To fix this issue, you need to refactor the EC2 AutoScaling group resource to use EC2 launch templates, rather than launch configurations.

[source,hcl]


Last updated

Was this helpful?