Checks whether ApsaraDB RDS instances are running High-availability Edition.
Scenario
If a primary instance fails in an ApsaraDB RDS instance of High-availability Edition, applications automatically switch to a standby instance. This improves system stability and prevents business system interruption.
Risk level
Default risk level: high.
The risk level can be changed when you apply this rule.
Compliance evaluation logic
If the ApsaraDB RDS instance is running High-availability Edition, the instance is compliant.
If the ApsaraDB RDS instance is running Basic Edition, the instance is non-compliant. To remediate, see Non-compliance remediation.
Rule details
|
Item |
Description |
|
Rule name |
rds-high-availability-category |
|
Rule ID |
rds-high-availability-category |
|
Tag |
RDS |
|
Automatic remediation |
Not supported |
|
Trigger type |
Configuration change |
|
Supported resource type |
ApsaraDB RDS instance |
|
Input parameter |
None |
Non-compliance remediation
Upgrade the ApsaraDB RDS instance from Basic Edition to High-availability Edition. For more information, see Upgrade an ApsaraDB RDS for SQL Server instance from Basic Edition to High-availability Edition or Change instance configurations.