> 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/public-exposure/appsec-aws-323.md).

# ElastiCache cluster is using the default subnet group misconfiguration detected in code

## Rule Details

|                        |                                |
| ---------------------- | ------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_323               |
| Category - Subcategory | Public Exposure - VPC VCN VNet |
| Provider               | AWS                            |
| Severity               | LOW                            |
| Framework              | Terraform, Terraform Plan      |

## Impact

This rule is checking to ensure that ElastiCache clusters are not using the default subnet group provided by AWS. This is a potential issue for a few reasons. First, using the default subnet group may not align with the specific security or access control requirements of your particular applications or user groups. Custom subnet groups allow you to define network traffic routing and access rules more granularly. Second, having all ElastiCache clusters in the default subnet group may lead to situations where a network issue impacts all clusters instead of a single one. By having separate subnet groups, you can isolate clusters and minimize the impact of any potential issues. So, this rule tries to avoid these potential issues by making sure that each ElastiCache cluster has its own dedicated subnet group.

## How to Fix

*Resource:* aws\_elasticache\_cluster

* *Arguments:* subnet\_group\_name

## To fix this issue, you need to create a custom subnet group instead of using the default one, and attach it to the ElastiCache cluster. The subnet group should contain the appropriate subnets for your application. \[source,go]

resource "aws\_elasticache\_subnet\_group" "example" { name = "example" subnet\_ids = \[aws\_subnet.example1.id, aws\_subnet.example2.id] }

resource "aws\_elasticache\_cluster" "example" { cluster\_id = "cluster-example" engine = "memcached" node\_type = "cache.m4.large" num\_cache\_nodes = 2 parameter\_group\_name = "default.memcached1.4" engine\_version = "1.4.24"

* subnet\_group\_name = aws\_elasticache\_subnet\_group.example.name }

***


---

# 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/public-exposure/appsec-aws-323.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.