> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec-aws-153.md).

# Autoscaling groups did not supply tags to launch configurations misconfiguration detected in code

## Rule Details

|                        |                                |
| ---------------------- | ------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_153               |
| Category - Subcategory | Compute - Startup Script Leaks |
| Provider               | AWS                            |
| Severity               | LOW                            |
| Framework              | Terraform, Terraform Plan      |

## Impact

This rule detects whether autoscaling groups supply tags to their launch configurations. Tags provide several benefits: they enable tag-based access control through conditions in your IAM policies, they aid in identifying and organizing AWS resources, and they allow for resource-level permissions in your Amazon EC2 Auto Scaling identity-based policies. By tagging resources, you can apply the same tag across different AWS services to indicate related resources, and gain fine-grained control over which resources users can manage.

## How to Fix

*Resource:* aws\_autoscaling\_group

* *Arguments:* launch\_configuration, tags

## To mitigate this issue, ensure that the `aws_autoscaling_group` resource includes the `tag` or `tags` attribute with appropriate key-value pairs. \[source,go]

resource "aws\_autoscaling\_group" "example" { ...

* tags = concat( \[ { "key" = "interpolation1" "value" = "value3" "propagate\_at\_launch" = true }, ... ] ) }

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec-aws-153.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.