Evaluates whether ApsaraDB for Redis instances have public IP addresses assigned. An instance without a public IP address is evaluated as Compliant.
Scenarios
Avoid assigning public IP addresses to ApsaraDB for Redis instances unless necessary, to reduce network security risks.
Risk level
Default risk level: high.
You can change the risk level based on your business requirements when you apply this rule.
Compliance evaluation logic
- If no public IP address is assigned to an ApsaraDB for Redis instance, the evaluation result is Compliant.
- If a public IP address is assigned to an ApsaraDB for Redis instance, the evaluation result is Incompliant. To remediate this configuration, see Incompliance remediation.
Rule details
| Item | Description |
| Rule name | redis-instance-no-public-ip |
| Rule identifier | redis-instance-no-public-ip |
| Tag service | Redis |
| Automatic remediation | Supported |
| Trigger type | Periodic execution |
| Evaluation frequency | Every 24 hours |
| Supported resource type | ApsaraDB for Redis instance |
| Input parameter | None. |
Incompliance remediation
Connect to an ApsaraDB for Redis instance by using a client, Data Management (DMS), or redis-cli. For more information, seeConnect to an ApsaraDB for Redis instance.