> 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/storage/appsec2-aws-50.md).

# AWS ElastiCache Redis cluster with Multi-AZ Automatic Failover feature set to disabled misconfigurat

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_AWS\_50                     |
| Category - Subcategory | Storage - Redundancy                 |
| Provider               | AWS                                  |
| Severity               | LOW                                  |
| Framework              | Terraform                            |
| Mapped CSPM/KSPM Rule  | fb8d5776-0bfa-4349-b1ec-1684f5353707 |

## Impact

This rule identifies ElastiCache Redis clusters that have Multi-AZ Automatic Failover feature set to disabled. It is recommended to enable the Multi-AZ Automatic Failover feature for your Redis Cache cluster, which will improve primary node reachability by providing read replica in case of network connectivity loss or loss of availability in the primary's availability zone for read/write operations.

NOTE Redis cluster Multi-AZ with automatic failover does not support T1 and T2 cache node types and is only available if the cluster has at least one read replica.

## How to Fix

## \[source,go]

## resource "aws\_elasticache\_replication\_group" "pass" { automatic\_failover\_enabled = true preferred\_cache\_cluster\_azs = \["us-west-2a", "us-west-2b"] replication\_group\_id = "tf-rep-group-1" description = "example description" node\_type = "cache.m4.large" num\_cache\_clusters = 2 parameter\_group\_name = "default.redis3.2" port = 6379 }


---

# 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/storage/appsec2-aws-50.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.